Tim Kay

I recall implementing AWS V4 signatures. Please try adding --AWS4 to the command line. I don't recall if the support is for all AWS products.

I just updated the code with support for Signature Version 4 across almost all other services. (S3 was already supported. Now EC2, etc.) Feedback, please. To use, add --AWS4 to...

Hmmm. Works for me: # ./aws describe-tags --region eu-central-1 --AWS4 f9b4a3b4-cb79-4cfa-be74-cfff9d6379fb Please send the output with -vv (two v's).

I modified my ~.awssecret file to contain an invalid key, and I got # aws describe-tags --region eu-central-1 --AWS4 +-------------+--------------------------------------------------------------+ | Code | Message | +-------------+--------------------------------------------------------------+ | AuthFailure | AWS...

Yes, but the credentials are stored in a different place. Make sure you have valid credentials in ~/.awssecret On Jul 16, 2015 5:30 AM, "mattheworiordan" [email protected] wrote: > I am...

I hadn't realized that you are using role-based authentication. In that case, you have to add --role. However, then we get a different error, which I am working on now.

Thanks for the suggestion. I do try to add new features to "aws", but unfortunately, I am swamped now, and I won't get to it for a while. ...Tim On...

The documentation for "aws" is pretty far behind. It was a lot of work just keeping up with the AWS enhancements and changes, and I didn't do a good job...

Thanks for the great feedback! I'm glad "aws" has been working for you. "aws" does this sanity check because lots of users ran into problem without it. By default, "aws"...

You make a great point: If it fails to find a Date: header, then it should behave better. I'll make that change.