awscli install fails due to cpython error about amazon-bedrock-workshop

[rmartine-ias]

This is because of yaml/pyyaml#601 and can be resolved with:

pip install wheel
pip install dependencies/awscli-1.27.162-py3-none-any.whl --no-build-isolation

A newer awscli might fix it as well.

[athewsey]

Same error observed in SageMaker Studio Data Science 3.0 kernel (Python 3.10.6), blocking #12

In that environment, upgrading wheel (default is already 0.40.0, newest available is 0.41.0) does not solve the issue - maybe there's a downgrade that might? Either way it's a bit of a fundamental package that I prefer to avoid messing with when possible 🫤

As far as i can tell, nothing in the workshop actually uses the preview AWS CLI today: The only CLI commands I see are aws s3 cp ...

So another option (aside from waiting for new CLI) could be to just remove the custom awscli install from the workshop notebooks altogether? Pros: Python 3.10+ environments including DataSci3.0 should work; Cons: If anybody did want to explore/demonstrate the Bedrock CLI (or expand the workshop examples to show it in action), they couldn't.

[athewsey]

@rmartine-ias In Studio I'm seeing that instead of installing wheel (which doesn't work on DataSci 3.0), running the awscli/boto installs with --no-build-isolation as shown below fixes it:

%pip install --no-build-isolation --force-reinstall \
    ../dependencies/awscli-1.27.162-py3-none-any.whl \
    ../dependencies/boto3-1.26.162-py3-none-any.whl \
    ../dependencies/botocore-1.29.162-py3-none-any.whl

I'd appreciate feedback whether that approach works for other people facing this issue in non-Studio environments too? (Or if anybody deeper on Python packaging than I am has reason to believe it's a bad idea!)