Multi stack support #95
Merged
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 7 commits
April 14, 2021 10:00
…id API validation errors like Role name lenght surpassing 64 characters
… Sets on Ruby Gem File
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 allows to have multiple Cloud Formation STACK SETS with Service Managed Roles in Cloud Formation supporting Multiple Environments. Using Stack Sets we can deploy to multiple account bundles using Organizational Units(OUs), i.e., one for Dev and one for Prod.
Instead of being fixed as AutoTag, the Lambda Function's name is taken from a Parameter in the Main Stack and that same Parameter is used in the multi-region Notification Stack to feed the SNS topic.
Thus you can have an AutoTag and AutoTagDev Lambda function running on the same region and under the same account if necessary, but most importantly you can separate them by environment name at the Stack Set level under your Parent AWS Account.
Thanks!