Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Requests specifying Server Side Encryption with AWS KMS managed keys require AWS Signature Version 4
See original GitHub issueWith default setting by aws-adfs, I can’t download files from s3 buckets.
$ aws s3 cp s3://xxx/xxx.yml xxx.yml
download failed: s3://xxx/xxx.yml to xxx.yml An error occurred (InvalidArgument) when calling the GetObject operation: Requests specifying Server Side Encryption with AWS KMS managed keys require AWS Signature Version 4. You can enable AWS Signature Version 4 by running the command: aws configure set s3.signature_version s3v4
After run aws configure set s3.signature_version s3v4
Below lines are added to ~/.aws/config
s3 =
signature_version = s3v4
So if I aws-adfs reset and aws-adfs login again, I lost the s3 setting in config file.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Released with version: 0.2.3
@SydOps I think it’s rather related to way how boto is working, since the configuration is read by this library. aws-adfs just appends configuration and nothing more.