Prompt
AWS CloudFormation alternatives for multi-cloud infrastructure
Latest observation
Oct 25, 2026
OpenAI APIWeb search: off
If you want CloudFormation-like infrastructure as code but need multi-cloud support, the main alternatives are:
1. Terraform
- Best overall choice for multi-cloud IaC.
- Supports AWS, Azure, GCP, Kubernetes, and many SaaS providers.
- Uses HCL language, strong module ecosystem, and mature state management.
- Good for provisioning infrastructure consistently across clouds.
2. Pulumi
- Uses general-purpose languages like TypeScript, Python, Go, C#.
- Strong for teams that prefer real programming over declarative DSLs.
- Multi-cloud support across AWS, Azure, GCP, Kubernetes, etc.
- Good for complex logic, abstractions, and software-engineering-style workflows.
3. Crossplane
- Kubernetes-native IaC/control plane.
- Lets you manage cloud resources through Kubernetes CRDs.
- Good if your platform is already built around Kubernetes and GitOps.
- Multi-cloud support via providers.
4. Ansible
- More configuration management / orchestration than pure IaC.
- Can provision across multiple clouds, but it’s usually less ideal than Terraform/Pulumi for long-lived infra state.
- Useful when you also need post-provision configuration.
5. Chef / Puppet
- Older configuration-management tools.
- Can be used in multi-cloud environments, but generally not the first choice for new infrastructure provisioning.
6. OpenTofu
- Community-driven fork of Terraform.
- Multi-cloud support similar to Terraform.
- Good option if you want an open-source alternative with Terraform compatibility.
Quick recommendation
- Most common choice: Terraform or OpenTofu
- Best for code-heavy teams: Pulumi
- Best for Kubernetes-centric platforms: Crossplane
If you want, I can also provide a feature-by-feature comparison table of CloudFormation vs Terraform vs Pulumi vs Crossplane.