docs: add SSE-KMS instructions & add tip re: UI generated policy#2842
Draft
SeanWhelan wants to merge 2 commits intomasterfrom
Draft
docs: add SSE-KMS instructions & add tip re: UI generated policy#2842SeanWhelan wants to merge 2 commits intomasterfrom
SeanWhelan wants to merge 2 commits intomasterfrom
Conversation
|
🚀 Preview deployed to https://docs.estuary.dev/pr-preview/pr-2842/ 📄 Changed pages: |
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
1 participant
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.
Description:
Adds S3 encryption guidance for storage mapping buckets. Documents that SSE-S3 works out of the box, and that SSE-KMS is supported if the customer grants Estuary's data plane the necessary KMS permissions (
kms:GenerateDataKey,kms:Decrypt,kms:DescribeKey). Includes a ready-to-use KMS key policy snippet and a fallback option to switch to SSE-S3. Also adds a callout that the storage mapping UI generates a complete bucket policy with the correct IAM ARNs.Workflow steps:
N/A
Documentation links affected:
getting-started/installation.md- https://docs.estuary.dev/getting-started/installation/#amazon-s3Notes for reviewers:
kms:GenerateDataKey,kms:Decrypt,kms:DescribeKeyto the data plane IAM user