feat: improve syncer s3 kms encryption #1915
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 10 commits
February 28, 2022 15:25
* added resource policies to sqs queues with a deny for all unsecured actions
* added policy to lambda to use kms key * specify encryption on s3 upload
julada
force-pushed
the
feature/improve-syncer-kms-encryption
branch
from
c02a97c
to
f9ec111
Compare
3 tasks
npalm
changed the title
npalm
added a commit
that referenced
this pull request
May 4, 2022
manual merge of #1915 Co-authored-by: Julius Adamek <julius.adamek@adesso.de>
|
Thx for you contribution, due to conflicts I have merged the changes manual in #2013 (add you as co author). |
npalm
added a commit
that referenced
this pull request
May 5, 2022
manual merge of #1915 Co-authored-by: Julius Adamek <julius.adamek@adesso.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
this pr also includes the terraform provider update. This PR should be merged first.
our cloud security tool requires us to set a bucket policy to enforce the kms encryption: