Count for multiple instances in Terraform - Step-by-Step Execution

Process Flow - Count for multiple instances

Define resource with count

↓

Evaluate count value

↓

Create instances 0 to count-1

↓

Assign index to each instance

↓

Deploy all instances

↓

END

Terraform reads the count value, creates that many instances, assigns each an index, and deploys them all.

Execution Sample

Terraform

resource "aws_instance" "example" {
  count = 3
  ami           = "ami-12345678"
  instance_type = "t2.micro"
}

Creates 3 AWS EC2 instances with the specified AMI and instance type.

Process Table

Step	Action	Count Value	Instance Index	Result
1	Read resource block	3	-	Prepare to create 3 instances
2	Evaluate count	3	-	Count is 3, proceed to create 3 instances
3	Create instance	3	0	Instance 0 created
4	Create instance	3	1	Instance 1 created
5	Create instance	3	2	Instance 2 created
6	Deploy instances	3	0-2	All 3 instances deployed
7	End	-	-	No more instances to create

💡 Count reached 3, all instances created and deployed.

Status Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	Final
count	undefined	3	3	3	3
instance_index	undefined	0	1	2	2
instances_created	0	1	2	3	3

Key Moments - 2 Insights

Why does Terraform create instances with indexes 0, 1, and 2 instead of 1, 2, and 3?

Terraform uses zero-based indexing for count, so instances start at index 0. See execution_table rows 3-5 where instance_index goes from 0 to 2.

What happens if count is set to 0?

Terraform creates no instances because count 0 means zero resources. This stops at step 2 in the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the instance_index when the second instance is created?

A 2

B 0

C 1

D 3

💡 Hint

Check execution_table row 4 where instance_index is 1 for the second instance.

At which step does Terraform finish creating all instances?

A Step 6

B Step 5

C Step 4

D Step 7

💡 Hint

Look at execution_table row 5 where the last instance (index 2) is created.

If count was changed to 1, how many instances would be created?

A 1

B 2

C 0

D 3

💡 Hint

Refer to variable_tracker for count value and how it controls instances_created.

Concept Snapshot

Terraform 'count' creates multiple resource instances.
Set count = N to make N copies.
Instances indexed from 0 to N-1.
Each instance can use count.index to get its number.
If count = 0, no instances are created.

Full Transcript

Terraform uses the 'count' argument to create multiple copies of a resource. When you set count to a number, Terraform creates that many instances, starting with index 0. Each instance can access its index using count.index. The process starts by reading the resource block, evaluating the count, then creating each instance one by one until the count is reached. If count is zero, no instances are created. This allows easy scaling of resources without repeating code.

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