-
Notifications
You must be signed in to change notification settings - Fork 3
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
upgrade cdk and default encryption for compliance #473
Conversation
if (this.props.compliancePolicy.isCustomerManagedKeys()) { | ||
// data in the buckets are encrypted with a key that the customer owns | ||
this.props.compliancePolicy.dataEncryptionKey.grantEncryptDecrypt( | ||
grantee | ||
); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if I need to do this for AWS-managed keys. I don't have to for AWS-owned because there's zero visibility into that, but AWS-managed creates a key with an alias, like aws/s3
and I'm hoping I don't need to grant permissions but I may.
Bug: the Entity Tables are using an AWS-owned key instead of an AWS-managed key: Fixed in: d16b66b |
Compliance
Construct that manages compliance policies and centralizes encryption keys