Step 1. Launch the stack - AWS Control Tower

Step 1. Launch the stack

The AWS CloudFormation template in this section deploys Customizations for AWS Control Tower (CfCT) in your account.

Note

You are responsible for the cost of the AWS services used while you run CfCT. For more details, see Cost.

  1. To launch Customizations for AWS Control Tower, download the template from GitHub and then launch it from AWS CloudFormation.

  2. The template launches in the US East (N. Virginia) Region by default. To launch CfCT in a different AWS Region, use the Region selector in the console navigation bar.

    Note

    CfCT must be launched in the same Region and account where you deployed your AWS Control Tower landing zone, which is your home Region.

  3. On the Create stack page, verify that the correct template URL shows in the URL text box and choose Next.

  4. On the Specify stack details page, assign a name to your CfCT stack.

  5. Under Parameters, review the following parameters and modify them in the template, if necessary.

    Pipeline Configuration
    Parameter Default Description
    Pipeline Approval Stage No

    Choose whether to change the pipeline configuration from the default automated approval stage to a manual approval stage. For more information, see CfCT customization guide.
    Pipeline Approval Email Address

    <Optional Input>

    The email address for approval notifications. To use this parameter, you must set the Pipeline Approval Stage parameter to Yes.
    AWS CodePipeline Source Amazon S3

    The source for AWS CodePipeline to help you select where to store and configure the CfCT customizations.
    AWS CodeCommit Setup
    Parameter Default Description
    Existing CodeCommit Repository? No

    Choose whether to use an existing CodeCommit Git repository. If you choose Yes, you must set the CodePipeline Source parameter to AWS CodeCommit.
    CodeCommit Repository Name custom-control-tower-configuration

    The Git repository name. To use this parameter, you must set the AWS CodePipeline Source parameter to AWS CodeCommit. This name is used to create a new Git repository, and must be unique. If you provide the name of an existing Git repository, you must set the Existing CodeCommit Repository? parameter to Yes and enter the exact name of that repository.
    CodeCommit Branch Name main

    The Git branch where the customization package is stored. Git repositories can have many branches. This is the default name given to the branch in the Git repository. To use this parameter, you must set the CodePipeline Source parameter to AWS CodeCommit.
    AWS CloudFormation StackSets Configuration
    Parameter Default Description
    Region Concurrency Type PARALLEL

    Select the concurrency type of deploying StackSets operations in Regions. This setting is applicable for create, update, and delete workflows. Other allowed value is SEQUENTIAL.
    Max Concurrent Percentage 100

    The maximum percentage of accounts in which to perform this operation at one time. The max allowed value is 100. For more information, refer to Stack Set operation options.

    Failure Tolerance Percentage 10

    The percentage of accounts, per Region, for which this stack operation can fail before AWS CloudFormation stops the operation in that Region. The minimum allowed value is 0 and max allowed value is 100. For more information, refer to Stack Set operation options.

  6. Choose Next.

  7. On the Configure stack options page, choose Next.

  8. On the Review page, review and confirm the settings. Be sure to check the box acknowledging that the template will create AWS Identity and Access Management (IAM) resources.

  9. Choose Create stack to deploy the stack.

    You can view the status of the stack in the AWS CloudFormation console in the Status column. You should see a status of CREATE_COMPLETE in approximately 15 minutes.