Chapter 13: The Operational Excellence Pillar
- 1. C, D. It’s a best practice to organize stacks by lifecycle (e.g., development, test, production) and ownership (e.g., network team, development team). You can store templates for multiple stacks in the same bucket, and there’s no need to separate templates for different stacks into different buckets. Organizing stacks by resource cost doesn’t offer any advantage since the cost is the same regardless of which stack a resource is in.
- 2. A, B. Parameters let you input custom values into a template when you create a stack. The purpose of parameters is to avoid hard-coding those values into a template. An AMI ID and EC2 key-pair name are values that likely would not be hard-coded into a template. Although you define the stack name when you create a stack, it is not a parameter that you define in a template. The logical ID of a resource must be hard-coded in the template.
- 3. C. When using nested stacks, the parent stack...
