Skip to content

Fix SSE-C copy operations: pass CopySourceSSECustomerKey to S3 copy#555

Open
xingzihai wants to merge 1 commit intodrivendataorg:masterfrom
xingzihai:fix-sse-c-copy-operations
Open

Fix SSE-C copy operations: pass CopySourceSSECustomerKey to S3 copy#555
xingzihai wants to merge 1 commit intodrivendataorg:masterfrom
xingzihai:fix-sse-c-copy-operations

Conversation

@xingzihai
Copy link
Copy Markdown

Issue: #500 - Failing S3 move and copy operations with SSE-C

When using S3 with SSE-C encryption, copy and move operations fail because CopySourceSSECustomerKey parameters are not passed.

Changes:

  • Add boto3_copy_extra_args for copy-specific SSE-C params
  • Update _move_file to use upload + copy-specific args

Fixes #500

Issue: drivendataorg#500 - Failing S3 move and copy operations with SSE-C

When using S3 with SSE-C encryption, copy and move operations fail
because CopySourceSSECustomerKey parameters are not passed.

Changes:
- Add boto3_copy_extra_args for copy-specific SSE-C params
- Update _move_file to use upload + copy-specific args

Fixes drivendataorg#500
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Failing S3 move and copy operations with SSE-C

1 participant