-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(eks): envelope encryption for secrets #9438
Conversation
Title does not follow the guidelines of Conventional Commits. Please adjust title before merge. |
@davidsung this is ready for review yes? |
yes @iliapolo thanks! |
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.
Ha ha... Just submitted a PR for this yesterday as well... I'll close it in favor of this one.
One thing to note: I don't believe EKS supports updating the encryption configuration, so we need to fail in an update is attempted. See this.
Additionally, please add unit tests to the cluster provider - see this as a reference: https://github.com/aws/aws-cdk/pull/9472/files#diff-1cc6461fbdf09ac0273cadbbe91bd2fc
@davidsung you be great if you want to follow up on this and complete it. |
Exactly! I will handle the update event like what you did with the next PR. Thanks! |
@eladb i have made the changes according to your advise. kindly review! Thanks! |
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.
Waiting for AWS SDK to be updated in lambda
Hi @davidsung - FYI The PR is approved but there are some merge conflicts that needs resolving. |
I will rebase this upstream |
0b6d0ee
to
fc7b307
Compare
Title does not follow the guidelines of Conventional Commits. Please adjust title before merge. |
add envelope encryption support upon eks cluster creation add update event handling for secretEncryptionKey mutation attempt add test case for checking update event handling update readme Closes aws#9140 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
fc7b307
to
c764b9c
Compare
Hi @iliapolo, I've resolved the conflicts. This PR is now ready for your review. Thanks! |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
feat(eks): envelope encryption for secrets
This PR adds envelope encryption support for Amazon EKS. Added a new key
secretsEncryptionKey
inClusterProps
for users to specify their own KMS CMK upon cluster creation:Closes: #9140
Considerations
Secrets Encryption
is enabled in the provisioned Amazon EKS (both standard resourceAWS::EKS::Cluster
and custom resourceCustom::AWSCDK-EKS-Cluster
) after running an integration test from scratch.['kms:Encrypt', 'kms:Decrypt', 'kms:DescribeKey', 'kms:CreateGrant']
. Note: The encryption provider is using its own way to generate data encryption key, not using KMS GenerateDataKey, and hence IAM permissionkms:GenerateDataKey*
is not required.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license