Cloud reference architecture
AWS landing zone
A multi-account AWS foundation with organization-wide guardrails, centralized logging and a shared network hub.
Design principles
- One account per workload and environment
- Guardrails enforced with SCPs, not documentation
- Logs and security findings aggregated to dedicated accounts
- Accounts vended from code with baselines applied
Components
| Component | Role |
|---|---|
| AWS Organizations | Account hierarchy and service control policies |
| IAM Identity Center | Federated workforce access |
| Log archive account | Immutable CloudTrail and Config history |
| Security tooling account | GuardDuty, Security Hub delegated admin |
| Network hub | Transit Gateway, inspection and egress |
More Cloud architectures
Azure landing zone
Management groups, policy-driven governance and a hub-and-spoke network for Azure subscriptions at scale.
View architectureKubernetes platform architecture
A shared EKS or AKS platform with tenancy, identity, policy, GitOps and observability as platform services.
View architectureHybrid cloud
Connecting data centers and colocation to AWS and Azure with consistent identity, networking and operations.
View architectureAdapt this to your environment
We'll help you apply this pattern to your constraints and existing estate.

