Why IaC over manual provisioning in Terraform - Visual Breakdown

Process Flow - Why IaC over manual provisioning

Start: Need Infrastructure

↓

Choose Provisioning Method

↓

Manual

↓

Manual Steps

↓

Click/Config

↓

Possible Errors

↓

Slow & Risky

↓

Infrastructure Ready

Shows the choice between manual setup and Infrastructure as Code (IaC), highlighting IaC's repeatability and safety.

Execution Sample

Terraform

# Manual: Click console to create VM
# IaC: terraform apply to create VM
resource "aws_instance" "example" {
  ami           = "ami-123456"
  instance_type = "t2.micro"
}

Compares manual VM creation steps with Terraform code that automates VM creation.

Process Table

Step	Method	Action	Result	Notes
1	Manual	Open cloud console	Console ready	Manual starts with UI
2	Manual	Fill VM details	VM config set	Manual prone to typos
3	Manual	Click create	VM created manually	No repeatability guarantee
4	Manual	Repeat for changes	Manual updates	Risk of drift and errors
5	IaC	Write Terraform code	Code defines VM	Code is version controlled
6	IaC	Run terraform apply	VM created	Repeatable and consistent
7	IaC	Change code and apply	VM updated	Safe updates with plan
8	IaC	Destroy with code	VM removed	Clean teardown possible
9	Exit	Manual errors risk high, IaC repeatable and safe	IaC preferred	Manual is slow and error-prone

💡 Manual provisioning is slow and error-prone; IaC is repeatable, safe, and faster.

Status Tracker

Variable	Start	After Step 3	After Step 6	After Step 7	Final
Infrastructure State	None	VM created manually	VM created by IaC	VM updated by IaC	VM updated and managed by IaC

Key Moments - 3 Insights

Why is manual provisioning considered risky?

Manual steps can have typos or missed configurations, leading to errors as shown in execution_table rows 2 and 4.

How does IaC ensure repeatability?

IaC uses code to define infrastructure, so running the same code always produces the same result, as seen in rows 5-7.

What happens if you want to update infrastructure with IaC?

You change the code and run apply again; Terraform plans changes safely before applying, shown in row 7.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after step 3 in manual provisioning?

A VM updated by IaC

B Code defines VM

C VM created manually

D Console ready

💡 Hint

Check the 'Result' column for step 3 in the manual method.

At which step does IaC first create the VM?

A Step 6

B Step 2

C Step 4

D Step 7

💡 Hint

Look for 'Run terraform apply' action in the IaC method.

If manual provisioning had no errors, how would the exit note change?

A It would say manual is faster

B It would still prefer IaC for repeatability

C It would say IaC is risky

D It would say manual is safer

💡 Hint

Consider the benefits of repeatability and safety shown in variable_tracker.

Concept Snapshot

IaC means writing code to create and manage infrastructure.
Manual provisioning uses clicks and forms.
IaC is repeatable, safe, and fast.
Manual is slow and error-prone.
Use IaC to automate cloud resources reliably.

Full Transcript

This visual execution compares manual provisioning with Infrastructure as Code (IaC). Manual provisioning involves opening the cloud console, filling details, and clicking to create resources. This process is slow and prone to errors. IaC uses code, like Terraform, to define infrastructure. Running the code creates or updates resources consistently. The execution table shows manual steps versus IaC steps, highlighting IaC's repeatability and safety. Variable tracking shows infrastructure state changes from none to managed by IaC. Key moments clarify why manual is risky and IaC is preferred. The quiz tests understanding of these steps and benefits. Overall, IaC automates cloud setup, making it faster and less error-prone than manual methods.