Skip to content
Nubent

/Glossary · Architecture

What is Landing zone?

A landing zone is a secure, well-governed multi-account AWS environment that serves as the foundation for your workloads. It defines account structure, identity, networking, centralized logging, and security controls from the start.

How a landing zone works

A landing zone uses AWS Organizations to group accounts into organizational units such as security, infrastructure, production workloads, and sandboxes. Each workload lives in its own account, which isolates permissions, service quotas, and costs. Service control policies and resource control policies set hard limits that no account can exceed.

Shared services are centralized around that structure: access through IAM Identity Center, CloudTrail and Config logs in a dedicated log archive account, GuardDuty and Security Hub findings in an audit account, and connectivity through Transit Gateway or shared VPCs. New accounts are created with that baseline already applied.

When to build a landing zone

Before a single AWS account ends up holding production, testing, and every team's experiments. You can split things up later, but it costs more. It also makes sense ahead of a security audit or a certification like ISO 27001 or SOC 2, or when several teams start asking for their own accounts.

If you already have a sprawl of accounts created without a standard, a landing zone lets you enroll them gradually and apply common controls. Product work does not have to stop: you design the structure, migrate account by account, and tune the controls with each team.

Best practices and common mistakes

Design organizational units around policies, not the org chart. Keep production and non-production in separate accounts, and define everything as code, whether with AWS Control Tower and Account Factory for Terraform or with your own modules. Get rid of IAM users with long-lived access keys and centralize access in IAM Identity Center.

Common mistakes: running workloads in the management account, applying policies so restrictive that they block teams and lead to manual exceptions, and skipping IP address planning, which later makes it impossible to connect networks across accounts without overlapping ranges.

/FAQ

Questions about Landing zone

Another question? Write to hello@nubent.com and an engineer will answer.

What is the difference between a landing zone and Control Tower?

A landing zone is the concept: a multi-account environment with shared controls and services. AWS Control Tower is a service that automates building and governing a landing zone based on AWS best practices. You can also build one with Terraform without Control Tower.

How many AWS accounts does a company need?

It depends on how many workloads and teams you have. At minimum, plan for the management account, a log archive account, an audit or security account, and separate production and non-production accounts for each major workload. Accounts themselves cost nothing.

What is an SCP in AWS?

A service control policy defines the maximum permissions available to accounts in an organizational unit. It does not grant permissions; it limits them. For example, it can block anyone from disabling CloudTrail or using unapproved regions, including account administrators.

Next step

What should we build next on AWS?

30 minutes with an engineer. Concrete next steps, whether or not you work with us.