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

Cannot delete s3 object with custom sse encryption #2494

Closed
omencl opened this issue Mar 16, 2017 · 8 comments
Closed

Cannot delete s3 object with custom sse encryption #2494

omencl opened this issue Mar 16, 2017 · 8 comments
Labels
bug This issue is a bug.

Comments

@omencl
Copy link

omencl commented Mar 16, 2017

When using command aws --profile some_profile s3 cp /some_file s3://bucket/some_file --sse-c AES256 --sse-c-key XXX file is successfully uploaded to server. Also copy back from bucket to local server works.
But this command aws --profile some_profile s3 rm s3://bucket/some_file returns

fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request

Same object uploaded without sse-c can be deleted normally.

@stealthycoin
Copy link
Contributor

Can you add --debug to the command and give us the logs here?

@stealthycoin stealthycoin added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Mar 17, 2017
@omencl
Copy link
Author

omencl commented Mar 17, 2017

Sorry, sure, here it is. I replaced original bucket name with some foo name in logs.
log.TXT

Thank you!

@omencl
Copy link
Author

omencl commented Mar 17, 2017

Note: now I am using s3api delete-object as a workaround

@neelay-shah
Copy link

I am having the exact same issue.

@stealthycoin
Copy link
Contributor

Interesting, can yuo give the working debug logs for s3api delete-object and also @ mention me when you post them?

@lvnyan05
Copy link

I had a same issue, too ! and I could avoid it as follows.

$ aws s3 cp file s3://backet/test/ --sse-c AES256 --sse-c-key xxx
upload: ./file to s3://backet/test

$ aws s3 rm s3://backet/test/file
fatal error: An error occurred (403) when calling the HeadObject operation: Forbidden

$ aws s3 rm s3://backet/test/ --recursive
delete: s3://backet/test/file

Best Regards.

@neelay-shah
Copy link

Hi @stealthycoin
Sorry for the delay, find the log in attachment.
aws-s3-rm-log.txt

@stealthycoin stealthycoin added bug This issue is a bug. and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Jun 2, 2017
@stealthycoin
Copy link
Contributor

Yep so this definitely looks like a bug to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

No branches or pull requests

4 participants