Showing posts with label AWS CLI. Show all posts
Showing posts with label AWS CLI. Show all posts
Tuesday, March 5, 2019
Wednesday, February 27, 2019
Thursday, February 7, 2019
Monday, December 24, 2018
Thursday, November 1, 2018
AWS CLI error in Amazon Linux
AWS CLI error in Amazon Linux
AWS CLI - is AWS Command Line Interface. It is a tool that brings in all the AWS provided services under a single roof, meaning, we will be able to create, modify and access resources using this command line interface via commands
We all know that we need to install in any flavor of Linux; recently, I faced an issue of accessing AWS CLI in Amazon linux AMI
Accessing aws from shell prompt returns "too few arguments" or aws --version returns awscli version installed in that instance
Let us see on resolving the same
Error:
[ec2-user@ip-xx.xx.xx] aws
ImportError: cannot import name HTTPClientError
Issue:
- could be that system update was applied using "sudo yum update" which might have updated any dependencies or so
Resolution:
- re-install didnt work
- sudo pip install upgrade --awscli - resolved the issue....Yayyyyyyyyyy !!!
Friday, October 12, 2018
AWS decode authorization message
AWS - How-to decode authorization error messages
Today I came across an interesting issue in AWS
I was mapping Jenkins to launch EC2 slaves dynamically[yes finally, i did it :-)]
The Launch configuration was giving some errors unreadable and was really confused about whats wrong and where
Finally identified, that the AWS Authorization messages thrown out on any request is bound to generate an encoded message, which is really confusing !!!
The encode message thus generated as part of EC2 access permissions error will have to deciphered by decoding the same using the AWS CLI utility. Yessss !!! AWS has it all !!!
Today I came across an interesting issue in AWS
I was mapping Jenkins to launch EC2 slaves dynamically[yes finally, i did it :-)]
The Launch configuration was giving some errors unreadable and was really confused about whats wrong and where
Finally identified, that the AWS Authorization messages thrown out on any request is bound to generate an encoded message, which is really confusing !!!
The encode message thus generated as part of EC2 access permissions error will have to deciphered by decoding the same using the AWS CLI utility. Yessss !!! AWS has it all !!!
Subscribe to:
Posts (Atom)





