Terraform vs CloudFormation vs Pulumi - Visual Side-by-Side Comparison

Process Flow - Terraform vs CloudFormation vs Pulumi

Start: Choose IaC Tool

↓

Deploy Infrastructure

↓

Manage State & Updates

↓

Infrastructure Ready

The flow shows choosing between Terraform, CloudFormation, or Pulumi, then deploying and managing infrastructure.

Execution Sample

Terraform

terraform {
  required_providers {
    aws = { source = "hashicorp/aws" version = "~> 4.0" }
  }
}
resource "aws_s3_bucket" "example" {
  bucket = "my-unique-bucket-12345"
}

This Terraform code creates an AWS S3 bucket named 'my-unique-bucket-12345'.

Process Table

Step	Action	Tool Behavior	Result
1	Initialize Terraform	Reads config, downloads AWS provider	Ready to plan
2	terraform plan	Compares desired state with current	Shows bucket to create
3	terraform apply	Creates S3 bucket in AWS	Bucket 'my-unique-bucket-12345' created
4	CloudFormation equivalent	Uses JSON/YAML template	Creates same bucket in AWS
5	Pulumi equivalent	Uses code in Python/JS/etc.	Creates same bucket in AWS
6	Manage updates	Terraform tracks state file	Updates or deletes resources as needed
7	Exit	Infrastructure deployed and managed	Ready for use

💡 Infrastructure is deployed and managed by the chosen tool.

Status Tracker

Variable	Start	After Init	After Plan	After Apply	Final
terraform_state	empty	initialized	planned (bucket to create)	applied (bucket created)	current state with bucket
aws_s3_bucket.example	none	defined in config	planned for creation	created in AWS	exists and ready

Key Moments - 3 Insights

Why does Terraform use a state file while CloudFormation does not?

Terraform keeps a local or remote state file to track resources across clouds, while CloudFormation manages state internally within AWS. See execution_table rows 6 and 4.

Can Pulumi use the same languages as Terraform?

No, Pulumi uses general-purpose languages like Python or JavaScript, while Terraform uses its own HCL language. See concept_flow and execution_table rows 5 and 1.

Why choose CloudFormation over Terraform?

CloudFormation is AWS-native and may have faster support for new AWS features. Terraform supports multiple clouds but may lag. See concept_flow and execution_table rows 4 and 1.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the S3 bucket actually created in AWS?

A Step 3

B Step 4

C Step 2

D Step 6

💡 Hint

Check the 'Result' column for when the bucket is created.

According to variable_tracker, what is the state of 'terraform_state' after 'terraform plan'?

A empty

B initialized

C planned (bucket to create)

D applied (bucket created)

💡 Hint

Look at the 'After Plan' column for 'terraform_state'.

If you want to use Python code to define infrastructure, which tool from concept_flow would you pick?

A CloudFormation

B Pulumi

C Terraform

D None of these

💡 Hint

See the 'Pulumi' box in concept_flow mentioning general languages.

Concept Snapshot

Terraform, CloudFormation, and Pulumi are tools to create cloud infrastructure.
Terraform uses HCL and supports many clouds.
CloudFormation is AWS-only and uses JSON/YAML.
Pulumi uses real programming languages and supports many clouds.
All deploy resources and manage updates differently.

Full Transcript

This visual execution compares Terraform, CloudFormation, and Pulumi. It starts with choosing a tool, then shows Terraform code creating an AWS S3 bucket. The execution table traces initialization, planning, applying, and managing infrastructure. Variable tracking shows how Terraform state and resource definitions change step-by-step. Key moments clarify differences in state management, language use, and cloud support. The quiz tests understanding of when resources are created, state changes, and tool language options. The snapshot summarizes key points for quick recall.