Prompt
I’m building an enterprise cloud landing zone and need IaC tools with governance controls
Latest observation
Oct 25, 2026
OpenAI APIWeb search: off
For an enterprise cloud landing zone with governance controls, you’ll usually want a stack that covers:
- Infrastructure provisioning
- Policy enforcement
- Identity and access control
- Guardrails/compliance
- Auditing and drift detection
- Multi-account / multi-subscription management
Strong IaC + governance options
1) Terraform / OpenTofu
Best for: multi-cloud and mature module ecosystem
Governance controls:
- Policy as code via Sentinel (Terraform Enterprise) or OPA/Conftest
- Remote state, RBAC, approvals in Terraform Cloud/Enterprise
- Module version pinning and private registries
- Drift detection and workspace controls
Good fit if:
- You need a cloud-agnostic landing zone
- You want reusable modules across teams
- You’re okay adding separate governance tooling
2) AWS CloudFormation + AWS Control Tower
Best for: AWS-first landing zones
Governance controls:
- AWS Control Tower sets up guardrails and multi-account governance
- Service Control Policies (SCPs) via AWS Organizations
- CloudFormation StackSets for org-wide deployment
- AWS Config, Security Hub, IAM Access Analyzer
Good fit if:
- Your landing zone is primarily on AWS
- You want built-in governance and account vending
- You want strong native compliance controls
3) Azure Bicep + Azure Landing Zones
Best for: Azure-first enterprises
Governance controls:
- Azure Policy for guardrails
- Management groups for hierarchy
- RBAC and PIM
- Blueprint-like landing zone patterns, policy assignments, deny effects
Good fit if:
- You’re standardizing on Azure
- You want native integration with Microsoft governance services
4) Pulumi
Best for: teams wanting general-purpose programming languages
Governance controls:
- Policy as code with Pulumi CrossGuard
- Stack protections, RBAC, secrets management
- Strong CI/CD integration
Good fit if:
- You want IaC in TypeScript, Python, Go, or C#
- You prefer software engineering workflows over declarative syntax
5) Crossplane
Best for: platform engineering / Kubernetes-centric environments
Governance controls:
- Kubernetes-native policy and admission controls
- Compositions for standardized platform abstractions
- Works well with GitOps and cluster policy engines
Good fit if:
- You want cloud resources managed from Kubernetes
- You’re building an internal platform layer
Governance controls you should require
For an enterprise landing zone, look for tools and patterns that support:
- Policy as code: deny unsafe configs before deployment
- RBAC / least privilege
- Separation of duties: platform team vs app teams
- Approved modules/templates only
- Centralized logging and audit trails
- Tagging/label enforcement
- Network guardrails: no public IPs, restricted peering, approved egress
- Encryption enforcement: at rest and in transit
- Cost controls: budgets, quotas, environment-specific limits
- Drift detection and remediation
- Multi-account / environment isolation
- Secret scanning and state protection
Practical recommendations by cloud
- AWS: Terraform/OpenTofu + AWS Control Tower + SCPs + AWS Config
- Azure: Bicep + Azure Policy + Management Groups + Terraform for reusable modules if needed
- GCP: Terraform/OpenTofu + Org Policy + Hierarchy + Config Controller/Policy Controller
- Multi-cloud: Terraform/OpenTofu + OPA/Conftest + CI/CD gates + centralized policy engine
If you want the shortest answer
For most enterprise landing zones:
- Terraform/OpenTofu for provisioning
- Native cloud governance for controls
- OPA/Sentinel/Azure Policy/SCPs for enforcement
- GitOps + CI/CD approvals for change management
If you want, I can give you:
- a reference architecture for an enterprise landing zone,
- a tool comparison table, or
- a recommended stack for AWS/Azure/GCP.