Provide possibility to assume AWS role (AWS STS) #21
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.
Hello
I've added a new CLI parameter
assume-rolewhich allows to leverage AWS "assume role" feature and thus to manage stacks in a different AWS account.In our case developers have AWS accounts in the main account, but it's pretty limited permissions in the main account and a dedicated AWS subaccount for testing. When they test their code locally with Minikube, they should be able to test their Stack resources as well. The most suitable way to provide such possibility is to configure the CloudFormation operator to use the assume role feature.