An AWS landing zone is the prepared, multi-account AWS environment that workloads move into. In AWS's words, "a landing zone is a well-architected, multi-account AWS environment that is scalable and secure" (AWS Prescriptive Guidance). It sets identity, logging, security controls and account structure once, so every new account and workload starts from the same baseline.
What a landing zone usually contains
| Part | What it does |
|---|---|
| Multiple AWS accounts, grouped in AWS Organizations | Separates production, test, logging and security, so a mistake in one account stays there |
| Central sign-in (IAM Identity Center) | One place to grant and remove people's access across accounts |
| Log archive and audit accounts | Keep CloudTrail and configuration logs where workload teams can't alter them |
| Controls (guardrails) | Preventive rules (service control policies) and detective rules (AWS Config) applied to every account |
| Account vending | New accounts created with the baseline already applied |
Ways to build one
- AWS Control Tower orchestrates AWS Organizations, AWS Service Catalog and IAM Identity Center "to build a landing zone in less than an hour" (AWS). There is no additional charge for Control Tower itself; you pay for the services it uses, mainly AWS Config and CloudTrail.
- Landing Zone Accelerator on AWS is an AWS solution aimed at "highly-regulated workloads and complex compliance requirements". AWS states that it "will not, by itself, make you compliant", and its sample configuration costs about $430 a month in underlying services before any workload runs.
- Your own infrastructure as code, for teams that need a design Control Tower doesn't fit.
Practical limits
- It is a foundation, not compliance. Controls catch drift, but the firm still decides who has access, what is logged and how long logs are kept.
- Running costs scale with activity. AWS warns that short-lived workloads can raise AWS Config costs, because every recorded change is charged.
- Retrofitting is harder than starting right. Moving live workloads into new accounts later means re-pointing networks, access and backups.
For UK financial services firms, a landing zone is where evidence starts: central logs, named administrators and consistent controls are what an auditor or the FCA will ask about after an incident. It also makes least-privilege IAM far easier to enforce. For where the landing zone fits in a migration plan, see AWS Migration Hub Is Closed: What to Use Instead. Designing and building it is the first stage of a Yemberzal cloud migration.