Add SSM policy to enable all cluster roles to access SSM #66
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
See if this actually works
This was referenced Jun 10, 2019
Closed
4 tasks
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.
Resolves hackoregon/civic-devops#241
SSM parameters were only accessible to the one ECS cluster running a manually-enhanced Role that includes
ssm:GetParametersandkms:Decryptactions for the existing resources.I've hard-coded those values for now in the
ecs-cluster.yamltemplate to ensure we have a working cluster. Separate ticket will be filed to refactor this into parameters that are injected through themaster.yamlso that this stack configuration could be re-used for different environments.