Skip to main content
In this lesson we walk through AWS Organizations and AWS Control Tower — how they relate, how to create Organizational Units (OUs), and how Control Tower builds a governed multi-account landing zone on top of Organizations. This guide assumes you have console access to your AWS Organization (the Management account) and permission to view and modify organizational units and Control Tower settings.
Use the Management account to administer AWS Organizations and to launch Control Tower. If you prefer automation, many steps shown here can be performed using the AWS CLI, AWS SDKs, or Infrastructure-as-Code tooling (for example, Terraform with the AWS provider).

Overview: Organizations vs Control Tower

  • AWS Organizations provides the foundational multi-account structure: a Root, a Management account, and Organizational Units (OUs) to group member accounts.
  • AWS Control Tower builds on Organizations to deliver a preconfigured “landing zone” with centralized governance, guardrails, account provisioning, and centralized logging.

Open AWS Organizations and create an OU

  1. Open the AWS console and search for AWS Organizations, then select it.
  2. If this is your first time, you may see an introductory page. Open the left panel and choose AWS accounts to view your organization structure.
  3. You will see the top-level Root and the Management account for the organization. The Management account administers the organization.
  4. To create an OU:
    • Select the Root.
    • From the Actions menu choose Create organizational unit (or Create new).
    • Provide a name (for example, testing) and create it.
An OU is a container to group AWS accounts so governance, guardrails, and policies can be applied consistently.
A screenshot of the AWS Organizations console showing a hierarchy of organizational units (Root, Security, Testing) and a management account entry. The top navigation and CloudShell/footer are also visible.
You should now see the OU you created under the Root alongside the management account.
In production environments, member accounts are typically placed inside OUs. This demo uses OUs as structural examples and does not cover adding member accounts; use Account Factory or the Organizations API to provision member accounts into OUs.

Open and prepare AWS Control Tower

Return to the console and open AWS Control Tower. Control Tower uses your Organization to deploy a multi-account landing zone with security, governance, and logging configured. Control Tower setup builds a landing zone that typically includes:
  • A Security OU that contains centralized logging and auditing accounts.
  • A Log Archive account and an Audit account for centralized logs and audit access.
  • Guardrails (Controls) from the Controls catalog which can be preventive, detective, or proactive.
Before enabling Control Tower, watch for an AWS Config organization-wide setup conflict.
If you have organization-wide AWS Config enabled in the same region, Control Tower may refuse to enable there. Workarounds:
  • Choose a different home region for Control Tower (for example, US East (N. Virginia) (us-east-1)), or
  • Disable the organization-wide AWS Config setup in that region before enabling Control Tower.
If Control Tower cannot enable in the chosen region, the console will display a message explaining the issue and suggesting remediation.
A screenshot of the AWS Control Tower console showing a notice that the AWS environment is not ready for Control Tower setup, with instructions to unsubscribe the organization from AWS Config and a "Recheck" button. The message also says only one AWS Control Tower environment is permitted per organization.

Control Tower setup flow

When you begin Control Tower setup you’ll move through several steps:
  1. Setup preference — choose the type of environment. For a full landing zone, select the complete environment.
  2. Home region — select the primary region for the Control Tower landing zone (us-east-1 is a common choice).
  3. Organizational units — Control Tower will present foundational OUs (e.g., Security, Sandbox). Choose which OUs to create or manage.
Control Tower will show the OUs it intends to create or manage. In many landing zones the Security OU is used for centralized logging and auditing.
A screenshot of the AWS Control Tower setup page in the AWS console. It shows organizational units (Security marked Created, Sandbox Not created) with Cancel, Previous and Create OUs buttons.

Configure service integrations

Next is the Configure service integration step. Here you select which AWS services to integrate and choose the default OU for those integrations. By convention, the Security OU is often chosen as the default OU so logging, auditing, and security-related integrations are centralized.
A screenshot of the AWS Control Tower web console showing the "Configure Service integrations — optional" setup page, with the left stepper highlighting Step 3 and a form to select the Default OU for service integrations. The browser top bar and account name (CloudWithDjango-Org) are visible.

Centralized logging with AWS CloudTrail

For centralized logging, enable AWS CloudTrail centralized logging. Control Tower will ask you to designate a CloudTrail administrator account. Best practice is to create a dedicated CloudTrail administrator account separate from the Management account. This account will hold centralized CloudTrail logs centrally and securely.
  • Create the CloudTrail administrator account by providing an email and account name.
  • Ensure the account status is Active before proceeding.
A screenshot of the AWS Control Tower console showing the "Enable AWS CloudTrail" option for centralized logging, with a CloudTrail administrator account ID and an "Active" status. The browser header and account/organization name are visible across the top.

Review and enable Control Tower

Review the configuration summary and enable AWS Control Tower. Building a landing zone can take significant time (the console often shows an estimated duration, for example ~35 minutes). Monitor progress in the Control Tower console and wait for the setup to complete. After setup, Control Tower governs your multi-account environment, using Organizations for account/OUs and applying guardrails across accounts.

Inspect Organization and Controls in Control Tower

Use the Control Tower organizational and resources views to inspect the OUs, accounts, and the status of controls and resources created by Control Tower.
A screenshot of the AWS Control Tower web console in a browser. It shows the Organization page with the left navigation menu and a resources table listing organizational units and control statuses.
Control Tower includes a Controls catalog. Controls are governance rules (preventive, detective, or proactive) you can enable to enforce compliance and best practices across accounts and OUs. The Control Catalog lists available controls and indicates which are enabled.
A screenshot of the AWS Control Tower web console showing the Controls library page, with a left navigation menu and a list of the "Top 5 enabled controls." The right panel displays control behavior statistics (showing "69 Preventive") and related details.

Provision accounts with Account Factory

Account Factory is the Control Tower feature for provisioning new accounts in a standardized, governed manner. Define account configuration templates (networking, SSO settings, tags, etc.) so newly provisioned accounts inherit required settings and guardrails.
A screenshot of the AWS Control Tower console open to the "Account factory" page, showing a "Create account" button and network configuration settings for provisioning accounts. The left sidebar displays navigation items like Dashboard, Organization, and Controls.

Landing Zone settings and governance

From the Control Tower dashboard, review your Landing Zone settings. These settings display:
  • The Control Tower version
  • The Home region (primary region for Control Tower, e.g., US East (N. Virginia) — us-east-1)
  • The list of governed regions and enabled services (for example, AWS CloudTrail)
The landing zone is the standardized, governed foundation for a multi-account AWS environment. Use Control Tower to maintain consistent governance across your organization.
A screenshot of the AWS Management Console showing the AWS Control Tower "Landing zone settings" page, with a Details panel listing current version, home region (US East N. Virginia), and service enablement statuses like AWS CloudTrail. The left sidebar displays Control Tower navigation items such as Dashboard, Organization, and Controls.

Quick troubleshooting and best practices

  • If Control Tower setup fails due to AWS Config, either pick a different home region or remove organization-wide AWS Config in the target region.
  • Use a dedicated CloudTrail admin account to isolate audit logs.
  • Use OUs to group accounts by lifecycle or responsibility (for example, Security, Sandbox, Production).
  • Automate account provisioning via Account Factory or the AWS Organizations API to keep accounts compliant at creation.
That concludes this demo lesson on AWS Organizations and AWS Control Tower.

Watch Video