Cloud automation is the layer that turns manual operations into code. The right tool depends on the task: configuration management, infrastructure provisioning, orchestration, deployment, or remediation. The choices in 2026 split into four buckets: configuration, provisioning, orchestration, and remediation.
Table of contents
- The four buckets
- The provisioning tools
- The configuration tools
- The orchestration tools
- The remediation tools
- How to choose
- FAQ
The four buckets
The four buckets, with the most common use case for each:
- Provisioning. Creating the infrastructure: the VPC, the cluster, the database, the queue. Terraform, Pulumi, CDK.
- Configuration. Configuring the infrastructure: the OS, the package, the file, the service. Ansible, Chef, Puppet, Salt.
- Orchestration. Coordinating the infrastructure: the deploy, the rollback, the scale-out, the scale-in. Kubernetes, ECS, Nomad.
- Remediation. Fixing the infrastructure when it breaks: the alert, the runbook, the auto-heal. The combination of observability and a workflow tool.
The provisioning tools
The provisioning tools in 2026, ordered by adoption:
- Terraform. The standard. The right answer when the team is comfortable with HCL and the provider ecosystem.
- Pulumi. The runner-up. The right answer when the team wants to write the IaC in a real programming language.
- CDK (Cloud Development Kit). The cloud-vendor-specific equivalent. The right answer when the team is all-in on one cloud and wants the integration with the vendor’s services.
- Crossplane. The Kubernetes-native equivalent. The right answer when the team is running everything on Kubernetes and wants the IaC to be a Kubernetes resource.
The configuration tools
The configuration tools in 2026, ordered by adoption:
- Ansible. The standard. The right answer when the team is comfortable with YAML and the module ecosystem.
- Chef. The enterprise equivalent. The right answer when the team is running a large Ruby shop.
- Puppet. The enterprise equivalent. The right answer when the team is running a large infrastructure and needs the model-driven approach.
- Salt. The middle ground. The right answer when the team wants the speed of Ansible and the model of Puppet.
The orchestration tools
The orchestration tools, for the workloads that need to coordinate multiple services:
- Kubernetes. The standard. The right answer for the team running containers at scale.
- ECS. The AWS managed equivalent. The right answer for the team on AWS that does not want to operate Kubernetes.
- Nomad. The HashiCorp equivalent. The right answer for the team that wants a simpler orchestrator than Kubernetes.
- Docker Swarm. The Docker-native equivalent. The right answer for the small team running a few containers.
The remediation tools
The remediation tools, for the workloads that need to auto-heal:
- Kubernetes liveness probes. The basic. The right answer when the workload is on Kubernetes and a restart is enough.
- AWS Auto Scaling. The AWS equivalent. The right answer when the workload is on AWS and a scale-out is enough.
- PagerDuty + runbook automation. The cross-vendor equivalent. The right answer when the team wants a human in the loop with an auto-remediation script.
- Argo Workflows. The Kubernetes-native equivalent. The right answer when the team wants the remediation to be a Kubernetes resource.
How to choose
The choice rule: pick the tool the team can actually operate. The team that picks the most modern automation tool and cannot operate it is in worse shape than the team that picks a simpler tool and runs it well.
The right starting point for most teams: Terraform (or CDK) for the provisioning, Ansible for the configuration, Kubernetes (or ECS) for the orchestration, and a runbook for the remediation. The team can add Argo, Crossplane, or PagerDuty automation as the workload grows.
FAQ
What is cloud automation?
The layer that turns manual operations into code. The right tool depends on the task: provisioning, configuration, orchestration, or remediation.
What is the difference between Terraform and Ansible?
Terraform is for provisioning - creating the infrastructure. Ansible is for configuration - configuring the infrastructure. The two are complementary; most teams use both.
What is the best cloud automation tool in 2026?
The right answer depends on the team. For provisioning: Terraform (or CDK). For configuration: Ansible. For orchestration: Kubernetes (or ECS). For remediation: a runbook plus an observability tool.
How do I get started with cloud automation?
Start with Terraform (or CDK) for the provisioning, Ansible for the configuration, Kubernetes (or ECS) for the orchestration, and a runbook for the remediation.
If you are sizing an automation project, the RunxBuild hosting calculator is the place to model the line items. The infrastructure, the configuration, the orchestration, the remediation - each one is a separate number, and the team’s mental model for the platform is the sum of those numbers. The RunxBuild dashboard is where the team sees the actual automation in one place.