Introduction

Most AWS landing zone tutorials stop after the initial setup click. This guide continues past that point, walking through a governed multi-account environment built with AWS Control Tower. Every account has a single responsibility, guardrails are enforced through Service Control Policies, and networking is centralized in one account before being shared with the others. The setup was tested in a real organization, including the missteps: an SCP that broke DNS, an allow-list policy that accidentally permitted everything, and an AWS Resource Access Manager share that failed for 40 minutes. Those fixes are included here so you can avoid the same delays.

What Happened

The article outlines a seven-account landing zone spread across five Organizational Units. The Management account governs the organization but runs no workloads. Security hosts the Audit and Log Archive accounts. Infrastructure owns the Network account and all VPCs. Deployments contains the Build account for CI/CD and container images. Workloads holds Dev and Production for running applications.

Each account follows strict "must not" rules enforced by deny-based SCPs. The Network account cannot run applications or CI/CD, while Dev and Production cannot create their own networking or push container images. Control Tower provisions the accounts and enables IAM Identity Center for single sign-on, removing the need for IAM users and long-lived access keys.

Networking relies on VPC sharing through AWS Resource Access Manager. The Network account creates three VPCs—one each for Dev, Production, and Build—and shares the relevant subnets with the corresponding workload accounts. This keeps environments isolated without requiring transit gateways or peering connections at the outset.

Real errors are documented as well. A region-lock SCP that included Route 53 broke DNS because Route 53 API calls route through us-east-1. An allow-list SCP attached alongside full access had no effect, leaving the Workloads OU unrestricted. RAM sharing failed until trusted access was reset using the AWS CLI.

Why This Matters

Separating accounts by responsibility creates hard boundaries for IAM permissions, billing, service quotas, and the blast radius of mistakes. When development, production, networking, and CI/CD share one account, permissions inevitably bleed across environments. Organizational Units let you apply guardrails to groups of accounts at once, so new accounts inherit the same protections automatically.

Cost is another factor. Three NAT gateways can run around $150 per month plus data transfer charges, making cleanup essential for learning environments. Deny-based SCPs are easier to maintain than allow-lists because every new service does not require a policy rewrite. Testing policies immediately after attachment catches misconfigurations before they affect production workloads.

Key Takeaways

  • Use seven accounts across five OUs: Management, Audit, Log Archive, Network, Build, Dev, and Production.
  • Prefer deny-based SCPs over allow-lists; allow-lists combined with full access effectively permit everything.
  • Exclude global services such as IAM, STS, and Route 53 from region-lock SCPs, or you will break DNS and identity lookups.
  • Centralize VPCs in a Network account and share subnets with workload accounts through AWS RAM.
  • Test every SCP with CLI dry-run commands right after attaching it.
  • Delete the default aws-controltower-VPC from new accounts and set Account Factory private subnets to zero to avoid unused resources.
  • Expect Control Tower setup to take roughly 35 minutes, and budget about two hours of hands-on work.

Conclusion

This foundation prepares the environment for the next parts of the series, which cover setting up a Build account with CodeCommit, ECR, and CodeBuild, then deploying applications on ECS across Dev and Production. If you build this landing zone to learn, remember to delete NAT gateways between sessions or run the cleanup steps to avoid surprise charges. With the right account boundaries, SCPs, and shared networking in place, you will have a multi-account AWS environment that is easier to secure, audit, and operate.