Count for multiple instances in Terraform - Mini Project: Build & Apply

Count for multiple instances

📖 Scenario: You are setting up a simple cloud infrastructure using Terraform. You want to create multiple identical virtual machines (instances) to handle web traffic.

🎯 Goal: Build a Terraform configuration that creates exactly three virtual machine instances using the count meta-argument.

📋 What You'll Learn

Create a resource block for an AWS EC2 instance named aws_instance.web.

Use the count meta-argument to create exactly 3 instances.

Set the ami attribute to "ami-0c55b159cbfafe1f0".

Set the instance_type attribute to "t2.micro".

💡 Why This Matters

🌍 Real World

Creating multiple virtual machines is common when you want to scale your application to handle more users.

💼 Career

Cloud engineers often use Terraform's count feature to efficiently manage multiple resources without repeating code.

1

DATA SETUP: Define the AWS provider

Write a provider block for AWS with the region set to "us-east-1".

Terraform

# Your code here

Hint

The provider block tells Terraform which cloud provider to use and where.

2

CONFIGURATION: Add the count variable

Create a variable called instance_count with a default value of 3.

Terraform

provider "aws" {
  region = "us-east-1"
}

# Your code here

Hint

Variables help you change values easily without editing resource blocks.

3

CORE LOGIC: Create multiple instances using count

Create a resource block named aws_instance.web that uses count = var.instance_count. Set ami to "ami-0c55b159cbfafe1f0" and instance_type to "t2.micro".

Terraform

provider "aws" {
  region = "us-east-1"
}

variable "instance_count" {
  default = 3
}

# Your code here

Hint

The count argument creates multiple copies of the resource.

4

COMPLETION: Add tags to instances

Add a tags block inside the aws_instance.web resource with Name = "WebServer-${count.index + 1}".

Terraform

provider "aws" {
  region = "us-east-1"
}

variable "instance_count" {
  default = 3
}

resource "aws_instance" "web" {
  count         = var.instance_count
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"

  # Your code here
}

Hint

Tags help identify your instances in the cloud console.

Practice

1. What does the count argument do in a Terraform resource block?

easy

A. It deletes resources after creation.

B. It creates multiple copies of the resource based on the count value.

C. It renames the resource dynamically.

D. It pauses resource creation until manually resumed.

Solution

1. Step 1: Understand the purpose of count

   The count argument tells Terraform how many copies of a resource to create.

2. Step 2: Recognize the effect of count value

   If count is set to 3, Terraform creates 3 identical resources.

3. Final Answer:

   It creates multiple copies of the resource based on the count value. -> Option B

4. Quick Check:

   count creates copies = A [OK]

Hint: Count controls how many resource copies are made [OK]

Common Mistakes:

• Thinking count deletes resources
• Assuming count renames resources
• Believing count pauses creation

2. Which of the following is the correct syntax to create 4 instances of an AWS EC2 resource using count?

easy

A. resource "aws_instance" "example" { count = 4 }

B. resource "aws_instance" "example" { count = "four" }

C. resource "aws_instance" "example" { count = true }

D. resource "aws_instance" "example" { count = 1..4 }

Solution

1. Step 1: Check the count value type

   The count argument must be a number, not a string or boolean.

2. Step 2: Validate syntax correctness

   resource "aws_instance" "example" { count = 4 } uses count = 4, which is a valid number and correct syntax.

3. Final Answer:

   resource "aws_instance" "example" { count = 4 } -> Option A

4. Quick Check:

   count = number syntax = D [OK]

Hint: Count must be a number, not string or boolean [OK]

Common Mistakes:

• Using string instead of number for count
• Using boolean true/false for count
• Trying to use a range expression directly

3. Given this Terraform snippet:

resource "aws_s3_bucket" "bucket" {
  count = 3
  bucket = "my-bucket-${count.index}"
}

What will be the names of the created buckets?

medium

A. ["my-bucket", "my-bucket", "my-bucket"]

B. ["my-bucket-1", "my-bucket-2", "my-bucket-3"]

C. ["my-bucket-0", "my-bucket-1", "my-bucket-2"]

D. ["my-bucket-3"]

Solution

1. Step 1: Understand count.index usage

   The count.index starts at 0 and increments by 1 for each instance.

2. Step 2: Apply count.index to bucket names

   With count=3, bucket names become "my-bucket-0", "my-bucket-1", and "my-bucket-2".

3. Final Answer:

   ["my-bucket-0", "my-bucket-1", "my-bucket-2"] -> Option C

4. Quick Check:

   count.index starts at 0 = C [OK]

Hint: count.index starts at zero and increments [OK]

Common Mistakes:

• Starting count.index at 1 instead of 0
• Using same name for all instances
• Assuming only one bucket created

4. Identify the error in this Terraform resource block:

resource "aws_security_group" "sg" {
  count = 2
  name = "sg-${count}"
}

medium

A. Name attribute cannot use interpolation.

B. Missing required provider configuration.

C. Count cannot be used with security groups.

D. Using count instead of count.index in the name.

Solution

1. Step 1: Check usage of count in interpolation

   The variable count is not valid inside strings; count.index should be used.

2. Step 2: Confirm correct interpolation

   Replace "sg-${count}" with "sg-${count.index}" to get unique names.

3. Final Answer:

   Using count instead of count.index in the name. -> Option D

4. Quick Check:

   Use count.index for indexes in strings = A [OK]

Hint: Use count.index, not count, inside strings [OK]

Common Mistakes:

• Using count instead of count.index
• Assuming count cannot be used with this resource
• Thinking name interpolation is disallowed

5. You want to create multiple AWS EC2 instances with different instance types using count. Which approach correctly assigns instance types from a list?

hard

A. Use count with var.instance_types[count.index] to assign types.

B. Use count and assign a single instance type to all instances.

C. Use count with a fixed string for instance type.

D. Use count with a random instance type each time.

Solution

1. Step 1: Understand how to assign different values per instance

   Using count.index allows selecting different values from a list for each instance.

2. Step 2: Apply list indexing with count.index

   Accessing var.instance_types[count.index] assigns the correct instance type per resource copy.

3. Final Answer:

   Use count with var.instance_types[count.index] to assign types. -> Option A

4. Quick Check:

   List indexing with count.index assigns unique values = B [OK]

Hint: Index lists with count.index for unique resource values [OK]

Common Mistakes:

• Assigning same instance type to all
• Using fixed string ignoring count.index
• Expecting random assignment without code