Definition of the cloud landing zone
A cloud landing zone (zone d’atterrissage in French) is the foundation an organisation sets up with a cloud provider to receive its applications. It brings together the account hierarchy, identities and access, the network, security controls and logging.
The term comes from the usage of cloud providers. Each gives its own definition in its documentation, consulted on 12 November 2026.
| Documentation | Original wording |
|---|---|
| AWS Control Tower, user guide | “a well-architected, multi-account environment” |
| Microsoft, Cloud Adoption Framework | “architecture for governing, securing, and scaling a multi-subscription Azure environment” |
| Google Cloud, Cloud Architecture Center | “a modular and scalable configuration” |
Google Cloud also uses “cloud foundation” as a synonym.
The components of a foundation
The three documentations each break down the foundation in their own way, around the same families.
- The resource hierarchy: accounts and organisational units at AWS, subscriptions and management groups at Azure, folders under an organisation resource at Google Cloud.
- Identities and access.
- The network, with interconnection to existing systems.
- Security controls. AWS calls them “controls”, sometimes “guardrails”, and distinguishes three kinds: preventive, detective, proactive.
- Logging and monitoring.
- Distributing accounts to teams: Account Factory in AWS Control Tower, “subscription vending” at Microsoft.
Microsoft separates the platform landing zone, which carries governance and shared resources, from “workload landing zones”, where teams deploy their applications.
This foundation can be described through infrastructure as code: Microsoft’s accelerators fall under it, as does the foundation example published by Google Cloud.
When to prepare it: Google Cloud’s recommendation
Google Cloud recommends building the landing zone before deploying the first enterprise application. Its text puts forward three reasons: a foundation designed to be secure, the applications’ network and the tools for internal cost allocation.
This last point touches on FinOps. The FinOps Foundation framework bases cost allocation on the account structure and on tags, two choices made at the time of the foundation.
The limitations of a landing zone
A landing zone cannot be carried over from one provider to another, since it is made of each one’s objects.
It is not fixed. According to Google Cloud, the first version is often not the last, and applications with particular compliance requirements may justify a second landing zone. AWS Control Tower calls “drift” the gap between the accounts and best practices, which its controls aim to contain.
Finally, the foundation frames the environment: the design of each application remains with its team.
Landing zone, zone, internal platform, zero trust: not to be confused
- A geographical zone is something else: Google Cloud specifies that a landing zone is neither a zone nor zonal resources.
- The internal developer platform, the subject of platform engineering, offers teams self-service delivery capabilities. The landing zone provides them with governed accounts.
- Zero trust is a security model, according to which the identities and the network of a landing zone can be configured.
Textbook case: the foundation of a construction group
Take a construction group that wants to host its worksite tracking applications with a cloud provider. The infrastructure team first settles the hierarchy: one account per application and per environment, one account reserved for logs, another for the network. Identities come from the group’s directory. A preventive control refuses any internet-exposed resource outside the network account.
When a subsidiary requests an environment, it receives an account created from the template, already connected to the logs and subject to the common rules.
For the place of the landing zone in a programme, see our page on cloud migration.