Creating your first resource in Terraform - Visual Walkthrough

Process Flow - Creating your first resource

Write resource block

↓

Run terraform init

↓

Run terraform plan

↓

Review plan output

↓

Run terraform apply

↓

Resource created in cloud

↓

Run terraform show or state

↓

Verify resource exists

You write a resource block, initialize Terraform, plan the changes, apply them to create the resource, then verify it exists.

Execution Sample

Terraform

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-unique-bucket-12345"
  acl    = "private"
}

This code creates a private S3 bucket named 'my-unique-bucket-12345' in AWS.

Process Table

Step	Command/Action	Terraform Output/State	Result
1	Write resource block in main.tf	File saved with resource definition	Resource definition ready
2	terraform init	Initializes backend and providers	Terraform ready to run plans
3	terraform plan	Shows plan to create aws_s3_bucket.my_bucket	Plan shows resource will be created
4	terraform apply	Applies plan, creates S3 bucket	S3 bucket created in AWS
5	terraform show	Displays current state with aws_s3_bucket.my_bucket	Confirms resource exists
6	terraform state list	Lists resources in state	aws_s3_bucket.my_bucket listed
7	terraform apply again	No changes detected	No resources changed, idempotent

💡 No changes after first apply, resource exists and Terraform state is up to date

Status Tracker

Variable	Start	After Step 3	After Step 4	Final
aws_s3_bucket.my_bucket	undefined	planned for creation	created with ID	exists in state

Key Moments - 3 Insights

Why does terraform plan show changes before apply?

Because terraform plan compares current state (empty at first) with desired config and shows what will be created, as seen in step 3 of execution_table.

What happens if you run terraform apply again without changes?

Terraform detects no changes needed and does nothing, showing 'No changes detected' as in step 7 of execution_table.

How do you verify the resource was created?

By running terraform show or terraform state list (steps 5 and 6), which confirm the resource exists in the state.

Visual Quiz - 3 Questions

Look at the execution_table, what does terraform plan show at step 3?

A Resource will be destroyed

B No changes needed

C Resource aws_s3_bucket.my_bucket will be created

D Error in configuration

💡 Hint

Check the 'Terraform Output/State' column at step 3 in execution_table

At which step does Terraform actually create the S3 bucket?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look for 'Applies plan, creates S3 bucket' in the 'Command/Action' column

If you change the bucket name in the resource block and run terraform apply again, what will happen?

A Terraform will create a new bucket and delete the old one

B Terraform will ignore the change

C Terraform will update the existing bucket name in place

D Terraform will fail with an error

💡 Hint

Changing bucket name is a resource replacement, so terraform plans to create new and delete old (related to step 3 plan behavior)

Concept Snapshot

Terraform resource creation steps:
1. Write resource block in .tf file
2. Run 'terraform init' to prepare
3. Run 'terraform plan' to see changes
4. Run 'terraform apply' to create resource
5. Verify with 'terraform show' or 'terraform state list'
Terraform is idempotent: repeated apply with no changes does nothing.

Full Transcript

Creating your first resource with Terraform involves writing a resource block in a configuration file, initializing Terraform with 'terraform init', planning the changes with 'terraform plan', applying those changes with 'terraform apply', and verifying the resource exists using 'terraform show' or 'terraform state list'. The plan step shows what Terraform will do before it does it. After applying, Terraform records the resource in its state. Running apply again without changes results in no action, demonstrating idempotency.