Best practices for StackSets
Before we begin, we need to learn a bit about best practices for StackSets. This is crucial, because we don't want to make a monstrous zoo instead of a properly organized infrastructure, and we want to have efficiency and transparency for stack operations. The most important of these are listed as follows:
- Develop universal templates: By default, StackSet deploys the same template and parameter set in all the regions and accounts. To allow this process to be as automated as possible, we must focus on the reusability of our template. Do not hardcode regions and availability zones; instead, use AWS SSM parameter stores in every account and region to ease the deployment of StackSet. Don't set names for global resources such as IAM roles, users, groups, policies, S3 bucket, and so on to avoid naming conflicts.
Think big, start small. If you are asked to create a StackSet for an application that will serve tens of accounts and regions, it is...
