Skip to content

CAMEL-21314: camel-aws2-s3 - supply the customer key when copying SSE-C objects (4.18.x backport) - #25044

Merged
oscerd merged 1 commit into
apache:camel-4.18.xfrom
oscerd:backport-4.18.x-CAMEL-21314
Jul 23, 2026
Merged

CAMEL-21314: camel-aws2-s3 - supply the customer key when copying SSE-C objects (4.18.x backport)#25044
oscerd merged 1 commit into
apache:camel-4.18.xfrom
oscerd:backport-4.18.x-CAMEL-21314

Conversation

@oscerd

@oscerd oscerd commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Backport of #25027 (merged on main) to camel-4.18.x. Clean cherry-pick.

copyObject set only the destination SSE-C parameters, so copying an object stored with SSE-C failed with InvalidRequest: SSE-C encrypted objects require customer key headers (400). The fix also sets copySourceSSECustomerKey/MD5/Algorithm, and re-enables S3CopyObjectCustomerKeyIT.

Verified against localstack on this branch: S3CopyObjectCustomerKeyIT passes with the fix (Tests run: 1, Failures: 0, Errors: 0).

Claude Code on behalf of Andrea Cosentino (@oscerd).

🤖 Generated with Claude Code

…-C objects (apache#25027)

copyObject only set the destination SSE-C parameters, so copying an object stored with SSE-C failed with 'SSE-C encrypted objects require customer key headers'. Also set copySourceSSECustomerKey/MD5/Algorithm, and re-enable S3CopyObjectCustomerKeyIT.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
@oscerd oscerd added the bug Something isn't working label Jul 23, 2026
@oscerd
oscerd requested review from davsclaus and gnodet July 23, 2026 07:53
@oscerd oscerd self-assigned this Jul 23, 2026
@oscerd oscerd added this to the 4.18.4 milestone Jul 23, 2026
@oscerd
oscerd merged commit b1b94fc into apache:camel-4.18.x Jul 23, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants