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.

Practice

1. Why is Infrastructure as Code (IaC) preferred over manual cloud provisioning?

easy

A. Manual provisioning tracks changes automatically.

B. Manual provisioning is faster for large-scale deployments.

C. IaC requires no knowledge of cloud services.

D. IaC automates setup, saving time and reducing human errors.

Solution

1. Step 1: Understand automation benefits of IaC

   IaC automates cloud setup, which reduces manual work and human mistakes.

2. Step 2: Compare manual provisioning drawbacks

   Manual provisioning is slower and prone to errors, especially at scale.

3. Final Answer:

   IaC automates setup, saving time and reducing human errors. -> Option D

4. Quick Check:

   Automation = IaC advantage [OK]

Hint: IaC automates and reduces errors, unlike manual steps [OK]

Common Mistakes:

• Thinking manual is faster for big setups
• Believing IaC needs no cloud knowledge
• Assuming manual tracks changes automatically

2. Which Terraform command applies your infrastructure code to create resources?

easy

A. terraform apply

B. terraform plan

C. terraform init

D. terraform destroy

Solution

1. Step 1: Identify command to create resources

   terraform apply runs the code and creates or updates infrastructure.

2. Step 2: Differentiate from other commands

   terraform plan shows changes, init sets up, destroy deletes resources.

3. Final Answer:

   terraform apply -> Option A

4. Quick Check:

   Apply = create/update resources [OK]

Hint: Apply means execute changes to infrastructure [OK]

Common Mistakes:

• Confusing plan with apply
• Using init to create resources
• Destroying instead of applying

3. Given this Terraform snippet, what is the main benefit of using it instead of manual setup?

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

medium

A. It automatically tracks and applies changes to the instance.

B. It requires manual steps to launch the instance.

C. It disables version control for infrastructure.

D. It prevents reuse of the configuration.

Solution

1. Step 1: Understand Terraform resource block

   This block defines an AWS instance that Terraform can create and manage automatically.

2. Step 2: Compare with manual setup

   Manual setup requires clicking or scripting outside Terraform, no automatic tracking or updates.

3. Final Answer:

   It automatically tracks and applies changes to the instance. -> Option A

4. Quick Check:

   Automatic tracking = IaC benefit [OK]

Hint: Terraform tracks changes; manual does not [OK]

Common Mistakes:

• Thinking manual steps are needed with Terraform
• Believing Terraform disables version control
• Assuming config cannot be reused

4. You wrote Terraform code but it fails to update your cloud resources. What is a common reason for this?

medium

A. Manual provisioning is required after every change.

B. You forgot to run terraform apply after changes.

C. Terraform does not support updating resources.

D. Terraform automatically updates without commands.

Solution

1. Step 1: Identify Terraform workflow

   After editing code, you must run terraform apply to update resources.

2. Step 2: Eliminate incorrect options

   Terraform supports updates but needs apply; manual provisioning is not needed after changes; updates are not automatic without commands.

3. Final Answer:

   You forgot to run terraform apply after changes. -> Option B

4. Quick Check:

   Apply runs updates [OK]

Hint: Always run terraform apply to update resources [OK]

Common Mistakes:

• Assuming Terraform updates automatically
• Thinking manual steps are needed after code changes
• Believing Terraform cannot update resources

5. How does using Terraform as IaC help teams fix problems faster compared to manual provisioning?

hard

A. Manual provisioning is faster to fix because it uses GUIs.

B. Manual provisioning automatically logs all changes for easy fixes.

C. Terraform code is reusable and tracks changes, making troubleshooting easier.

D. Terraform requires no collaboration, so fewer errors occur.

Solution

1. Step 1: Understand Terraform's tracking and reusability

   Terraform stores infrastructure as code, enabling version control and easy sharing.

2. Step 2: Compare with manual provisioning challenges

   Manual provisioning lacks automatic tracking and is harder to reproduce or fix consistently.

3. Final Answer:

   Terraform code is reusable and tracks changes, making troubleshooting easier. -> Option C

4. Quick Check:

   Tracking + reuse = faster fixes [OK]

Hint: Code tracks changes and is reusable for quick fixes [OK]

Common Mistakes:

• Believing manual provisioning logs changes automatically
• Thinking Terraform needs no teamwork
• Assuming GUIs are always faster to fix problems