Skip to content
Cloud Governance Tools

AWS Control Tower guardrails are now called controls, and they come in three types: preventive, detective and proactive

AWS Control Tower documentation says it is moving from the term guardrail to the term control and treats them as synonyms. Preventive controls use SCPs and RCPs, detective controls use AWS Config rules, and proactive controls use CloudFormation hooks. Each type has a different reach, read 16 Nov 2026.

See the ranking ยท All guides

A control is one plain-language rule applied to an entire OU

AWS documentation defines a control as "a high-level rule that provides ongoing governance for your overall AWS environment" and says it applies to an entire organizational unit. Every account in the OU is subject to it. AWS notes that the old term, guardrail, still appears in the console, blogs and videos, and calls the two terms synonymous.

Controls fall into three groups by guidance. Mandatory controls apply to every OU, are applied when the landing zone is set up, and cannot be deactivated. Strongly recommended and elective controls can be changed at any time from the console or the APIs.

Each control type is a different AWS mechanism with a different reach

The reach column is the part buyers miss. A preventive control covers accounts that are not enrolled in Control Tower. A detective control does not. AWS also states that proactive controls cannot evaluate secure strings and secrets, because those values are not resolved before they reach the hook.

TypeImplemented withWhen it actsStatus valuesDocumented limit
PreventiveService control policies and resource control policiesDenies the actionenforced or not enabledApplies to all member accounts under the OU, enrolled and unenrolled
DetectiveAWS Config rulesAfter the resource existsclear, in violation or not enabledApplies to enrolled accounts only; only in supported Regions
ProactiveCloudFormation hooks (preCreate and preUpdate)Before a stack operation creates or updates a resourceNot stated in the page readMay not affect requests made through the console, APIs, SDKs or other IaC tools

Three mandatory controls are detective, not preventive

AWS states that the mandatory controls have preventive behavior except three that are detective. The three are Detect Public Read Access Setting for Log Archive, Detect Public Write Access Setting for Log Archive, and Detect whether shared accounts under the Security organizational unit have AWS CloudTrail or CloudTrail Lake enabled. The last one is marked for removal in landing zone 4.0.

The management account is exempt on purpose. AWS says the root user and administrators in the management account can perform work that controls would otherwise deny, to keep that account from becoming unusable. Actions there are still logged in the log archive account.

Configurable controls take parameters, including exempted principals and actions

AWS shows that a control can be enabled on an OU through CloudFormation with the resource type AWS::ControlTower::EnabledControl, a control identifier and a target OU identifier. Its example passes three parameters: AllowedRegions, ExemptedPrincipalArns (a role such as arn:aws:iam::*:role/ReadOnly) and ExemptedActions (for example logs:StartQuery).

These parameters are the native exception route for catalog controls. They are set per OU, so an exemption covers every account in that OU. The page read gives no expiry field for them: none found on 10 Nov 2026. Guardrail exceptions and waivers compares this with the Azure and Google Cloud routes.

Where Control Tower controls stop and plain SCPs begin

Control Tower controls come from an AWS-owned catalog. A rule outside the catalog, such as Deny access outside approved Regions, is written as a service control policy and attached to the OU yourself. The mechanism pages explain evaluation and limits, and how SCP evaluation works covers the allow-list and deny-list models.

To compare Control Tower with other products on safe rollout, see the AWS Control Tower platform page. For the general split between the three types, see preventive vs detective controls and the proactive control glossary entry.

Sources

  1. AWS Control Tower: how controls work, read 10 Nov 2026
  2. AWS Control Tower: about controls, read 16 Nov 2026
  3. AWS Control Tower: preventive controls, read 10 Nov 2026
  4. AWS Control Tower: detective controls, read 10 Nov 2026
  5. AWS Control Tower: proactive controls, read 10 Nov 2026
  6. AWS Control Tower: mandatory controls, read 10 Nov 2026
  7. AWS Control Tower: enable controls with CloudFormation, read 10 Nov 2026

Last reviewed 16 Nov 2026.