Why variables make configurations reusable in Terraform - See It in Action

Why variables make configurations reusable

📖 Scenario: You are setting up a cloud server configuration using Terraform. You want to make your setup easy to change for different projects without rewriting the whole code.

🎯 Goal: Build a Terraform configuration that uses variables to make the server setup reusable for different environments.

📋 What You'll Learn

Create a variable for the server name

Create a variable for the server instance type

Use the variables in the resource configuration

Set default values for the variables

💡 Why This Matters

🌍 Real World

Cloud engineers use variables in Terraform to create flexible infrastructure code that works for many projects.

💼 Career

Knowing how to use variables is essential for writing reusable and maintainable infrastructure as code.

1

Create variables for server name and instance type

Create two variables in Terraform: server_name with default value my-server and instance_type with default value t2.micro.

Terraform

# Define variables for server_name and instance_type
# Your code here

Hint

Use variable blocks with default values for both variables.

2

Add a resource using the variables

Add an aws_instance resource named example that uses the variables server_name for tags.Name and instance_type for instance_type.

Terraform

variable "server_name" {
  type    = string
  default = "my-server"
}

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

# Add aws_instance resource using variables
# Your code here

Hint

Use var.instance_type and var.server_name inside the resource block.

3

Add a variable for the AMI ID

Create a variable called ami_id with default value ami-0c55b159cbfafe1f0 and update the aws_instance resource to use var.ami_id for the ami attribute.

Terraform

variable "server_name" {
  type    = string
  default = "my-server"
}

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

# Define ami_id variable and update aws_instance resource
# Your code here

Hint

Define the ami_id variable and replace the hardcoded AMI in the resource with var.ami_id.

4

Add an output for the server ID

Add an output called server_id that outputs the id attribute of the aws_instance.example resource.

Terraform

variable "server_name" {
  type    = string
  default = "my-server"
}

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

variable "ami_id" {
  type    = string
  default = "ami-0c55b159cbfafe1f0"
}

resource "aws_instance" "example" {
  ami           = var.ami_id
  instance_type = var.instance_type

  tags = {
    Name = var.server_name
  }
}

# Add output for server_id
# Your code here

Hint

Use an output block with the value set to aws_instance.example.id.

Practice

1. Why do variables make Terraform configurations reusable?

easy

A. Because they allow changing values without modifying the main code

B. Because they automatically create resources

C. Because they prevent any errors in the code

D. Because they remove the need for providers

Solution

1. Step 1: Understand the role of variables

   Variables hold values that can be changed without editing the main configuration code.

2. Step 2: Recognize how this affects reusability

   Changing variable values lets you reuse the same code for different setups or environments easily.

3. Final Answer:

   Because they allow changing values without modifying the main code -> Option A

4. Quick Check:

   Variables = flexible values [OK]

Hint: Variables let you change inputs, not code [OK]

Common Mistakes:

• Thinking variables create resources automatically
• Believing variables fix all code errors
• Assuming variables replace providers

2. Which of the following is the correct way to declare a variable in Terraform?

easy

A. var region = "us-west-1"

B. variable "region" { default = "us-west-1" }

C. set variable region = "us-west-1"

D. define region: "us-west-1"

Solution

1. Step 1: Recall Terraform variable syntax

   Terraform variables are declared using the keyword 'variable' followed by the name in quotes and a block with settings.

2. Step 2: Match the syntax to options

   variable "region" { default = "us-west-1" } matches the correct syntax: variable "region" { default = "us-west-1" }.

3. Final Answer:

   variable "region" { default = "us-west-1" } -> Option B

4. Quick Check:

   Correct variable syntax = variable "region" { default = "us-west-1" } [OK]

Hint: Look for 'variable' keyword and braces {} [OK]

Common Mistakes:

• Using 'var' keyword incorrectly
• Missing braces {} around variable block
• Using assignment syntax from other languages

3. Given this Terraform snippet:

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

What will be the instance type if no variable value is provided?

medium

A. t2.micro

B. ami-123456

C. var.instance_type

D. No instance type will be set

Solution

1. Step 1: Identify the default variable value

   The variable "instance_type" has a default value set to "t2.micro".

2. Step 2: Understand variable usage in resource

   The resource uses var.instance_type, so if no override is given, it uses the default "t2.micro".

3. Final Answer:

   t2.micro -> Option A

4. Quick Check:

   Default variable value used = t2.micro [OK]

Hint: Default value applies if no override given [OK]

Common Mistakes:

• Confusing AMI ID with instance type
• Thinking var.instance_type is a string literal
• Assuming no value means no instance type

4. You wrote this variable declaration:

variable "env" = "production"

Why does Terraform give an error?

medium

A. Because default values must be numbers

B. Because variable names cannot be "env"

C. Because variable declarations need a block, not an assignment

D. Because variables cannot have default values

Solution

1. Step 1: Check variable declaration syntax

   Terraform variables must be declared using a block: variable "name" { ... } not with '=' assignment.

2. Step 2: Identify the error cause

   Using '=' directly after variable name causes syntax error.

3. Final Answer:

   Because variable declarations need a block, not an assignment -> Option C

4. Quick Check:

   Variable declaration requires block syntax [OK]

Hint: Use braces {} for variables, not '=' [OK]

Common Mistakes:

• Using '=' instead of block for variables
• Thinking variable names are restricted
• Believing default values must be numeric

5. You want to reuse a Terraform module for multiple environments (dev, test, prod) with different instance sizes. How do variables help achieve this?

hard

A. By writing separate code for each environment without variables

B. By using variables only for provider configuration

C. By hardcoding instance sizes inside the module

D. By defining a variable for instance size and passing different values per environment

Solution

1. Step 1: Understand module reuse with variables

   Variables let you set inputs like instance size dynamically when calling the module.

2. Step 2: Apply different values per environment

   Passing different values for the instance size variable lets the same module create resources tailored to each environment.

3. Final Answer:

   By defining a variable for instance size and passing different values per environment -> Option D

4. Quick Check:

   Variables enable flexible module inputs [OK]

Hint: Use variables to customize modules per environment [OK]

Common Mistakes:

• Duplicating code instead of using variables
• Hardcoding values inside modules
• Limiting variables to provider settings only