Design an AWS (or Azure/GCP) landing zone for a regulated company with 50 product teams.
Short answer
Multi-account (subscription/project) structure by environment and sensitivity, central identity with SSO and least-privilege roles, hub-and-spoke networking with controlled egress and on-prem connectivity, organization-wide guardrails as code, centralized immutable logging and security tooling, budgets and tagging, and automated account vending.
Detailed answer
- Structure: OUs for Security (log archive, audit), Infrastructure (network hub, shared services), Workloads (prod, non-prod), Regulated (PCI/sensitive), Sandbox.
- Identity: IAM Identity Center with corporate IdP; permission sets per role; break-glass accounts; no IAM users.
- Network: Transit Gateway hub, inspection VPC with firewall, centralized egress, private DNS, Direct Connect + VPN backup; IP plan.
- Guardrails: SCPs (region restriction, protect logging, deny disabling GuardDuty), Config conformance packs, mandatory encryption.
- Security: GuardDuty, Security Hub, Macie organization-wide; delegated admin in security account.
- Logging: CloudTrail org trail and Config to log archive with Object Lock.
- Cost: tag policies, budgets per account, CUR to analytics.
- Vending: Account Factory (Terraform) with baselines in minutes.
Architecture diagram
flowchart TB ORG[AWS Organization] --> SEC[Security OU: log archive, audit] ORG --> INF[Infrastructure OU: network hub, shared services] ORG --> WL[Workloads OU: prod / non-prod accounts] ORG --> REG[Regulated OU: PCI accounts] WL --> HUB[Transit Gateway hub + inspection] REG --> HUB HUB --> ONP[On-premises via Direct Connect]
What the interviewer expects
Coverage of identity, network, guardrails, logging, cost and automation with regulated-data isolation.
Common mistakes to avoid
Single account for everything, overlapping CIDRs, manual account creation, logs writable by workload accounts.