Kanji
・Cloud engineer / freelance ・Born in 1993 ・From Ehime / Living in Shibuya, Tokyo ・5 years AWS experience Profile details
Table of Contents
When governing a multi-account AWS environment for an enterprise or production system, you rarely get to start from a completely empty greenfield organization. More often, dozens of AWS accounts are already running workloads independently. When I led a project to introduce AWS Control Tower (CT) into an existing AWS Organizations environment and incrementally enroll brownfield accounts into governed OUs, I ran into two painful operational traps.
The first trap was duplicate CloudTrail management event charges alongside an unexpected spike in AWS Config recording costs . Before adopting CT, our management account already had an organization-wide CloudTrail trail recording management events. Because we left CT’s managed organization trail option enabled during setup, every account began recording management events twice. While the first copy of management events in CloudTrail is free, additional copies cost $2.00 per 100,000 events . Worse yet, CT deployed AWS Config recorders across all governed regions with all resource types enabled; in accounts running high-churn EKS and ECS workloads where ENIs attached and detached every minute, our monthly AWS Config Configuration Item bill ( $0.003 per item) multiplied several times over the following month.
$2.00
$0.003
The second trap was pre-check failures and batch concurrency limits when enrolling existing accounts ( Enroll Account / RegisterOrganizationalUnit ) . When we moved an existing account into a governed OU and triggered enrollment, it rolled back with Account enrollment failed: Existing AWS Config recorder or delivery channel found . Even though a team member had clicked “Disable” in the Tokyo region console years ago, leftover default Config recorders and delivery channels still existed in us-east-1 and other regions, causing CT’s baseline StackSet to fail. Furthermore, when running RegisterOrganizationalUnit on an OU containing more than 10 accounts, we hit internal 5-account batch processing limits and had to build an automated pre-flight cleanup script to purge legacy Config recorders across all regions and provision the AWSControlTowerExecution role before enrollment.
Enroll Account
RegisterOrganizationalUnit
Account enrollment failed: Existing AWS Config recorder or delivery channel found
default
us-east-1
AWSControlTowerExecution
With the release of AWS Control Tower Landing Zone 4.0 in late 2025, AWS redesigned the platform specifically to address these real-world pain points. Instead of forcing an all-or-nothing monolithic setup, Landing Zone 4.0 introduces modular, selective service integration, a Controls-Only experience (letting you use managed controls without deploying shared CT accounts), and dedicated per-service S3 buckets in the Log Archive account (separating CloudTrail and AWS Config logs).
In this guide, based on Landing Zone 4.0 specifications and hands-on operational lessons, I systematically cover the 5 pre-adoption checks, the 5 guardrail types in AWS Control Catalog (SCPs, RCPs, Declarative Policies, Hooks, and Config), account automation comparing AFT vs. CfCT, and day-2 operations for drift remediation and Config cost control.
▲ Enterprise AWS Control Tower (Landing Zone 4.0) Architecture: Multi-Account Governance, 5 Guardrail Mechanisms, Separated Log Buckets & AFT Automation
AWS Control Tower orchestrates multi-account AWS environments built on AWS Organizations, automating landing zone provisioning, guardrail enforcement, and account vending. There is no additional fee for AWS Control Tower itself; you pay only for the underlying AWS resources enabled (such as AWS Config, CloudTrail, S3, and KMS).
Control Tower governance operates across three dimensions: Preventive Controls (blocking disallowed actions before execution), Proactive Controls (validating resource configurations prior to CloudFormation provisioning), and Detective Controls (asynchronously auditing resource states after changes occur).
Whether deploying a new environment or upgrading an existing one, understanding the four structural changes introduced in Landing Zone 4.0 is essential:
aws-controltower-logs-*
NotificationForwarder
Before enabling Control Tower in a new or brownfield organization, verify these five foundational criteria during the design phase.
Control Tower must be enabled in the AWS Organizations Management Account. If you procure AWS through a billing reseller or distributor, verify whether you have administrative access to the Management Account and permissions to enable all features ( All features ), SCPs, RCPs, and Declarative Policies. For details on contract patterns, see [Design Guideline] AWS Organizations .
All features
If you already operate a custom Landing Zone built with Terraform or CloudFormation StackSets, migrating everything into CT’s opinionated OU and logging structure used to require heavy refactoring. With Landing Zone 4.0 selective integration or Controls-Only mode , you can retain your existing log aggregation buckets and CloudTrail trails while leveraging Control Tower strictly for AWS Control Catalog guardrails and Account Factory for Terraform (AFT).
Whereas regions such as Hyderabad ( ap-south-2 ), Melbourne ( ap-southeast-4 ), and Milan ( eu-south-1 ) were unsupported in 2023, AWS Control Tower now supports virtually all commercial AWS Regions, including newer opt-in regions .
ap-south-2
ap-southeast-4
eu-south-1
ap-northeast-1
ap-northeast-3
us-east-2
us-west-1
us-west-2
ca-central-1
sa-east-1
ca-west-1
mx-central-1
ap-southeast-1
ap-southeast-2
ap-northeast-2
ap-south-1
ap-east-1
ap-southeast-3
ap-southeast-5
ap-southeast-7
eu-central-1
eu-west-1..3
eu-north-1
eu-south-1..2
eu-central-2
me-central-1
il-central-1
af-south-1
Region Deny Best Practice : Even if your workloads run exclusively in Tokyo ( ap-northeast-1 ), global AWS services such as CloudFront, IAM, and Route 53 rely on N. Virginia ( us-east-1 ) , which CT’s Region Deny guardrail automatically exempts. Govern only your active regions (e.g., ap-northeast-1 , ap-northeast-3 , us-east-1 ) and block all other regions via CT’s Region Deny control to prevent unauthorized crypto-mining or shadow IT deployment if credentials are ever compromised.
arn:aws:iam::<Management-Account-ID>:root
AdministratorAccess
Prod
NonProd
Sandbox
Infrastructure
AWSControlTowerBaseline
0
Modern AWS Control Tower governance extends far beyond basic SCPs and Config rules. AWS Control Catalog now unifies five distinct enforcement engines :
aws:PrincipalOrgID
CT.*.PR.*
cfn
CT.*.DT.*
SH.*
AWS::ControlTower::EnabledControl
Rather than clicking controls manually in the console, manage guardrails declaratively using AWS::ControlTower::EnabledControl (or Terraform’s aws_controltower_control ) with AWS Control Catalog global ARNs:
aws_controltower_control
AWSTemplateFormatVersion: "2010-09-09" Description: Enable Control Tower Guardrails on Production OU via Control Catalog ARN Parameters: ProductionOUTargetIdentifier: Type: String Description: ARN of the Production Organizational Unit Default: "arn:aws:organizations::111122223333:ou/o-exampleorgid/ou-xxxx-prodouid" Resources: # 1. Detective Control: Require S3 Bucket Versioning EnableS3VersioningControl: Type: AWS::ControlTower::EnabledControl Properties: ControlIdentifier: !Sub "arn:aws:controlcatalog:${AWS::Region}::control/AWS-GR_S3_VERSIONING_ENABLED" TargetIdentifier: !Ref ProductionOUTargetIdentifier # 2. Parameterized Control: CloudWatch Log Group Retention Check EnableCWLogGroupRetentionControl: Type: AWS::ControlTower::EnabledControl Properties: ControlIdentifier: !Sub "arn:aws:controlcatalog:${AWS::Region}::control/CT.CLOUDWATCH.DT.1" TargetIdentifier: !Ref ProductionOUTargetIdentifier Parameters: - Key: MinimumRetentionTime Value: 90
To automate account vending, custom VPC provisioning, and baseline IAM deployment, AWS provides two official customization frameworks: AFT (Account Factory for Terraform) and CfCT (Customizations for AWS Control Tower) .
aft-account-request
manifest.yaml
aws-guardrails-*
CheckPolicyCompliance
aws-controltower-BaselineConfigRecorder
DriftDetected
MoveAccount
EnabledControlDriftDetected
ResetEnabledControl
SUPPRESSED
Workloads-Special-Compliance
When deploying or modernizing AWS Control Tower across your organization, anchor your architecture on these four practices:
One trade-off that still requires careful calibration in each organization is deciding how aggressively to exclude ephemeral container/serverless resource types from AWS Config recording in non-production OUs versus maintaining 100% configuration history. I am currently refining our baseline AWSControlTowerBaseline overrides alongside Declarative Policies in Landing Zone 4.0 to strike the best balance between monthly Config bills and audit visibility. Start by codifying your core guardrails with EnabledControl in a sandbox OU and testing drift remediation workflows.
EnabledControl
When establishing an AWS cloud landing zone, formulating AWS standardization guidelines strengthens ... [Read more]
Enterprise AWS Config design guide: multi-account organization aggregators, conformance packs, confi ... [Read more]
Enterprise AWS IAM and IAM Identity Center design guide covering Entra ID/Okta SAML SSO, JIT privile ... [Read more]
Master conversation skills with realistic AI phone training and 5-axis feedback. Includes 16-lesson interactive academy and studio AI portraits.
Effortlessly snap receipts for instant AI itemization. Integrated with LINE for seamless group expense tracking and pain-free settlement.
Interactive AI personas (Fortune Teller, Butler, Bartender) host real-time games, challenges, and conversation starters for unforgettable gatherings.
Real-time AI quant analysis of earnings reports, corporate filings, and momentum indicators for global equities and Japanese stocks.
Unbiased healthcare database featuring zero-additive filters and active ingredient cost performance metrics.
Get the complete configuration pack featured in this article: universal AGENTS.md, deterministic hooks.json, Git safety guardrails, and validation scripts tested across Antigravity, Kiro, Claude Code, and Codex.