← All cheatsheets

Cloud

Cloud Landing Zones — multi-account structure across AWS, GCP, Azure

A conceptual comparison of how the same landing-zone capabilities — org hierarchy, identity, guardrails, shared networking, central logging, security baseline, tagging, budgets, and workload onboarding — map across AWS, GCP, and Azure, with inspect-first verification commands. Confirm your management/org context before any change; vending a new account, project, or subscription is billable.

Docs-checkedlanding-zonegovernanceorganizationsguardrailsmulti-account

Quick reference — reach for these first

Org hierarchyaws organizations list-rootsAccount/project/subscription tree: root to OUs/folders/mgmt-groups to accounts
Identityaws sso-admin list-instancesOne central workforce identity source feeding every account
Guardrailsaws organizations list-policies --filter SERVICE_CONTROL_POLICYPreventive policy that denies disallowed actions org-wide
Shared networkingaws ec2 describe-transit-gatewaysHub-and-spoke connectivity shared from a platform account
Central loggingaws cloudtrail describe-trailsImmutable audit/log archive aggregated in one account

Reference landing-zone structure: org root to platform and workload environments

Cloud landing-zone reference structureOrganization root branches into Platform and Workloads parents (OUs / folders / management groups); Platform holds Log Archive, Network Hub and Security accounts; Workloads holds Sandbox, Dev and Prod environments; guardrails, logging and budgets inherit top-down.Organization RootOrgs / GCP Org / Tenant Root MGPlatformOU / Folder / Mgmt GroupWorkloadsOU / Folder / Mgmt GroupLog Archive acctNetwork Hub acctSecurity Tooling acctSandboxDevProd (production)Guardrails, central logging and budgets inherit top-down into every leaf

Text equivalent: A tree. At the top is Organization Root (AWS Organizations / GCP Organization / Azure Tenant Root). It branches into two parent nodes labeled OU / Folder / Management Group: a Platform branch and a Workloads branch. The Platform branch contains three accounts: Log Archive, Network Hub, and Security Tooling. The Workloads branch contains three environment accounts/projects/subscriptions: Sandbox, Dev, and Prod. Prod is highlighted as production. An accent note indicates guardrails, logging, and budgets are inherited top-down from the root through the parents into each leaf.

Common tasks

Capability · AWS / GCP / Azure mapping · How to verify

CapabilityAWS / GCP / Azure mappingHow to verify
Org hierarchyAWS Organizations + OUs | GCP Organization + Folders + Projects | Azure Management Groups + Subscriptionsaws organizations list-organizational-units-for-parent --parent-id ROOT_ID ; gcloud resource-manager folders list --organization ORG_ID ; az account management-group list -o table
Identity (central SSO)IAM Identity Center | Cloud Identity + IAM | Microsoft Entra IDaws sso-admin list-instances ; gcloud organizations get-iam-policy ORG_ID ; az ad signed-in-user show
Policy guardrailsService Control Policies (SCP) | Organization Policies | Azure Policyaws organizations list-policies --filter SERVICE_CONTROL_POLICY ; gcloud org-policies list --organization ORG_ID ; az policy assignment list --scope /providers/Microsoft.Management/managementGroups/MG_ID
Shared networkingTransit Gateway + RAM share | Shared VPC (host/service projects) | Virtual WAN + hub VNet peeringaws ec2 describe-transit-gateway-attachments ; gcloud compute shared-vpc get-host-project SERVICE_PROJECT ; az network vhub list -o table
Centralized loggingOrg CloudTrail to S3 log-archive acct | Aggregated log sinks to logging project | Diagnostic settings to central Log Analyticsaws cloudtrail get-trail-status --name ORG_TRAIL ; gcloud logging sinks list --folder FOLDER_ID ; az monitor diagnostic-settings list --resource RESOURCE_ID
Security baselineSecurity Hub + GuardDuty (delegated admin) | Security Command Center | Microsoft Defender for Cloudaws securityhub get-administrator-account ; gcloud scc settings services describe --organization ORG_ID ; az security auto-provisioning-setting list
Config/compliance baselineAWS Config org rules | Org Policy + SCC posture | Azure Policy complianceaws configservice describe-configuration-recorder-status ; gcloud scc findings list ORG_ID --filter="state=ACTIVE" ; az policy state summarize --management-group MG_ID
Tagging / labelsTag Policies (Organizations) | Labels + org policy constraint | Azure tags + Policy require-tagaws organizations list-policies --filter TAG_POLICY ; gcloud resource-manager tags keys list --parent organizations/ORG_ID ; az policy assignment list --query "[?contains(displayName,'tag')]"
Encryption / keysAWS KMS (per-account CMK) | Cloud KMS | Azure Key Vaultaws kms list-keys ; gcloud kms keyrings list --location LOCATION ; az keyvault list -o table
Budgets / cost controlAWS Budgets + Cost Categories | Billing budgets (Pub/Sub alerts) | Cost Management budgetsaws budgets describe-budgets --account-id ACCOUNT_ID ; gcloud billing budgets list --billing-account BILLING_ID ; az consumption budget list
Workload onboardingControl Tower Account Factory | Project factory (Terraform) | Subscription vending / landing-zone moduleaws controltower list-enabled-controls --target-identifier OU_ARN ; gcloud projects describe NEW_PROJECT ; az account subscription show --id NEW_SUB_ID

Onboard a new Dev workload account and verify it inherited guardrails, logging, and budget

onboarding

1
CONFIRM you are operating against the intended management/org account before anything
aws organizations describe-organization --query 'Organization.MasterAccountId' --output text
# 111122223333  (verify this is the management account, not a workload)
2
Vend the account via Account Factory / landing-zone module into the Workloads > Dev OU (LABEL: creates a new billable account)
terraform apply -target=module.account_factory.dev_workload
# account 444455556666 created under ou-dev-xxxx
3
Verify the SCP guardrails are inherited on the new account's OU target
aws organizations list-policies-for-target --target-id 444455556666 --filter SERVICE_CONTROL_POLICY --query 'Policies[].Name'
# [ "Deny-Leave-Org", "Guardrails-Dev" ]
4
Verify central audit logging covers the new account (org trail still logging)
aws cloudtrail get-trail-status --name org-trail --query 'IsLogging'
# true
5
Verify a budget with alert subscribers exists for the account
aws budgets describe-budgets --account-id 444455556666 --query 'Budgets[].BudgetName'
# [ "Dev-Monthly-500" ]  (80% + 100% alerts to platform-alerts@EXAMPLE)
6
Confirm the config/compliance baseline is recording in the new account
aws configservice describe-configuration-recorder-status --query 'ConfigurationRecordersStatus[0].recording'
# true

Troubleshooting — symptom → first check → next check

SymptomFirst checkEstablishesNext check
New account/project/subscription ignores a guardrail that peers enforceList the policies actually attached to its OU/folder/mgmt-group, not just the org rootWhether the resource lives in the OU the guardrail targets and inherits it, vs. sitting in an unmanaged parentMove it under the correct OU/folder/mgmt-group (AWS organizations move-account; gcloud projects move; az account management-group subscription add) and re-run the inherited-policy check
Resources have drifted from the security baselineQuery the compliance engine for non-compliant findings scoped to that accountWhether drift is config-level (recorder off, rule failing) or a manual change outside IaCRemediate via the managed control or re-apply the Terraform/landing-zone module; enable auto-remediation where supported
Cross-account/project access unexpectedly allowed or deniedSimulate the principal's effective permissions against the target before changing any grantWhether an SCP/org-policy boundary, an IAM grant, or a resource policy is the deciding layerFix at the narrowest correct layer; never widen an org-level SCP to solve a single-account need
Orphaned or untagged resources accumulatingRun a tag/label compliance query and list resources missing required keysWhether the tag policy is enforced (deny) or advisory, and which owner/cost-center is unknownEnforce the require-tag policy in deny mode on new resources and sweep existing ones into an owner before cleanup
Budget exists but no alert ever firedInspect the budget's threshold rules and notification subscribers/channelWhether the budget has notifications wired (SNS/Pub-Sub/action group) vs. a display-only budgetAttach notification subscribers and test the channel; confirm the budget scope matches the account/project
Workload onboarded but logging/monitoring is silentVerify the account/project/subscription is enrolled in the org trail / aggregated sink / diagnostic settingWhether the vending process attached the central logging config or skipped the new targetRe-run the landing-zone enrollment/baseline step and confirm events land in the log-archive account

References

aws-cli v2, gcloud 480+, az CLI 2.60+ on macOS/Linux; a managed landing zone (Control Tower / GCP landing-zone blueprint / Azure CAF) is assumed in place.