Why resources are Terraform's core - Visual Breakdown

Process Flow - Why resources are Terraform's core

Define Resource Block

↓

Terraform Reads Config

↓

Create/Update Resource

↓

Track Resource State

↓

Manage Infrastructure

↓

Apply Changes or Destroy

Terraform uses resource blocks to know what cloud parts to create or change. It reads these, makes the resources, tracks them, and manages updates.

Execution Sample

Terraform

resource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
}

This code tells Terraform to create a small AWS server using a specific image.

Process Table

Step	Action	Resource State Before	Terraform Operation	Resource State After
1	Read resource block	No aws_instance.example	Parse config	Prepare to create aws_instance.example
2	Plan execution	No aws_instance.example	Compare desired vs current	Plan to create aws_instance.example
3	Apply changes	No aws_instance.example	Send create request to AWS	aws_instance.example created
4	Update state file	aws_instance.example created	Record resource info	State file updated with aws_instance.example
5	Next apply	aws_instance.example exists	Check for changes	No changes, resource unchanged
6	Destroy resource	aws_instance.example exists	Send delete request to AWS	aws_instance.example removed
7	Update state file	aws_instance.example removed	Remove resource from state	State file updated, resource removed

💡 Terraform stops when resource state matches desired config or resource is destroyed.

Status Tracker

Variable	Start	After Step 3	After Step 5	After Step 7
aws_instance.example	undefined	created	unchanged	deleted

Key Moments - 3 Insights

Why does Terraform keep a state file after creating resources?

Terraform uses the state file to remember what it created (see execution_table step 4). This helps it know what exists and what needs updating or deleting later.

What happens if you change the resource config after creation?

Terraform compares the new config with the state (step 5). If different, it plans and applies updates to match the new config.

Why is the resource block important in Terraform?

The resource block tells Terraform exactly what to create or manage (step 1). Without it, Terraform doesn't know what infrastructure to handle.

Visual Quiz - 3 Questions

Look at the execution_table, what is the resource state after step 3?

A Resource is planned to be created

B Resource is created

C Resource is deleted

D Resource state is unknown

💡 Hint

Check the 'Resource State After' column in step 3.

At which step does Terraform update the state file to remove the resource?

A Step 4

B Step 5

C Step 7

D Step 6

💡 Hint

Look for 'State file updated, resource removed' in the 'Resource State After' column.

If you change the instance_type in the resource block, which step will detect this change?

A Step 2 - Plan execution

B Step 3 - Apply changes

C Step 5 - Next apply

D Step 6 - Destroy resource

💡 Hint

Terraform compares desired vs current state during planning (step 2).

Concept Snapshot

Terraform uses resource blocks to define cloud parts.
It reads these blocks, creates or updates resources,
and keeps track in a state file.
This state helps Terraform manage changes safely.
Resources are the core because they represent real infrastructure.

Full Transcript

Terraform's core is the resource block. It tells Terraform what cloud resource to create or manage. When you run Terraform, it reads these blocks, plans what to do by comparing current state and desired state, then applies changes to create or update resources. After creating, Terraform saves resource info in a state file to remember what exists. This helps it manage updates or deletions later. If you change the resource config, Terraform detects differences during planning and applies updates. When you destroy resources, Terraform deletes them and updates the state file. This cycle makes resources the heart of Terraform's infrastructure management.