Question

A company uses CloudFormation StackSets with service-managed permissions to deploy a logging configuration stack to all accounts in an AWS Organizations OU. The stack template accepts a parameter, CentralLogBucketArn, that must point to a different destination bucket depending on which region the stack instance is deployed in (each region has its own regional log bucket). The DevOps team currently maintains a single stack set and wants a single deployment operation to populate the correct bucket ARN per region without maintaining separate stack sets. What is the MOST appropriate way to achieve this?

Accepted Answer

Use a single global parameter value and add a Mappings section in the template keyed on AWS::Region to resolve the correct bucket ARN at stack creation time.

Answer

Define parameter overrides per region using the StackSet operation's region-level override capability, supplying the region-specific CentralLogBucketArn when creating stack instances in each target region.

Answer

Create a separate stack set for each region, each hardcoding its own CentralLogBucketArn as a template default, and deploy them independently.

Answer

Store the per-region bucket ARNs in Parameter Store and reference them from the StackSet parameters using a dynamic ssm reference resolved at deploy time.