Skip to content
Cloud Governance Tools

An AWS landing zone starts with mandatory controls on every OU, then adds guardrails OU by OU

An AWS Control Tower landing zone applies mandatory controls to every organizational unit when it is set up, and AWS says they cannot be deactivated. Landing zone 4.0 stopped deploying four CloudTrail controls. This page lists the baseline and the library guardrails that match it, as read on 16 Nov 2026.

See the ranking ยท All guides

AWS documentation defines a landing zone as "a cloud environment that offers a recommended starting point, including default accounts, account structure, network and security layouts". It says Control Tower acts as an orchestration layer over other AWS services to implement the AWS multi-account recommendations, and that one account is not enough for a well-architected environment.

AWS lists the reasons for multiple accounts: security controls, isolation, many teams, data isolation, business process, billing and quota allocation. Each is a reason to attach a different guardrail to a different OU.

Mandatory controls are the fixed baseline, and they use the same exception pattern you would write

AWS says mandatory controls are owned by Control Tower, apply to every OU in the landing zone (with some exceptions for the Security OU), are applied by default at setup and cannot be deactivated, because they protect Control Tower resources.

The reference page prints their policy text. One of them, Disallow changes to Amazon SNS subscriptions and topics managed by AWS Control Tower, uses Sid CTSNSPV1. It denies every action except a list (confirm, get, list, publish, subscribe, unsubscribe and tagging actions) on topics named aws-controltower-CentralizedLoggingNotifications*, and exempts one principal with an ArnNotLike condition on the role AWSControlTowerExecution. That is the same NotAction plus exempt-role shape that the sample SCPs in the library use.

Landing zone 4.0 stopped deploying four CloudTrail controls and removed others

AWS states that from landing zone 4.0 it no longer deploys four controls that protect account trails created in landing zone 2.9 and below: Disallow Configuration Changes to CloudTrail, Integrate CloudTrail Events with Amazon CloudWatch Logs, Enable CloudTrail in All Available Regions, and Enable Integrity Validation for CloudTrail Log File. They stay in force on landing zone versions below 4.0 and are deleted on upgrade.

Two AWS Config aggregator controls are also removed for customers who upgrade with Config integration enabled. If your baseline was written from an older landing zone, the controls on your OUs and the controls in the current catalog may differ.

Seven library entries cover the same ground as the baseline

Each linked page records what the entry blocks, what it breaks and how AWS says to test it. The SCP mechanism page lists the evaluation limits.

Baseline goalLibrary entryMechanism
Keep accounts in the organizationDeny member accounts leaving the organizationSCP
Keep audit trails intactDeny modifications to specific CloudTrail trailsSCP
Keep configuration recording onDeny enabling and disabling AWS ConfigSCP
Keep detection onDeny disabling or modifying Amazon GuardDutySCP
Keep network logsDeny deleting VPC flow logsSCP
Limit RegionsDeny access outside approved RegionsSCP
Encrypt in transitRequire HTTPS for access to resourcesRCP

AWS recommends four OUs, and guardrails attach to each one separately

AWS also recommends at least two accounts, Production and Staging, with distinct controls and policies, governed as separate OUs. Because a control applies to a whole OU, the OU layout decides how finely a guardrail can be aimed. Control Tower supports nested OUs, so a baseline can sit on a parent and exceptions on a child.

OUWho creates itPurpose in AWS's description
SecurityControl Tower, as the first required OUShared security accounts; mandatory controls have some exceptions here
SandboxControl Tower, if you select itSoftware development; for example a fixed spending limit or no link to the production network
InfrastructureYouShared services and networking accounts
WorkloadsYouAccounts that run workloads

Preventive controls reach unenrolled accounts, and detective controls do not

AWS states that preventive controls enabled on an OU registered with Control Tower apply to all member accounts under the OU, enrolled and unenrolled, while detective controls apply to enrolled accounts only. Preventive controls enabled on an OU higher in the tree also apply to unregistered OUs below it. Place the baseline high and the exceptions low. See AWS Control Tower guardrails for the three control types.

Sources

  1. AWS Control Tower: multi-account strategy for your landing zone, read 10 Nov 2026
  2. AWS Control Tower: mandatory controls, read 10 Nov 2026
  3. AWS Control Tower: preventive controls, read 10 Nov 2026
  4. AWS Control Tower: detective controls, read 10 Nov 2026

Last reviewed 16 Nov 2026.