Closed joschna closed 8 months ago
This PR is included in version 6.3.0 :tada:
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
I added a new variable
s3_kms_key_id
that allows to specify the KMS key that is used to encrypt the S3 object representing the Lambda package.Motivation and Context
We are using S3 buckets with custom KMS key encryption to store our Lambda build artifacts. This module currently does not allow to specify a KMS key on the
aws_s3_object
resource which leads to failures when trying to upload the package (denied by bucket policy).Breaking Changes
No
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s) Added examples3-custom-kms-key
examples/*
projects Changes were validated by deploying thecomplete
examplepre-commit run -a
on my pull request