fix(core): Remove encryption on lifecycle SNS Topic #163
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
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.
Fixes: #162
The problem is that something changed in the KMS service that the AutoScalingGroup now needs some additional permissions to be able to publish lifecycle events to a KMS-encrypted SNS Topic. RFDK is not applying whatever those permissions are, and so a deployment will fail.
Solution: Remove encryption from the SNS Topic. An earlier security review concluded that this encryption is not necessary since there is no sensitive information in this SNS Topic -- it is purely Lifecycle Event control messages.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license