Prerequisites
In your AWS Organizations management account, check the quotas for the following services:
AWS CloudTrail
AWS Config
AWS CloudFormation StackSets
AWS Organizations management account
Service control policies
Perform an inventory and assessment of your existing AWS Landing Zone environment. At a minimum, look at the following resources:
AWS Landing Zone manifest.yaml file
Additional baselines
Additional AWS Service Catalog product
AWS Region where AWS IAM Identity Center (successor to AWS Single Sign-On) is configured, if used
CloudFormation stack sets
Customizations deployed
If you are using a new organization, create an email address for AWS Control Tower management account. (This isn't required if you are using an existing organization for AWS Control Tower deployment.)
Make sure that this email address has never been used in AWS before.
(Optional) Create an email address for the log archive account. (This isn't required if you are using an existing organization for AWS Control Tower deployment.)
Make sure that this email address has never been used in AWS before.
(Optional) Create an email address for the audit account. (This isn't required if you are using an existing account.)
Make sure that this email address has never been used in AWS before.
For more information about AWS Control Tower accounts, see About AWS accounts in AWS Control Tower.
Make sure you are not running the AWS CodePipeline pipeline for AWS Landing Zone during this transition. On the AWS Management Console, on the AWS-Control-Tower-Pipeline page, choose Disable transition between the Source stage and the Build stage in the AWS Landing Zone pipeline.