Why IaC over manual provisioning in Terraform - See It in Action

Why IaC over manual provisioning

📖 Scenario: You work as a cloud engineer for a small company. The company wants to set up a simple web server on a cloud provider. They are deciding between creating the server manually through the cloud console or using code to automate the setup.

🎯 Goal: Build a simple Terraform configuration that creates a virtual machine instance. This will show how Infrastructure as Code (IaC) works compared to manual setup.

📋 What You'll Learn

Create a Terraform configuration file named main.tf

Define a resource for a virtual machine instance with specific properties

Add a variable to configure the instance type

Use the variable in the resource configuration

Add an output to show the instance's public IP address

💡 Why This Matters

🌍 Real World

Cloud engineers use Infrastructure as Code to automate and manage cloud resources reliably and quickly.

💼 Career

Knowing IaC tools like Terraform is essential for roles in cloud operations, DevOps, and infrastructure management.

1

Create the initial Terraform resource

Create a Terraform resource named aws_instance called web_server with the following properties: ami = "ami-0c55b159cbfafe1f0" and instance_type = "t2.micro" inside a file named main.tf.

Terraform

# Your code here

Hint

The resource block starts with resource "aws_instance" "web_server" { and ends with }.

2

Add a variable for instance type

Add a Terraform variable named instance_type with a default value of "t2.micro" in the same main.tf file.

Terraform

resource "aws_instance" "web_server" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
}

# Your code here

Hint

Use variable "instance_type" {} block and refer to it as var.instance_type inside the resource.

3

Add an output for the public IP

Add an output named public_ip that shows the public_ip attribute of the aws_instance.web_server resource in main.tf.

Terraform

resource "aws_instance" "web_server" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = var.instance_type
}

variable "instance_type" {
  type    = string
  default = "t2.micro"
}

# Your code here

Hint

Use output "public_ip" { value = aws_instance.web_server.public_ip } to show the IP.

4

Explain why IaC is better than manual provisioning

Add a comment at the top of main.tf explaining in simple words why using Terraform (IaC) is better than creating the server manually.

Terraform

# Your comment here
resource "aws_instance" "web_server" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = var.instance_type
}

variable "instance_type" {
  type    = string
  default = "t2.micro"
}

output "public_ip" {
  value = aws_instance.web_server.public_ip
}

Hint

Write a simple comment starting with # explaining benefits like repeatability, fewer errors, and tracking.

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