feat(object-storage): document Key Manager permissions required for SSE-KMS - #6788
Merged
Conversation
vanda-scw
approved these changes
Aug 13, 2026
vanda-scw
added
do not merge
Co-authored-by: vanda-scw <villyes@scaleway.com>
Loic-kd
approved these changes
Aug 14, 2026
vanda-scw
approved these changes
Aug 18, 2026
Collaborator
|
Hi @dulacp, |
vanda-scw
removed
status: tech review
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
3 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.
Your checklist for this pull request
Description
Enabling SSE-KMS on a bucket requires the IAM principal that reads and writes objects to hold Key Manager permission sets, in addition to its Object Storage ones. That requirement is not documented on the SSE-KMS pages, and it costs a failed deployment to discover.
I was able to confirm it on a small project, failing to upload a document on S3 without
KeyManagerKeyEncrypt.