What is Infrastructure as Code in Terraform - Visual Explanation

Process Flow - What is Infrastructure as Code

Write code to define infrastructure

↓

Run code with Terraform

↓

Terraform reads code

↓

Terraform creates/updates resources

↓

Infrastructure is ready and managed by code

↓

Change code -> Run Terraform again -> Update infrastructure

Infrastructure as Code means writing code to create and manage cloud resources automatically. Terraform reads this code and makes the real infrastructure match it.

Execution Sample

Terraform

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

This code tells Terraform to create a private S3 bucket named 'my-unique-bucket-123'.

Process Table

Step	Action	Terraform Reads	Result
1	Start Terraform apply	Reads resource block for aws_s3_bucket.my_bucket	Plans to create S3 bucket named 'my-unique-bucket-123'
2	Create resource	Sends request to AWS to create bucket	AWS creates the bucket successfully
3	Verify creation	Checks bucket exists	Bucket is confirmed created
4	Finish	No more changes	Infrastructure matches code

💡 Terraform finishes because infrastructure matches the code definition.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
aws_s3_bucket.my_bucket	undefined	planned	created	verified	ready

Key Moments - 3 Insights

Why do we write code instead of clicking in the cloud console?

Writing code lets us repeat, track, and share infrastructure setup easily. Execution table step 1 shows Terraform reading code to plan creation.

What happens if we change the code after creation?

Terraform compares current infrastructure with code and updates resources accordingly, as shown in the concept flow last step.

Does Terraform create resources immediately when we write code?

No, Terraform only creates resources when we run 'terraform apply', as shown in execution table step 2.

Visual Quiz - 3 Questions

Look at the execution table, what does Terraform do at step 2?

A Verifies the bucket exists

B Reads the code to plan changes

C Sends request to AWS to create the bucket

D Finishes execution

💡 Hint

Check the 'Action' and 'Result' columns in step 2 of the execution table.

According to the variable tracker, what is the state of aws_s3_bucket.my_bucket after step 3?

A undefined

B verified

C planned

D created

💡 Hint

Look at the 'After Step 3' column for aws_s3_bucket.my_bucket in the variable tracker.

If we change the bucket name in the code and run Terraform again, what will happen?

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

B Terraform will ignore the change

C Terraform will update the existing bucket to the new name

D Terraform will crash

💡 Hint

Refer to the concept flow last step about changing code and running Terraform again.

Concept Snapshot

Infrastructure as Code means writing code to define cloud resources.
Terraform reads this code and creates or updates resources automatically.
This makes infrastructure repeatable, trackable, and easy to manage.
Changes in code lead to updates in real infrastructure when Terraform runs.
No manual clicks needed; code is the source of truth.

Full Transcript

Infrastructure as Code is a way to manage cloud resources by writing code instead of clicking in a console. You write code that describes what you want, like creating a storage bucket. Then you run Terraform, which reads your code and makes the cloud match it. Terraform plans what to do, creates or updates resources, and checks they exist. If you change the code later, running Terraform again updates the infrastructure to match. This method helps keep infrastructure consistent, easy to share, and repeatable.