feat(lambda): support for customer managed encryption (CMCMK) #32072
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.
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