Greetings,
The primary bug reported here is still present -- awscli seems quite
broken in sid -- and the proposed resolution works.
On a very clean and up to date Debian sid system:
$ dpkg -l | grep awscli
ii awscli 1.5.5-1 all
Universal Command Line Environment for AWS
$ aws
Traceback (most recent call last):
File "/usr/bin/aws", line 15, in <module>
import awscli.clidriver
File "/usr/share/awscli/awscli/clidriver.py", line 16, in <module>
import botocore.session
File "/usr/lib/python3/dist-packages/botocore/session.py", line 29, in
<module>
from botocore.endpoint import EndpointCreator
File "/usr/lib/python3/dist-packages/botocore/endpoint.py", line 28, in
<module>
from botocore.awsrequest import AWSRequest
File "/usr/lib/python3/dist-packages/botocore/awsrequest.py", line 27, in
<module>
from requests.packages.urllib3.connection import HTTPConnection
ImportError: cannot import name 'HTTPConnection'
$ sudo sed -i -e "s/^from requests.packages./from /"
/usr/lib/python3/dist-packages/botocore/awsrequest.py
$ aws
usage: aws [options] <command> <subcommand> [parameters]
aws: error: the following arguments are required: command
Regarding the second item raised by Tom, the failure of the command:
> $ aws --debug --region us-east-1c ec2 describe-instances
This command fails because `us-east-1c` is an availability zone, not a
region. Using `us-east-1` here instead works fine.
Cheers,
-- TC
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
