Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add messaging on how to enable sigv4 for s3 #1638

Merged
merged 1 commit into from
Nov 13, 2015

Conversation

kyleknap
Copy link
Contributor

Now the error will now look like this:

$ aws s3 cp s3://mybucketfoo/foo foo
download failed: s3://mybucketfoo/foo to ./foo A client error (InvalidArgument) occurred 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

Was brought up in discussion of this PR: #1623

cc @jamesls @mtdowling @rayluo @JordonPhillips

@kyleknap kyleknap added the pr:needs-review This PR needs a review from a Member. label Nov 13, 2015
@mtdowling
Copy link
Member

🚢

img

@JordonPhillips
Copy link
Member

:shipit:

uss_constitution

kyleknap added a commit that referenced this pull request Nov 13, 2015
Add messaging on how to enable sigv4 for s3
@kyleknap kyleknap merged commit b9984c9 into aws:develop Nov 13, 2015
@kyleknap kyleknap deleted the s3-kms-erros branch November 13, 2015 23:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr:needs-review This PR needs a review from a Member.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants