Looks like the system botocore has the fix, bit there's another one
bundled with awscli that doesn't - and that's the one being used:
/usr/lib/python3/dist-packages/awscli/botocore/httpsession.py
/usr/lib/python3/dist-packages/botocore/httpsession.py:
So looks like we need to remove the botocore bundled with awscli, i
tried simply renaming /usr/lib/python3/dist-packages/awscli/botocore but
then it seems awscli couldn't find the system botocore:
Traceback (most recent call last):
File "/usr/bin/aws", line 19, in
import awscli.clidriver
File "/usr/lib/python3/dist-packages/awscli/clidriver.py", line 21,
in
import botocore.session
ModuleNotFoundError: No module named 'botocore'
So something is hardcoded to look inside awscli i guess?
Simply copying httpsession.py from the system botocore to the awscli one
fixes this error but I'm not sure we want to just do that.
On Wed, 19 Jun 2024 09:07:42 +0200 Gregor Riepl wrote:
> that leads here: https://github.com/aws/aws-cli/issues/7905
> "cannot import name 'DEFAULT_CIPHERS' from 'urllib3.util.ssl_'"
>
> https://github.com/boto/botocore/pull/2924/files
It's not mentioned in the changelog, but this commit was already included in
1.29.123:
https://github.com/boto/botocore/compare/1.29.122...1.29.123
Debian sid has 1.34.46, so I'm not entirely sure why it's still broken?
--
Simon John
