Skip to content

Fix S3 multipart SSE-C integration test broken by new S3 default bucket encryption behavior#6850

Open
Fred1155 wants to merge 1 commit intomasterfrom
bole/fix_sse_integration_test
Open

Fix S3 multipart SSE-C integration test broken by new S3 default bucket encryption behavior#6850
Fred1155 wants to merge 1 commit intomasterfrom
bole/fix_sse_integration_test

Conversation

@Fred1155
Copy link
Copy Markdown
Contributor

@Fred1155 Fred1155 commented Apr 8, 2026

Motivation and Context

Starting April 6, 2026, AWS S3 began rolling out a new default security setting that automatically disables server-side encryption with customer-provided keys (SSE-C) for all newly created general purpose buckets announcement.

This caused S3MultipartClientPutObjectIntegrationTest.putObject_withSSECAndChecksum_objectSentCorrectly to fail with AccessDeniedException because the test creates a fresh bucket (with no encryption configuration) and then attempts an SSE-C upload, which is now blocked by default.

Modifications

After bucket creation in @BeforeAll, call PutBucketEncryption to explicitly unblock SSE-C on the test bucket by setting BlockedEncryptionTypes to EncryptionType.NONE.
Reference: https://docs.aws.amazon.com/us_en/AmazonS3/latest/userguide/blocking-unblocking-s3-c-encryption-gpb.html

Testing

Local test passed

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed
  • I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

@Fred1155 Fred1155 requested a review from a team as a code owner April 8, 2026 23:53
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 9, 2026

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.

2 participants