Skip to main content
In this lesson we’ll clear up common confusions about Terraform and show how it relates to other infrastructure and configuration tools. Understanding these differences helps you choose the right tool for provisioning, lifecycle management, or in-guest configuration. There are two natural groupings to keep in mind:
  • Tools similar to Terraform (infrastructure-as-code, focused on provisioning).
  • Tools with a different purpose but often complementary to Terraform (configuration management).

​
Infrastructure-as-Code (IaC) — Tools similar to Terraform

These tools are declarative and focused on provisioning infrastructure. Pick one based on whether you want cloud-native integration, multi-cloud portability, or developer-friendly languages. Practical consequence: organizations adopting multiple clouds often prefer a single cross-cloud tool (Terraform or Pulumi) to reduce the learning curve and maintenance overhead of provider-specific IaC. Conversely, CloudFormation or Bicep are excellent if you want deep, platform-native features for a single cloud.

​
Complementary Tools — Configuration Management

Configuration management tools operate inside provisioned machines (in-guest) and excel at installing packages, managing files and services, and configuring applications. These tools are often idempotent and focus on ensuring a desired state of software and configuration inside the OS, whereas Terraform maintains resource state and a dependency graph for lifecycle management.

​
Common Workflows

A typical, effective pipeline blends both types of tools:
  • Use Terraform (or another cloud IaC tool) to provision and manage infrastructure: networks, instances, managed services, load balancers, and DNS entries.
  • Use a configuration management tool (Ansible, Chef, Puppet, etc.) to finalize in-guest setup: install packages, configure services, deploy application code, and run migrations.
  • Some configuration tools (Ansible modules, for example) can provision cloud resources, but their core strength remains configuring running systems and applications.
  • Terraform stores state and plans changes based on a resource graph; treat state as a critical artifact and store it safely (remote/backed storage with locking).
Terraform maintains state and a resource dependency graph. Protect and manage state (use remote state backends and locking) and be careful when importing or modifying resources outside Terraform to avoid drift and state mismatches.

​
Quick Comparison Table

​
When to Choose Which

  • Choose CloudFormation or Bicep when:
    • You are committed to a single cloud and need the deepest, native platform integration.
  • Choose Terraform when:
    • You need consistent tooling across multiple clouds or a broad provider ecosystem.
  • Choose Pulumi when:
    • Your team prefers using general-purpose languages and standard developer tooling for infrastructure code.
  • Choose Ansible/Chef/Puppet/SaltStack when:
    • You need to manage packages, services, files, and application config inside running machines.
Consider team skills, target clouds, and integration needs: use cloud-native IaC for platform depth, Terraform or Pulumi for multi-cloud consistency, and configuration management tools for final in-guest setup and application deployment.

​
Summary

  • CloudFormation and Azure Bicep: cloud-specific declarative IaC for deep platform integration.
  • Pulumi: cloud-agnostic IaC using general-purpose programming languages.
  • Terraform: cloud-agnostic declarative IaC with HCL, a provider model, and strong multi-cloud support.
  • Ansible, Chef, Puppet, SaltStack: configuration management for installing and configuring software on provisioned machines.
Understanding these roles helps you design an effective automation pipeline: use an IaC tool (Terraform, Pulumi, or a cloud-native solution) to create and manage infrastructure, and use configuration management tools to finalize software and runtime configuration inside those resources.

Watch Video