A company has 40 accounts in AWS Organizations and needs the same baseline stack in each account across three Regions, including accounts created next month. Which approach meets this with the least manual effort?
Show answer and explanation
Answer: A
StackSets create, update, and delete stack instances across accounts, organizational units, and Regions from one definition. With service-managed permissions and auto deployment turned on, accounts added to a targeted OU later receive the stack without an operator doing anything.
This is the standard way to roll out a baseline such as logging, guardrails, or networking components at scale.
Why the other options are wrong
- B. Manual stacks per account and Region do not scale and leave new accounts unconfigured until someone notices.
- C. A nested stack only composes templates inside one stack and cannot reach other accounts.
- D. A stack in the management account affects only that account, not the member accounts that need the baseline.
Exam tip. Auto deployment is what covers accounts that join the OU later.