[release-1.13] Add descriptive error message when SSE-C is denied on S3 buckets (cherry-pick #318) - #321
Open
kaovilai wants to merge 1 commit into
Open
Conversation
…ero-io#318) As of April 2026, AWS disables SSE-C by default on new S3 buckets. Users configuring customerKeyEncryptionFile or customerKeyEncryptionSecret will get a generic AccessDenied 403 error with no indication of the root cause. This change detects AccessDenied errors when SSE-C is configured and wraps them with guidance on how to enable SSE-C on the bucket using PutBucketEncryption, or switch to SSE-KMS as an alternative. Also updates documentation to note the April 2026 SSE-C bucket requirement and recommend SSE-KMS for users who do not need customer-managed keys. Fixes #9762 Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com> (cherry picked from commit 3eb40b5) Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of #318 to
release-1.13.Original PR: #318
release-1.13predates thebuildPutObjectInputrefactor (that helper doesn't exist on this branch), soPutObject's conditional-error-wrap was applied directly to its existing inlines3.PutObjectInputconstruction instead of pulling in that refactor. Test-side, only the three tests PR #318 itself actually adds (TestWrapSSECError,TestObjectExists_SSECAccessDenied,TestGetObject_SSECAccessDenied) were kept —TestCreateSignedURL*/TestBuildPutObjectInputare unrelated pre-existingmaincontent tied to that same refactor and don't apply here.Note
Responses generated with Claude