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.

Practice

1. What is the main role of a resource in Terraform?

easy

A. It defines what cloud or system object Terraform will create or manage.

B. It stores variables for Terraform configurations.

C. It runs scripts during deployment.

D. It controls user access permissions.

Solution

1. Step 1: Understand Terraform's purpose

   Terraform manages infrastructure by creating or updating real-world objects like servers or databases.

2. Step 2: Identify the role of resources

   Resources tell Terraform exactly which objects to create or manage in the cloud or system.

3. Final Answer:

   It defines what cloud or system object Terraform will create or manage. -> Option A

4. Quick Check:

   Resources = Define infrastructure objects [OK]

Hint: Resources = real cloud objects Terraform manages [OK]

Common Mistakes:

• Confusing resources with variables
• Thinking resources run scripts
• Assuming resources control permissions

2. Which of the following is the correct syntax to declare an AWS EC2 instance resource in Terraform?

easy

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

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

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

D. resource "aws_instance" "example" ( ami = "ami-123456", instance_type = "t2.micro" )

Solution

1. Step 1: Recall Terraform resource syntax

   Terraform resource blocks require the keyword resource, followed by the resource type and name in quotes, then a block with settings.

2. Step 2: Check each option

   resource "aws_instance" "example" { ami = "ami-123456" instance_type = "t2.micro" } correctly uses quotes around type and name, and curly braces for settings. Others miss quotes or use wrong brackets.

3. Final Answer:

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

4. Quick Check:

   Correct resource syntax uses quotes and braces [OK]

Hint: Resource type and name must be in quotes with braces [OK]

Common Mistakes:

• Omitting quotes around resource type or name
• Using parentheses instead of braces
• Missing commas or wrong separators

3. Given this Terraform resource snippet:

resource "aws_s3_bucket" "mybucket" {
  bucket = "my-unique-bucket-123"
  acl    = "private"
}

What will Terraform do when applying this configuration?

medium

A. Create a new S3 bucket named 'mybucket' with public access.

B. Delete any existing S3 bucket named 'mybucket'.

C. Update the ACL of all S3 buckets to 'private'.

D. Create a new S3 bucket named 'my-unique-bucket-123' with private access.

Solution

1. Step 1: Read the resource block details

   The resource is an AWS S3 bucket named 'mybucket' in Terraform, with bucket name 'my-unique-bucket-123' and ACL set to 'private'.

2. Step 2: Understand Terraform behavior

   Terraform will create or manage the bucket named 'my-unique-bucket-123' with the specified ACL. It does not delete unrelated buckets or change all buckets.

3. Final Answer:

   Create a new S3 bucket named 'my-unique-bucket-123' with private access. -> Option D

4. Quick Check:

   Resource defines exact object and settings [OK]

Hint: Resource name is internal; bucket attribute is actual bucket name [OK]

Common Mistakes:

• Confusing resource name with actual bucket name
• Thinking it deletes buckets
• Assuming ACL is public by default

4. You wrote this Terraform resource:

resource "aws_instance" "web" {
  ami = "ami-abc123"
  instance_type = t2.micro
}

What is the error in this configuration?

medium

A. The AMI ID is missing.

B. The instance_type value should be in quotes.

C. The resource name "web" should not be in quotes.

D. The resource type aws_instance is invalid.

Solution

1. Step 1: Check the instance_type attribute

   The value t2.micro is a string and must be enclosed in quotes in Terraform.

2. Step 2: Verify other parts

   The resource type and name are correctly quoted. The AMI ID is present as "ami-abc123".

3. Final Answer:

   The instance_type value should be in quotes. -> Option B

4. Quick Check:

   String values need quotes in Terraform [OK]

Hint: String values always need quotes in resource blocks [OK]

Common Mistakes:

• Forgetting quotes around string values
• Misquoting resource names or types
• Assuming AMI ID is optional

5. You want to create two AWS EC2 instances with different names but the same AMI and instance type using Terraform resources. Which approach correctly uses resources to achieve this?

hard

A. Use a variable to store the AMI and instance_type, but only one resource block with one name.

B. Define one resource block and try to assign two names separated by a comma.

C. Define two separate resource blocks with different names but same AMI and instance_type values.

D. Create one resource block and duplicate it manually in the same file with the same name.

Solution

1. Step 1: Understand resource uniqueness

   Each resource block must have a unique name to represent a distinct object Terraform manages.

2. Step 2: Check options for creating multiple instances

   Define two separate resource blocks with different names but same AMI and instance_type values correctly defines two resource blocks with different names but same settings. Others either reuse names or misuse syntax.

3. Final Answer:

   Define two separate resource blocks with different names but same AMI and instance_type values. -> Option C

4. Quick Check:

   Unique resource names needed for multiple objects [OK]

Hint: Use unique resource names for each object [OK]

Common Mistakes:

• Trying to assign multiple names in one resource
• Duplicating resource blocks with same name
• Using variables but only one resource block