Launching Control Tower

AWS Landing Zone

The Landing Zone is the start URL for users to access the organization's AWS accounts.

thoughtbot uses Control Tower to build a Landing Zone implementing security best practices and reliable workload isolation. This provides a quick starting point for a multi-account setup while still allowing for significant customization and expansion later.

Rather than managing individual IAM users, we use AWS SSO to manage users centrally and integrate with existing identity stores like a Google or Microsoft user directory.

We use Customizations for Control Tower to configure account baselines and deploy service control policies.

Getting Started

1. Allow IAM administrators to manage billing following the IAM billing guide.

2. Create an IAM user following the Control Tower IAM user guide. Create a user with programmatic and console access. Save your password and access key.

3. Write down your AWS account ID.

4. Sign out of the root user account and sign in as the newly-created IAM user.

5. Enable Cost Management by following the AWS Cost Management guide. This will allow you to see your costs broken down by service, tags, and account.

6. Deploy your landing zone (steps below follow the Control Tower getting started guide)

   1. Create shared account emails for logs and audit accounts: AWS Guide

   2. Configure and launch your Landing Zone: AWS Guide

   3. Review and set up the landing zone: AWS Guide

      1. You can use the default names for OUs and foundational accounts.

      2. Enable encryption settings using KMS. You will need to create a new symmetric, single-region key. When prompted for an alias, enter control-tower.

         1. Edit the policy for the KMS key you created to grant permissions that allow AWS CloudTrail and AWS Config to use the chosen KMS key. You can use the following statement:

         2. { "Sid": "CloudTrail and AWS Config to encrypt/decrypt logs", "Effect": "Allow", "Principal": { "Service": [ "cloudtrail.amazonaws.com", "config.amazonaws.com" ] }, "Action": [ "kms:GenerateDataKey", "kms:Decrypt" ], "Resource": "*" }

      3. Select the key you created and launch your landing zone. If you receive quota-related errors during this step for a freshly-created account, wait at least an hour and try again. It may also take several hours for your landing zone to be fully deployed. While your landing zone is deploying, you will receive an email requesting email confirmation. You must confirm your email before the landing zone will complete successfully.

7. Congratulations! You now have an AWS Landing Zone managed by Control Tower.

You are now ready to launch Customizations for Control Tower.