What is Terraform, and how does it differ from other infrastructure-as-code tools like AWS CloudFormation and Azure Resource Manager?

Question

Accepted Answer

Terraform is an open-source infrastructure-as-code tool created by HashiCorp that allows engineers to define, provision, and manage cloud infrastructure using a declarative configuration language called HCL, or HashiCorp Configuration Language. It has become one of the most widely adopted IaC tools in the industry.

The fundamental concept behind Terraform is that you describe the desired state of your infrastructure in configuration files, and Terraform determines the steps needed to reach that state. When you run terraform apply, it compares the desired state in your configuration with the current state of your infrastructure and creates, modifies, or destroys resources as needed to reconcile the difference.

Terraform differs from provider-specific tools like AWS CloudFormation and Azure Resource Manager in several important ways. The most significant difference is that Terraform is cloud-agnostic. While CloudFormation only works with AWS resources and ARM templates only work with Azure resources, Terraform supports hundreds of providers including AWS, Azure, GCP, Kubernetes, GitHub, Datadog, and many others. This means a single tool and workflow can manage infrastructure across multiple platforms.

Terraform uses a provider plugin architecture. Each cloud provider is supported through a provider plugin that translates HCL configurations into API calls specific to that provider. The AWS provider, for example, knows how to create EC2 instances, S3 buckets, and VPCs by calling the appropriate AWS APIs. This modular approach allows the community to create and maintain providers for virtually any service with an API.

Another key difference is state management. Terraform maintains a state file that records the current state of all managed resources, including resource IDs, attributes, and metadata. This state file serves as the source of truth for what Terraform manages. CloudFormation also tracks state, but it does so within the AWS service itself rather than in an external file, which simplifies some operations but limits flexibility.

HCL is designed to be human-readable and writable, offering a balance between the verbosity of JSON-based templates used by CloudFormation and the complexity of full programming languages. It supports variables, outputs, locals, data sources, and built-in functions that make configurations expressive without requiring general-purpose programming knowledge.

Terraform also introduces the concept of a plan phase. Running terraform plan shows exactly what changes will be made before any infrastructure is modified, providing a safety net that helps prevent unintended changes. This plan output can be reviewed by team members and integrated into CI/CD pipelines for approval workflows.

In summary, Terraform's multi-cloud support, provider ecosystem, explicit state management, and plan-and-apply workflow make it the preferred choice for organizations managing infrastructure across multiple platforms or seeking to avoid vendor lock-in in their tooling.