-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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(lambda): support for customer managed encryption (CMCMK) #32072
Conversation
tools/@aws-cdk/spec2cdk/temporary-schemas/us-east-1/aws-lambda-sourcekmskey.json
Outdated
Show resolved
Hide resolved
Pull request has been modified.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #32072 +/- ##
==========================================
- Coverage 77.30% 77.29% -0.02%
==========================================
Files 114 114
Lines 7627 7627
Branches 1360 1360
==========================================
- Hits 5896 5895 -1
- Misses 1549 1550 +1
Partials 182 182
Flags with carried forward coverage won't be shown. Click here to find out more.
|
81ba967
to
91749f2
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Comments on closed issues and PRs are hard for our team to see. |
Issue # (if applicable)
NA
Reason for this change
AWS Lambda is adding a new feature that allows customers to use their own AWS KMS keys to encrypt their Lambda function code stored in Amazon S3. This gives customers greater control and flexibility over the encryption of their sensitive data and code. The new SourceKMSKeyArn field in the Lambda function's Code object enables customers to specify the ARN of the KMS key to be used for encryption.
Description of how you validated changes
Have added unit tests and integration test to verify the feature.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license