Allow user to provide a KMS key to encrypt S3 content #34
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.
This PR allows users to provide a KMS key to encrypt data at rest in S3. More importantly, the IAM role for the KB is granted decrypt access to the key for the purposes of ingesting content. The IAM permissions present in this PR match the specific policy generated by the AWS Console wizard for KB creation.
(This is a duplicate of PR 27 which was closed due to pre-commit difficulties)