Question

A DevOps team manages a global application using a single CloudFormation StackSet that deploys to 12 accounts across 4 regions. The template creates a primary DynamoDB global table configuration and Lambda functions that reference it. During deployment, the team requires that the us-east-1 region always deploys and completes successfully FIRST, because it provisions a shared global resource that all other regions depend on. If us-east-1 fails, no other region should be attempted. The team currently deploys to all regions with default concurrency settings and occasionally sees other regions fail because the shared resource is not yet available. Which approach best enforces the required ordering?

Accepted Answer

Configure the StackSet operation with RegionOrder listing us-east-1 first, set MaxConcurrentCount to 1, and set FailureTolerance to 0 so regions deploy sequentially and any failure halts the operation.

Answer

Increase the region concurrency to deploy all regions in parallel and add a WaitCondition in each regional stack that polls for the shared resource before proceeding.

Answer

Split the shared resource into a separate StackSet, but keep both StackSets using default region concurrency so they deploy at the same time to reduce total deployment time.

Answer

Enable service-managed permissions with automatic deployment so new accounts inherit the resource, and rely on eventual consistency for the region ordering.