Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Step 4. Call your blueprint to create a customized account

Focus mode
Step 4. Call your blueprint to create a customized account - AWS Control Tower

When you follow the Create account workflow in the AWS Control Tower console, you'll see an optional section where you can enter information about the blueprint you'd like to use for customizing accounts.

Prerequisites

You must set up your customization hub account and add at least one blueprint (Service Catalog product) before you can enter that information into the AWS Control Tower console and begin to provision customized accounts.

Create or update a customized account in the AWS Control Tower console.
  1. Enter the account ID for the account that contains your blueprints.

  2. From that account, select an existing Service Catalog product (existing blueprint).

  3. Select the proper version of the blueprint (Service Catalog product), if you have more than one version.

  4. (Optional) You can add or change a blueprint provisioning policy at this point in the process. The blueprint provisioning policy is written in JSON and attached to an IAM role, so it can provision the resources that are specified in the blueprint template. AWS Control Tower creates this role in the member account so that Service Catalog can deploy resources using AWS CloudFormation stack sets. The role is named AWSControlTower-BlueprintExecution-bp-xxxx. The AdministratorAccess policy is applied here by default.

  5. Choose the AWS Region or Regions in which you wish to deploy accounts based on this blueprint.

  6. If your blueprint contains parameters, you can enter the values for the parameters into additional fields in the AWS Control Tower workflow. The additional values may include: a GitHub repository name, a GitHub branch, an Amazon ECS cluster name, and a GitHub identity for the repository owner.

  7. You can customize accounts at a later time by following the Account update process, if your hub account or blueprints are not yet ready.

For more details, see Create a customized account from a blueprint.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.