A customer security questionnaire arrives, or your first audit request, and someone on the team says "just use AWS Control Tower." If you're the CTO or platform lead who has to agree, the name tells you little about what changes. Control Tower adds accounts, organizational units (OUs), policies and central logging to your organization. It also hands you a versioned landing zone that your team has to keep current.
Before you agree, you need to know what it creates, how it deploys, what its controls enforce, what you maintain and where it stops. All of it applies to landing zone 4.0, which AWS released on November 17, 2025.
What is AWS Control Tower?
AWS Control Tower is an AWS service that sets up and governs a multi-account AWS environment, which it calls your landing zone. It orchestrates AWS Organizations, AWS Service Catalog and IAM Identity Center, applies managed controls to your OUs, creates accounts through Account Factory, and reports compliance on a dashboard.
AWS groups it into four features: the landing zone, controls, Account Factory, and a dashboard that lists provisioned accounts, enabled controls and noncompliant resources by account and OU. In Control Tower's vocabulary, the landing zone is the environment it builds and manages, and it carries a version number. The landing zone as a general concept has its own guide.
Under the hood, AWS Organizations holds the accounts, OUs, service control policies (SCPs) and resource control policies (RCPs). Service Catalog hosts the Account Factory product, and IAM Identity Center handles sign-in.
AWS documents building a landing zone in under an hour, and the console getting-started guide says about 30 minutes. Control Tower itself has no additional charge. You pay for the services it enables, such as AWS Config, AWS CloudTrail and Amazon S3, and the comparison with Organizations breaks down what those services cost.
What does the Control Tower landing zone create in your organization?
A default console setup creates a hub OU with two service integration accounts, mandatory controls, IAM Identity Center groups, and an Account Factory product in the management account. Landing zone 4.0 made most of that optional.
| What it creates | Where | Optional in 4.0? | Your decision |
|---|---|---|---|
| Hub OU (Security OU by default) and an optional Sandbox OU | Directly under the root | The Security OU is no longer required; hub accounts must share one OU directly under the root | Default OU or your own structure |
| CloudTrail administrator account (formerly log archive) with the central log bucket | Hub OU | Yes, with the CloudTrail integration | New account or an existing one, chosen once at setup |
| Config aggregator account (formerly audit) with its own Config bucket | Hub OU | Yes, with the Config integration | Keep it on if you want detective controls and Account Factory |
| IAM Identity Center groups | Management account | Yes (accessManagement) | Its instance or yours; the home Region must match, except an instance in us-east-1 |
AWS Control Tower Account Factory product in Service Catalog | Management account | Needs the Config integration | Console vending or Account Factory for Terraform |
Mandatory controls and the AWSControlTowerExecution role | Registered OUs and enrolled accounts | No, mandatory controls always apply | Which OUs to register |
The Config row is the one to decide on purpose. According to the feature comparison without AWS Config, switching Config off also forces the Security Roles, IAM Identity Center and AWS Backup integrations off. Preventive and proactive controls keep working. Detective controls, OU baselines and Account Factory through Service Catalog stop. I'd keep Config on unless all you want from Control Tower is SCP-based guardrails.
Count accounts before you start. The default setup adds two beyond the management account, but in 4.0 the number follows the integrations you enable, and a controls-only setup needs none.
How Control Tower rolls the baseline out to every account and Region
Control Tower deploys its baseline with AWS CloudFormation StackSets. In the words of How AWS Control Tower works, it "deploys one stack set instance per account and Region." If StackSets are new to you, start with how StackSets roll one template out to many accounts.
With 20 enrolled accounts and 3 governed Regions, a single baseline stack set holds up to 60 stack instances (my arithmetic, not an AWS figure).
Excalidraw diagram loading.
What those stack sets deploy is grouped into baselines: a group of resources and configurations applied to a target. Registering an OU enables AWSControlTowerBaseline on it. Others, such as CentralConfigBaseline and LogArchiveBaseline, are set up once for the landing zone, and ListEnabledBaselines shows what is active.
Governed Regions decide where the instances land. Adding a Region updates the landing zone but not the accounts already in it, so you re-register each OU to extend governance. Leaving a Region ungoverned doesn't block deployments there; it leaves them outside governance. The elective Region deny control closes that gap, and it can never deny your home Region. Applying it to the whole landing zone needs the Config integration; the OU-level version doesn't. Control Tower runs in more than 30 Regions.
Choices you cannot undo after setup
I'd settle the home Region before anything else, because AWS is blunt about it: "After you've selected a home Region, you cannot change it."
- Home Region: permanent for the life of the landing zone.
- Existing accounts as CloudTrail administrator or Config aggregator: you can only designate them during initial setup.
- Governed Regions and Region deny: changeable later, followed by OU re-registration.
Controls (guardrails): what Control Tower blocks, detects and checks
Controls are rules that Control Tower applies to OUs; older material calls them guardrails. Each control has a behavior, which is how it's enforced, and a guidance level, which is how strongly AWS recommends it. The two are independent.
By behavior, there are three kinds:
- Preventive controls are service control policies and RCPs. They block the API call and apply in all Regions.
- Detective controls are AWS Config rules, so they stop when the Config integration is off. They report on existing resources, and only in Regions where Control Tower is supported.
- Proactive controls are CloudFormation hooks. They check a resource before CloudFormation creates it and return PASS, FAIL or SKIP.
By guidance, mandatory controls are always on and can't be changed, while strongly recommended and elective controls are your call. Region deny, for example, is elective and preventive. The Control Catalog holds more than 750 managed controls.
The management account is the exception. AWS Prescriptive Guidance states it plainly: "SCPs (preventive controls) don't have any effect in the management account. The root user and IAM administrators in the management account can perform any action that is denied in an SCP." With the CloudTrail integration on, the organization trail still logs API activity there, but nothing blocks it. AWS Config isn't enabled in the management account by default, so set up a recorder there yourself if you want its configuration history. Keep workloads out of the management account, and administer Control Tower as an IAM Identity Center user instead of root.
The other mistake is editing the SCPs Control Tower created. The Organizations guidance says not to modify or detach them on a registered OU. If someone does, you reset the landing zone or re-register the OU. Your own SCPs share the same room, because an OU in the landing zone holds at most 10 SCPs.
Account Factory: how new accounts arrive already governed
Account Factory is a configurable account template, built on a Service Catalog product named AWS Control Tower Account Factory. It creates an account, or enrolls an existing one, in a registered OU, and the account picks up that OU's baseline and controls. Terraform teams can use Account Factory for Terraform (AFT), where a new account is an account request file and a git push. Account Factory Customization (AFC) applies blueprints to new and existing accounts. The account vending guide compares other ways to vend accounts.
What you maintain after setup: drift, updates and landing zone 4.0
Drift means your organization no longer matches what Control Tower expects, and AWS sorts it into several types. Account drift is the common one: someone moves an account to another OU in the Organizations console instead of through Control Tower. Landing zone drift hits the foundation itself, such as a deleted foundational OU or a missing Control Tower IAM role. Control Tower scans its managed policies daily, and for the landing zone, one call shows your version, the latest available version and the drift status:
aws controltower get-landing-zone \
--landing-zone-identifier arn:aws:controltower:eu-west-1:111122223333:landingzone/EXAMPLE \
--query 'landingZone.[version,latestAvailableVersion,driftStatus.status]' \
--output text
Illustrative output for a drifted landing zone one version behind:
3.3 4.0 DRIFTED
The status is either DRIFTED or IN_SYNC. Don't leave DRIFTED sitting there: while it lasts, the console's Enroll account feature stops working. On version 3.1 or later, ResetLandingZone restores the configuration you set up. It does not upgrade you to the latest version. Below 3.1, you update the landing zone instead, which also resolves drift. A moved member account is fixed by updating the account or re-registering its OU, while a moved shared account needs a landing zone update. Controls inherited from the old OU can also linger and need disabling separately.
New versions are opt-in. You update from the Landing zone settings page, which AWS says takes "a little more than half an hour", and then re-register OUs to bring member accounts along. On 3.1 and later, you can choose which version to move to, and opt-in auto-enrollment applies a registered OU's baselines and controls to any account moved into it.
Beyond the optional integrations in the table, 4.0 also lets you enable controls on an OU without a full landing zone. Landing zone operations also have APIs: aws controltower create-landing-zone --landing-zone-version 4.0 --manifest file://manifest.json launches one from a JSON manifest.
Does AWS Control Tower fit your team, and where does it stop?
AWS Control Tower fits when you want an AWS-supported governance baseline fast and your accounts sort cleanly into OUs. It stops at governance.
It fits when:
- You want logging, access and mandatory controls from one setup run, not from code you write.
- Your multi-account strategy already groups accounts by OU, so registering an OU governs every account in it.
- You need to show a customer or auditor what's enforced, and the dashboard lists enabled controls and noncompliant resources per account and OU.
- You already run an organization, since you can register existing OUs and enroll their accounts.
Where it stops, per the limits and quotas page and the FAQ:
- Console operations: landing zone, baseline and control operations have APIs, but other operations run from the console, and a console change gets no pull request review.
- Scope: it governs accounts. Workload networking, CI/CD and application baselines beyond its own are yours to build.
- Quotas: 10 SCPs per OU, no registering an OU with more than 1000 directly nested accounts, up to 10,000 accounts in the organization, and one operation at a time apart from control and account operations.
- Regions: Canada West (Calgary), Asia Pacific (Malaysia), Thailand, Mexico (Central), New Zealand, Taipei and the European Sovereign Cloud don't support AWS Service Catalog. Account Factory behaves differently there, and AFC isn't available. AFT and CfCT are also unavailable in Europe (Zurich), Europe (Spain) and Asia Pacific (Melbourne). Check the Regional differences page for IAM Identity Center in your intended home Region too.
- Compliance: controls produce evidence, not a certification, and your auditor still assesses them (see landing zones and SOC 2).
If those limits rule it out, the alternatives range from AWS Organizations on its own to landing zones you own as code.
Your next step before choosing
- AWS Control Tower orchestrates Organizations, Service Catalog and IAM Identity Center, and deploys its baseline through StackSets.
- Landing zone 4.0 makes most of the landing zone optional, but AWS Config carries detective controls, OU baselines and Account Factory.
- SCP-based controls skip the management account, so keep workloads out of it.
- You own drift, version updates and the home Region you can't change.
Read next: whether to delegate or own your landing zone, comparing Control Tower with the AWS CDK Landing Zone.
Next step