article --summary
The summary
This AWS announcement explains how custom execution role templates for CloudFormation StackSets let you control which IAM role StackSets uses in member accounts, instead of the default role that carries AdministratorAccess. You'll learn why this matters for least-privilege access and how the custom role is bootstrapped into each account with a small helper stack.
The post also covers a second benefit: service-managed stack sets can now deploy templates that use nested stacks, macros, and transforms such as SAM, which were not previously supported. It notes that the execution role template itself still cannot use those features, and it shows the CLI flags needed for a SAM workload.
Finally, it lists the prerequisites, including service-managed permissions and trusted access with AWS Organizations, and the four rules a role template must meet: a single IAM role with a required name prefix, a trust policy tied to the organization management account, a specific output, and no nested stacks or transforms. A sample template and creation instructions round it out.
Editorial note: This is a summary of an article first published by AWS DevOps Blog. The full piece is on their site.