Open jlax47 opened 3 years ago
Hi @jlax47,
Thanks for the report! I can reproduce. Marking this as a bug.
Following up after some additional testing— confirmed the S3 API supports encrypting a previously unencrypted object being transferred from one bucket to another. This works:
aws s3api copy-object --copy-source sourcebucket/index.html --key index.html --bucket destinationbucket --sse-customer-algorithm AES256 --sse-customer-key somekey
I'm also affected by this issue. Thanks in advance!
May I work on it?
Hi @Da-1kun,
You're welcome to work on it! We'll need accompanying tests for any pull requests submitted for this fix.
@stobrien89 Is there any document which describes how to run the AWS CLI test? → I found out how to run the tests.
@stobrien89 @kdaily @jlax47 I made a PR, could you check it ?
Any update on this? It's been a year since this bug was reported and the only PR was closed.. 😬 The workaround with the s3api is unfortunately not applicable for my case, because I want to copy a folder recursively and that does not work with Copy-Object as far as I have seen. 😞
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug When doing a bucket to bucket copy using aws s3 cp, the copy fails when SSE-C is enabled on the destination, but not the source.
aws s3 cp s3://source/file s3://destination --sse-c --sse-c-key 00000000000000000000000000000000
SDK version number aws-cli/2.1.29 Python/3.9.2 Darwin/20.3.0 source/x86_64 prompt/off
Platform/OS/Hardware/Device What are you running the cli on? MacOS 11.2.3
To Reproduce (observed behavior)
Expected behavior A clear and concise description of what you expected to happen. The CLI should have copied a file from the source bucket to the destination bucket (with SSE-C on the copied file).
Logs/output
Additional context The problem stems from the fact that the cli is sending a head request to the source bucket with the SSE-C headers set, when it should not.