Cloud Landing Zones

The multi-account or multi-project foundation of identity, networking, security, logging and guardrails that every workload deploys into, with AWS, Azure and Google Cloud implementations.

What it is

A landing zone is a pre-configured, secure, scalable cloud foundation: account/subscription/project structure, identity and access, network topology, security baselines, logging, guardrails and automation for creating new environments. Workload teams get "vending machine" environments that are compliant by default.

Typical structure

flowchart TB
  ORG[Organization root] --> SEC[Security OU<br/>log archive, security tooling]
  ORG --> INF[Infrastructure OU<br/>network hub, shared services]
  ORG --> WL[Workloads OU]
  WL --> PROD[Prod OU] --> A1[App A prod]
  WL --> NONPROD[Non-prod OU] --> A2[App A dev/test]
  ORG --> SBX[Sandbox OU<br/>budget-capped experiments]
  ORG --> PCI[Regulated OU<br/>PCI / sensitive data]
  INF --> HUB[Network hub<br/>Transit GW / hub VNet / Shared VPC]
  A1 & A2 --> HUB

Building blocks

Area Decisions
Resource hierarchy Account/subscription/project per app per environment; OUs/management groups/folders by environment and compliance
Identity Central IdP SSO, role/permission sets, break-glass accounts, no long-lived keys
Network Hub-and-spoke, IP address plan (non-overlapping CIDRs), egress control, private DNS, on-prem connectivity
Security Guardrails (SCPs/Azure Policy/Org Policy), centralized threat detection, encryption defaults, key management
Logging Org-wide audit trails to an immutable log archive account; central SIEM
Cost Mandatory tags/labels, budgets, cost allocation
Automation Account vending via IaC pipelines; baseline drift detection

Provider implementations

AWS Azure Google Cloud
Hierarchy Organizations, OUs, accounts Management groups, subscriptions Organization, folders, projects
Accelerator Control Tower + Account Factory (for Terraform), Landing Zone Accelerator Azure landing zones (Cloud Adoption Framework), ALZ Bicep/Terraform modules Google Cloud setup, Cloud Foundation Fabric (FAST)
Guardrails SCPs, RCPs, Config rules Azure Policy Organization Policy Service
Network hub Transit Gateway / Cloud WAN Hub VNet or Virtual WAN Shared VPC / Network Connectivity Center

Architect-level considerations

[!EA] The landing zone is where enterprise architecture standards become enforceable: encode principles as policies (allowed regions, encryption required, no public buckets) instead of documents.

[!WARNING] IP address planning and the account/project structure are expensive to change later. Plan for growth (hundreds of accounts, multiple regions, mergers).

Interview questions and answers

Why one account per workload per environment?

It is the strongest isolation boundary for security, quotas, blast radius and cost attribution, and lets you apply different guardrails to prod and non-prod.

How do developers get a new environment?

Through an account/project vending pipeline: a request (often via a portal or pull request) triggers IaC that creates the account, applies baselines, networking, budgets and access, usually within minutes to hours.