Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow user to provide a KMS key to encrypt S3 content #34

Merged
merged 2 commits into from
Nov 21, 2024

Conversation

corey-cole
Copy link
Contributor

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)

@corey-cole
Copy link
Contributor Author

Side note: Figured out why this PR (and PR 27) were failing. For reasons, can't install pre-commit in this repo and so was running latest terraform-docs. There's a bug fix in the latest version compared to the frozen version in pre-commit.

@scottschreckengaust
Copy link
Collaborator

/do-e2e-tests

Copy link

End to end test has been scheduled

Copy link

E2E tests in progress

1 similar comment
Copy link

E2E tests in progress

Copy link

@aws-ia-automator-prod aws-ia-automator-prod bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

E2E tests completed successfully

@alexa-perlov alexa-perlov merged commit fe6f324 into aws-ia:main Nov 21, 2024
2 checks passed
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.

3 participants