
                    For aws-cli, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

Leaving this here in case someone comes across this via google like me:
I had the same issue with the same environment (anaconda environment with python 3.6) 

aws cli Invalid Syntax Error when running any AWS command.

For those of you looking to create a bucket via the CLI run this: aws s3api create-bucket --bucket dev-xxxx-com-state --region us-east-2
A client error (IllegalLocationConstraintException) occurred when calling the CreateBucket operation: The unspecified location constraint is incompatible for the region specific endpoint this request was sent to

aws cli aws s3api create-bucket throws error for us-east-2

Just kill this 'feature' seriously Even apart from security concerns it certainly violates the principle of least surprise 

aws cli aws ssm put-parameter performs an HTTP GET request when the value param is an url

For people arriving here from Google here's one way to list all your instances across all regions with the AWS CLI (based on the discussion above): 

aws cli How to describe instances from all regions?

Interesting It looks like it's failing to parse ~/.aws/config Can you try putting in fake values?  Here's the exact steps I tried 

aws cli Can't install / configure aws cli

eb deploy gave me


find  -mtime +10950 -print -exec touch {} \;
solved the problem. 

aws cli Code Deploy - Unhandled exception - ZIP does not support timestamps before 1980

We have had some success here by running Hi It seems the latest release of awscli requires PyYAML as its dependency 

aws cli PyYAML requires python-dev dependency

If you still want to use cli (maybe for automation) this is the full command according to the official docs 

aws cli aws ecr get-login error: argument operation: Invalid choice

Alright so I can confirm that getting assume role can be tricky AWS CLI fails while attempting to issue API calls with MFA authentication 

aws cli aws-cli fails to acquire session token before issuing sts:AssumeRole call

In case anyone is looking for a workaround you can try using jq like so:
aws cloudformation deploy --parameter-overrides $(jq -r '.[] | [.ParameterKey 

aws cli Allow cloudformation deploy to accept a paramater file

@Simonwep I think this is due to a difference in behavior between the V1 and V2 clients When you pip install you're getting the v1 client 

aws cli Executable breaks GitHub action - python version works

me too we avoid this problem by specifying aws-cli and awseb-cli version. Problem
I'm not sure 

aws cli Broken elastic beasntalk deploy in latest update

Hi Mike Thanks for bringing this issue to our attention Hi I'm having trouble getting ECR to authenticate using CLI v2 First off 

aws cli ECR docker login issues with CLI v2

Ok I found the problem I had region = ireland in my config file while the correct one is region = eu-west-1. 

aws cli Missing required header for this request: x-amz-content-sha256

echo $(aws ecr get-authorization-token --region eu-central-1 --output text --query 'authorizationData[].authorizationToken' | base64 -d | cut -d: -f2) | docker login -u AWS https://123456.dkr.ecr.eu-central-1.amazonaws.com --password-stdin

aws cli aws ecr get-login should use --password-stdin if available

I need to run

in my .zshrc before
complete -C '/usr/local/bin/aws_completer' aws
also note you have to remove the 2 if you install the GA version 

aws cli [V2] Command completion doesn't work

@tleyden you probably need to just encapsulate it in quotes This doesn't work:


Whereas this works:


Other folks have reported the same issue:  https://gist.github.com/andywirv/f312d561c9702522f6d4ede1fe2750bd

aws cli aws lambda update-function-configuration --environment key/value pair only works for one key/value

Looks like this was fixed a few days ago with PR #206 @jamesls will a release with this fix get pushed up to PyPI sometime soon?  Thanks!
In the meantime 

aws shell when i run aws-shell, I got a error

This error occurs if you copy / paste step 5 from this page https://docs.aws.amazon.com/iot/latest/developerguide/device-certs-your-own.html  

aws cli AWS IOT UnicodeDecodeError error when register-ca-certificate

It's happening to me too installed with pip.. Ubuntu 14.04
Python 2.7.6
pip 9.0.1
awscli==1.11.25
botocore==1.4.5
Update:  Strange 