Skip to content

AWS Control Tower fails to decommission Landing Zone – OptInRequired (CloudFormation 403)

-1

I am trying to decommission an AWS Control Tower Landing Zone, but the process fails with the following error:

AWS Control Tower has failed to decommission your landing zone. An error occurred while decommissioning your landing zone: AWS Control Tower failed to deploy one or more StackSet instances.

StackSet: AWSControlTowerBP-BASELINE-SERVICE-LINKED-ROLE Stack instance status: OUTDATED

Error message: The AWS Access Key Id needs a subscription for the service (Service: AmazonCloudFormation; Status Code: 403; Error Code: OptInRequired)

The failure happens during the removal of Control Tower baselines, specifically related to the Service-Linked Role StackSet.

Has anyone encountered this issue when decommissioning a Landing Zone? Is this related to a region or service that requires explicit opt-in (for example, regions not enabled in the account or services not subscribed)?

Any guidance on how to properly resolve this and complete the decommissioning would be appreciated.

asked 9 months ago138 views

1 Answer
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

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.