Why state is essential in Terraform - Visual Breakdown

Process Flow - Why state is essential

Write Terraform Code

↓

Run terraform apply

↓

Terraform creates resources

↓

Terraform saves state file

↓

Next run reads state file

↓

Terraform compares desired vs actual

↓

Apply only needed changes

↓

End

Terraform uses a state file to remember what resources it created. This helps it know what to change next time.

Execution Sample

Terraform

terraform apply
# creates resources and saves state
terraform apply
# reads state and updates only changes

Shows how Terraform uses the state file to track resources between runs.

Process Table

Step	Action	State File Content	Terraform Behavior
1	Run terraform apply first time	Empty or no state file	Creates all resources as per config, saves state file with resource info
2	Run terraform apply second time	State file with resource info	Reads state, compares with config, no changes if config unchanged
3	Change config (e.g., add resource)	State file with old resources	Reads state, detects new resource, creates only new resource, updates state
4	Delete resource from config	State file with old resources	Reads state, detects missing resource in config, destroys resource, updates state

💡 Terraform stops after syncing real resources with config using state file to track changes.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
state file	empty	contains all created resources	unchanged (if no config change)	updated with new resource	updated after resource deletion

Key Moments - 3 Insights

Why does Terraform need a state file?

Terraform uses the state file to remember what resources it created so it can know what to add, change, or remove next time (see execution_table steps 1 and 2).

What happens if the state file is lost?

Terraform will think no resources exist and try to create everything again, causing duplicates or errors (related to execution_table step 1).

How does Terraform know what changed in the infrastructure?

It compares the current state file with the desired config to find differences and apply only needed changes (see execution_table steps 3 and 4).

Visual Quiz - 3 Questions

Look at the execution_table, what does the state file contain after the first terraform apply?

A It is empty

B It contains all created resources

C It contains only deleted resources

D It contains only planned changes

💡 Hint

Check execution_table row 1 under 'State File Content'

At which step does Terraform detect a new resource to create?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at execution_table row 3 under 'Terraform Behavior'

If the state file is lost, what will Terraform do on next apply?

A Update only changed resources

B Destroy all resources

C Create all resources again

D Do nothing

💡 Hint

Refer to key_moments about losing the state file

Concept Snapshot

Terraform state file stores info about created resources.
It helps Terraform know what exists and what to change.
Without state, Terraform can't track resources properly.
State is updated after each apply.
Always keep state safe and shared for teams.

Full Transcript

Terraform uses a state file to keep track of the resources it creates. When you run terraform apply the first time, it creates all resources and saves their info in the state file. On the next runs, Terraform reads this state file to know what resources already exist. It compares the current state with your configuration to decide what to add, change, or remove. This way, Terraform only makes necessary changes, avoiding duplicates or errors. Losing the state file causes Terraform to lose track of resources, which can lead to recreating everything. Therefore, the state file is essential for Terraform to manage infrastructure safely and efficiently.