feature(kms): Allow Functions to Decrypt Environment Variables #1990
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.
...If They Have Been Encrypted
When a Function specifies that its environment variables should be
encrypted by supplying a value for
KmsKeyArn
, a correspondingPolicy will be generated for that Function's execution Role which
allows it to decrypt the environment variables with that key.
Permissions are restricted so that it should be able to do nothing
else with the key.
Issue #, if available:
#1989
Description of changes:
Checks for presence of
KmsKeyArn
and creates a correspondingAWS::IAM::Policy
forkms:Decrypt
on that value with restrictiveConditions
.Description of how you validated changes:
Ran all unit tests and compared generated policy to manually written one from other, earlier projects.
Checklist:
make pr
passesExamples?
Please reach out in the comments, if you want to add an example. Examples will be
added to
sam init
through https://github.com/awslabs/aws-sam-cli-app-templates/By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.