1 Answer
- Newest
- Most votes
- Most comments
0
This is caused by a disabled or non–opt-in Region. During decommission, Control Tower updates StackSets and CloudFormation returns OptInRequired (403) when a target Region isn’t enabled in one of the governed accounts. Identify the failed StackSet instance (AWSControlTowerBP-BASELINE-SERVICE-LINKED-ROLE) and check its account/Region. Either enable (opt-in) that Region for all Control Tower accounts or remove the Region from governance and delete the StackSet instance. After resolving, retry the landing zone decommission.
answered 9 months ago
Relevant content
asked a year ago
