For Each Vs Count

Learning Objectives

Understand when to use for_each vs count to create multiple resource instances.
Learn the key differences, limitations, and best practices for each.
Master exam-style questions about resource creation patterns.
Recognize common pitfalls and when each approach is appropriate.

1. Overview: Creating Multiple Resources

Terraform provides two meta-arguments to create multiple instances of a resource:

count: Creates resources based on a number
for_each: Creates resources based on a map or set

Both serve similar purposes but have different use cases and behaviors.

2. Using `count`

Basic Syntax

resource "aws_instance" "web" {
  count = 3
  
  ami           = "ami-0123456789abcdef0"  # Example AMI ID
  instance_type = "t2.micro"
  tags = {
    Name = "web-server-${count.index}"
  }
}

What it does:

Creates 3 identical EC2 instances
count.index provides 0, 1, 2 for each instance
Resource address: aws_instance.web[0], aws_instance.web[1], aws_instance.web[2]

Referencing Resources Created with `count`

# Output all instance IDs
output "instance_ids" {
  value = aws_instance.web[*].id
}

# Output specific instance
output "first_instance_id" {
  value = aws_instance.web[0].id
}

# Reference in another resource
resource "aws_elb" "web" {
  instances = aws_instance.web[*].id
}

When to Use `count`

✅ Good for:

Creating a known number of identical resources
Simple scenarios where you just need N copies
When order/index matters

❌ Not ideal for:

Resources that need unique names/identifiers
When you might need to remove middle items (causes recreation)
Maps or sets of items with unique keys

3. Using `for_each`

Basic Syntax (with Map)

resource "aws_instance" "web" {
  for_each = {
    web-1 = "t2.micro"
    web-2 = "t3.small"
    web-3 = "t2.micro"
  }
  
  ami           = "ami-0123456789abcdef0"  # Example AMI ID
  instance_type = each.value
  tags = {
    Name = each.key
  }
}

What it does:

Creates 3 instances with unique keys: web-1, web-2, web-3
each.key = the map key (e.g., "web-1")
each.value = the map value (e.g., "t2.micro")
Resource address: aws_instance.web["web-1"], aws_instance.web["web-2"], etc.

Basic Syntax (with Set)

variable "regions" {
  type    = set(string)
  default = ["us-east-1", "us-west-2", "eu-west-1"]
}

resource "aws_s3_bucket" "logs" {
  for_each = var.regions
  
  bucket = "logs-${each.value}"
  
  provider = aws.region[each.value]
}

With sets:

each.key = the set element value
each.value = same as each.key (for sets)

Referencing Resources Created with `for_each`

# Output all instance IDs as map
output "instance_ids" {
  value = {
    for k, instance in aws_instance.web : k => instance.id
  }
}

# Output specific instance
output "web_1_id" {
  value = aws_instance.web["web-1"].id
}

# Reference in another resource
resource "aws_elb" "web" {
  instances = values(aws_instance.web)[*].id
}

When to Use `for_each`

✅ Good for:

Resources with unique identifiers (names, tags)
Maps or sets of items
When you need to add/remove specific items without affecting others
Resources that should not be recreated when list order changes

❌ Not ideal for:

Simple "create N copies" scenarios (count is simpler)
When order/index is what matters

4. Key Differences: `count` vs `for_each`

Feature	`count`	`for_each`
Input Type	Number	Map or Set
Resource Address	`resource[0]`, `resource[1]`	`resource["key"]`
Index Access	`count.index`	`each.key`, `each.value`
Removing Middle Item	Recreates all items after it	Only affects that specific item
Order Matters	✅ Yes	❌ No
Use with Maps	❌ No (convert to list)	✅ Yes
Use with Sets	❌ No	✅ Yes
Better for Unique IDs	❌ No	✅ Yes

5. Practical Comparison Examples

Example 1: Simple Web Servers

Using count:

resource "aws_instance" "web" {
  count = 3
  
  ami           = "ami-0123456789abcdef0"  # Example AMI ID
  instance_type = "t2.micro"
  tags = {
    Name = "web-${count.index + 1}"
  }
}

Using for_each:

resource "aws_instance" "web" {
  for_each = toset(["web-1", "web-2", "web-3"])
  
  ami           = "ami-0123456789abcdef0"  # Example AMI ID
  instance_type = "t2.micro"
  tags = {
    Name = each.key
  }
}

Example 2: Different Instance Types

Using for_each (better choice):

resource "aws_instance" "web" {
  for_each = {
    frontend = "t3.medium"
    backend  = "t3.large"
    cache    = "t3.small"
  }
  
  ami           = "ami-0123456789abcdef0"  # Example AMI ID
  instance_type = each.value
  tags = {
    Name   = each.key
    Role   = each.key
    Type   = each.value
  }
}

Why for_each here?

Each instance has unique configuration
Names map to roles (frontend, backend, cache)
Removing one doesn't affect others' addresses

6. Common Pitfalls and Gotchas

Pitfall 1: Removing Middle Item with `count`

# Initial: count = 3 creates [0], [1], [2]
# Change to: count = 2
# Result: [0] stays, [1] becomes new [1] (was [2]), [2] destroyed
# Old [1] is destroyed even though you only wanted to remove [2]

Solution: Use for_each if you need to remove specific items.

Pitfall 2: `for_each` Requires Map or Set

# ❌ This will ERROR
resource "aws_instance" "web" {
  for_each = ["web-1", "web-2"]  # List, not set!
}

# ✅ Correct - convert to set
resource "aws_instance" "web" {
  for_each = toset(["web-1", "web-2"])
}

Pitfall 3: Cannot Use Both `count` and `for_each`

# ❌ ERROR: Cannot use both count and for_each
resource "aws_instance" "web" {
  count    = 3
  for_each = { a = "b" }
}

You must choose one or the other.

Pitfall 4: Changing from `count` to `for_each`

# Initial state with count
resource "aws_instance" "web" {
  count = 2
  # Creates: aws_instance.web[0], aws_instance.web[1]
}

# Changing to for_each
resource "aws_instance" "web" {
  for_each = toset(["web-1", "web-2"])
  # Creates: aws_instance.web["web-1"], aws_instance.web["web-2"]
}

This will cause Terraform to destroy old resources and create new ones.
Solution: Use terraform state mv to migrate:

terraform state mv 'aws_instance.web[0]' 'aws_instance.web["web-1"]'
terraform state mv 'aws_instance.web[1]' 'aws_instance.web["web-2"]'

7. Converting Between `count` and `for_each`

Converting List to `for_each`

variable "server_names" {
  type    = list(string)
  default = ["web-1", "web-2", "web-3"]
}

# Option 1: Convert list to set
resource "aws_instance" "web" {
  for_each = toset(var.server_names)
  # ...
}

# Option 2: Convert list to map with index
resource "aws_instance" "web" {
  for_each = {
    for idx, name in var.server_names : name => idx
  }
  # ...
}

Converting Map to `count`

variable "instances" {
  type = map(string)
  default = {
    web-1 = "t2.micro"
    web-2 = "t3.small"
  }
}

# Convert map to count (loses key names)
resource "aws_instance" "web" {
  count = length(var.instances)
  
  ami           = "ami-0123456789abcdef0"  # Example AMI ID
  instance_type = values(var.instances)[count.index]
  tags = {
    Name = keys(var.instances)[count.index]
  }
}

Note: Converting map → count loses the ability to reference by key and causes issues when removing items.

8. Real-World Examples

Example 1: Multi-Region Resources

variable "regions" {
  type = set(string)
  default = ["us-east-1", "us-west-2", "eu-west-1"]
}

resource "aws_s3_bucket" "logs" {
  for_each = var.regions
  
  bucket = "company-logs-${each.value}"
  
  # Use provider alias for each region
  provider = aws.region[each.value]
}

Why for_each? Each bucket has unique name based on region key.

Example 2: Dynamic Security Groups

locals {
  security_groups = {
    web = {
      ports = [80, 443]
      cidr  = "0.0.0.0/0"
    }
    db = {
      ports = [3306]
      cidr  = "10.0.0.0/16"
    }
  }
}

resource "aws_security_group_rule" "ingress" {
  for_each = {
    for sg_name, sg_config in local.security_groups :
    sg_name => sg_config
  }
  
  type              = "ingress"
  security_group_id = aws_security_group.main[each.key].id
  from_port         = each.value.ports[0]
  to_port           = each.value.ports[0]
  protocol          = "tcp"
  cidr_blocks       = [each.value.cidr]
}

Example 3: Conditional Resource Creation

# Using count (simpler for boolean)
variable "enable_monitoring" {
  type    = bool
  default = true
}

resource "aws_cloudwatch_alarm" "cpu" {
  count = var.enable_monitoring ? 1 : 0
  
  alarm_name = "high-cpu"
  # ...
}

# Using for_each (for conditional map)
variable "environments" {
  type = map(object({
    enabled = bool
    region  = string
  }))
  default = {
    prod = { enabled = true, region = "us-east-1" }
    dev  = { enabled = false, region = "us-west-2" }
  }
}

resource "aws_instance" "app" {
  for_each = {
    for k, v in var.environments : k => v
    if v.enabled
  }
  
  # Only creates resources for enabled environments
}

9. Exam-Style Practice Questions

Question 1

You need to create 5 identical EC2 instances. Which approach is simplest? A) for_each with a set B) count = 5 C) for_each with a map D) Define 5 separate resources

Show Answer

Answer: **B** - `count = 5` is the simplest for identical resources.

Question 2

What happens if you remove the middle item from a count-based resource list? A) Only that item is removed B) All items after it are recreated C) Nothing happens D) All items are recreated

Show Answer

Answer: **B** - With `count`, removing a middle item causes all subsequent items to be recreated with new indices.

Question 3

Which data types can be used with for_each? A) List and Map B) Set and Map only C) Number and List D) Any data type

Show Answer

Answer: **B** - `for_each` only accepts maps or sets. Lists must be converted using `toset()`.

Question 4

You have a map of instance configurations with unique names. Removing one instance should not affect others. Which should you use? A) count B) for_each C) Both work the same D) Neither - use separate resources

Show Answer

Answer: **B** - `for_each` is better for maps with unique keys because removing one item doesn't affect others' addresses.

Question 5

What is the correct syntax to reference a resource created with for_each? A) aws_instance.web[0] B) aws_instance.web["web-1"] C) aws_instance.web.web-1 D) Both A and B work

Show Answer

Answer: **B** - Resources created with `for_each` use map-style addresses: `resource["key"]`. `count` uses index: `resource[0]`.

10. Decision Tree

Need to create multiple instances?
│
├─ Are they identical?
│  ├─ Yes → Use `count = N`
│  └─ No → Continue
│
├─ Do they have unique names/keys?
│  ├─ Yes → Use `for_each` with map
│  └─ No → Continue
│
├─ Is it a list of items?
│  ├─ Yes → Convert to set: `for_each = toset(list)`
│  └─ No → Continue
│
└─ Need to add/remove specific items without affecting others?
   ├─ Yes → Use `for_each`
   └─ No → `count` is fine

11. Key Takeaways

count: Use for a known number of identical resources. Creates indexed addresses [0], [1], etc.
for_each: Use for maps/sets with unique keys. Creates map-style addresses ["key"].
count limitation: Removing middle items causes recreation of subsequent items.
for_each limitation: Must use maps or sets, not plain lists.
Cannot combine: You can't use both count and for_each on the same resource.
Conversion: Lists can be converted to sets with toset() for for_each.
Migration: Changing from count to for_each requires state migration with terraform state mv.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

For Each Vs Count

Learning Objectives

1. Overview: Creating Multiple Resources

2. Using `count`

Basic Syntax

Referencing Resources Created with `count`

When to Use `count`

3. Using `for_each`

Basic Syntax (with Map)

Basic Syntax (with Set)

Referencing Resources Created with `for_each`

When to Use `for_each`

4. Key Differences: `count` vs `for_each`

5. Practical Comparison Examples

Example 1: Simple Web Servers

Example 2: Different Instance Types

6. Common Pitfalls and Gotchas

Pitfall 1: Removing Middle Item with `count`

Pitfall 2: `for_each` Requires Map or Set

Pitfall 3: Cannot Use Both `count` and `for_each`

Pitfall 4: Changing from `count` to `for_each`

7. Converting Between `count` and `for_each`

Converting List to `for_each`

Converting Map to `count`

8. Real-World Examples

Example 1: Multi-Region Resources

Example 2: Dynamic Security Groups

Example 3: Conditional Resource Creation

9. Exam-Style Practice Questions

Question 1

Question 2

Question 3

Question 4

Question 5

10. Decision Tree

11. Key Takeaways

References

FilesExpand file tree

02-for-each-vs-count.md

Latest commit

History

02-for-each-vs-count.md

File metadata and controls

For Each Vs Count

Learning Objectives

1. Overview: Creating Multiple Resources

2. Using count

Basic Syntax

Referencing Resources Created with count

When to Use count

3. Using for_each

Basic Syntax (with Map)

Basic Syntax (with Set)

Referencing Resources Created with for_each

When to Use for_each

4. Key Differences: count vs for_each

5. Practical Comparison Examples

Example 1: Simple Web Servers

Example 2: Different Instance Types

6. Common Pitfalls and Gotchas

Pitfall 1: Removing Middle Item with count

Pitfall 2: for_each Requires Map or Set

Pitfall 3: Cannot Use Both count and for_each

Pitfall 4: Changing from count to for_each

7. Converting Between count and for_each

Converting List to for_each

Converting Map to count

8. Real-World Examples

Example 1: Multi-Region Resources

Example 2: Dynamic Security Groups

Example 3: Conditional Resource Creation

9. Exam-Style Practice Questions

Question 1

Question 2

Question 3

Question 4

Question 5

10. Decision Tree

11. Key Takeaways

References

2. Using `count`

Referencing Resources Created with `count`

When to Use `count`

3. Using `for_each`

Referencing Resources Created with `for_each`

When to Use `for_each`

4. Key Differences: `count` vs `for_each`

Pitfall 1: Removing Middle Item with `count`

Pitfall 2: `for_each` Requires Map or Set

Pitfall 3: Cannot Use Both `count` and `for_each`

Pitfall 4: Changing from `count` to `for_each`

7. Converting Between `count` and `for_each`

Converting List to `for_each`

Converting Map to `count`