Why For_each for map-based instances in Terraform? - Purpose & Use Cases

The Big Idea

What if you could create dozens of servers with one simple list instead of dozens of repeated blocks?

The Scenario

Imagine you need to create multiple cloud servers, each with different names and settings. You write each server's setup by hand, copying and changing details for every one.

The Problem

This manual way is slow and tiring. If you want to add or change a server, you must edit many places. Mistakes happen easily, like using the wrong name or forgetting a setting.

The Solution

Using for_each with a map lets you write one block of code that automatically creates all servers. You just list the servers and their details once, and Terraform handles the rest safely and quickly.

Before vs After

✗ Before

resource "aws_instance" "server1" {
  name = "app1"
}
resource "aws_instance" "server2" {
  name = "app2"
}

✓ After

resource "aws_instance" "servers" {
  for_each = {
    app1 = "details1",
    app2 = "details2"
  }
  name = each.key
}

What It Enables

You can manage many cloud resources easily and reliably by changing just one map, saving time and avoiding errors.

Real Life Example

A company needs to launch servers in different regions with unique names. Using for_each with a map, they define all servers once and deploy them all at once without repeating code.

Key Takeaways

Manual setup is slow and error-prone.

for_each with maps automates resource creation.

It makes managing many instances simple and safe.

Practice

1. What does for_each do when used with a map in Terraform?

easy

A. Creates resources only for the first key in the map

B. Deletes all resources in the map

C. Combines all map entries into a single resource

D. Creates one resource for each key-value pair in the map

Solution

1. Step 1: Understand the role of for_each with maps

   for_each iterates over each key-value pair in a map to create multiple resources.

2. Step 2: Recognize resource creation behavior

   Each key-value pair results in one resource instance, using each.key and each.value inside the resource block.

3. Final Answer:

   Creates one resource for each key-value pair in the map -> Option D

4. Quick Check:

   for_each with map = one resource per pair [OK]

Hint: Remember: for_each maps keys to separate resources [OK]

Common Mistakes:

• Thinking for_each merges all map entries into one resource
• Assuming for_each deletes resources
• Believing for_each only uses the first map key

2. Which of the following is the correct syntax to use for_each with a map in a Terraform resource?

easy

A. resource "aws_instance" "example" { for_each = { key1 = "val1", key2 = "val2" } }

B. resource "aws_instance" "example" { for_each = ("key1", "key2") }

C. resource "aws_instance" "example" { for_each = "key1" }

D. resource "aws_instance" "example" { for_each = ["one", "two"] }

Solution

1. Step 1: Identify valid for_each types

   for_each accepts a map or set of strings, but here we focus on map usage.

2. Step 2: Check syntax correctness

   resource "aws_instance" "example" { for_each = { key1 = "val1", key2 = "val2" } } uses a map with key-value pairs correctly inside curly braces, which is valid Terraform syntax.

3. Final Answer:

   resource "aws_instance" "example" { for_each = { key1 = "val1", key2 = "val2" } } -> Option A

4. Quick Check:

   Map syntax with curly braces = correct for_each [OK]

Hint: Use curly braces for maps in for_each [OK]

Common Mistakes:

• Using square brackets for maps instead of curly braces
• Passing a single string instead of a map
• Using parentheses which are invalid here

3. Given the Terraform snippet:

variable "servers" {
  default = {
    web = "10.0.0.1"
    db  = "10.0.0.2"
  }
}

resource "aws_instance" "example" {
  for_each = var.servers
  ami           = "ami-123456"
  instance_type = "t2.micro"
  tags = {
    Name = each.key
    IP   = each.value
  }
}

What will be the value of the tag Name for the instance with IP 10.0.0.2?

medium

A. web

B. 10.0.0.2

C. db

D. example

Solution

1. Step 1: Map keys to IP addresses

   The map has keys 'web' and 'db' with values '10.0.0.1' and '10.0.0.2' respectively.

2. Step 2: Match IP to key

   The IP '10.0.0.2' corresponds to the key 'db', so the tag Name will be 'db'.

3. Final Answer:

   db -> Option C

4. Quick Check:

   each.key for IP 10.0.0.2 = db [OK]

Hint: Match IP value to map key for Name tag [OK]

Common Mistakes:

• Confusing key and value in the map
• Using IP as the Name tag instead of the key
• Assuming static tag values

4. What is wrong with this Terraform resource using for_each on a map?

resource "aws_instance" "example" {
  for_each = { "one" = "10.0.0.1", "two" = "10.0.0.2" }
  ami           = "ami-123456"
  instance_type = "t2.micro"
  tags = {
    Name = each.value
  }
  count = 2
}

medium

A. Using both for_each and count together causes an error

B. The map syntax is invalid

C. Missing each.key in tags

D. AMI ID is incorrect

Solution

1. Step 1: Check resource meta-arguments

   Terraform does not allow using both for_each and count in the same resource block.

2. Step 2: Identify the error cause

   The presence of count = 2 alongside for_each causes a configuration error.

3. Final Answer:

   Using both for_each and count together causes an error -> Option A

4. Quick Check:

   for_each and count cannot coexist [OK]

Hint: Never mix for_each and count in one resource [OK]

Common Mistakes:

• Thinking map syntax is wrong
• Believing missing each.key causes error
• Assuming AMI ID is the problem

5. You have a map of server roles and IPs:

servers = {
  app1 = "10.0.1.1"
  app2 = ""
  app3 = "10.0.1.3"
  app4 = null
}

You want to create AWS instances only for servers with valid IPs using for_each. Which expression correctly filters the map to exclude empty or null IPs?

hard

A. for_each = var.servers

B. for_each = { for k, v in var.servers : k => v if v != "" && v != null }

C. for_each = { for k, v in var.servers : k => v if v == "" || v == null }

D. for_each = [ for v in var.servers : v if v != "" ]

Solution

1. Step 1: Understand filtering with for expressions

   Use a for expression with an if condition to filter out empty strings and null values from the map.

2. Step 2: Check each option

   for_each = { for k, v in var.servers : k => v if v != "" && v != null } correctly filters keys where value is neither empty string nor null, producing a valid filtered map for for_each.

3. Final Answer:

   for_each = { for k, v in var.servers : k => v if v != "" && v != null } -> Option B

4. Quick Check:

   Filter map with if condition to exclude empty/null [OK]

Hint: Filter map with for and if to exclude empty/null [OK]

Common Mistakes:

• Not filtering out empty or null values
• Using list comprehension instead of map
• Filtering for empty/null instead of excluding them