Why dynamic blocks reduce repetition in Terraform - Visual Breakdown

Process Flow - Why dynamic blocks reduce repetition

Start with repeated blocks

↓

Identify repeated pattern

↓

Create dynamic block with for_each

↓

Terraform loops over items

↓

Generates multiple blocks dynamically

↓

Result: Less code, easier changes

↓

End

Dynamic blocks let Terraform repeat similar blocks automatically, so you write less code and avoid copying the same structure many times.

Execution Sample

Terraform

resource "aws_security_group" "example" {
  name = "example"

  dynamic "ingress" {
    for_each = var.ingress_rules
    content {
      from_port   = ingress.value.from_port
      to_port     = ingress.value.to_port
      protocol    = ingress.value.protocol
      cidr_blocks = ingress.value.cidr_blocks
    }
  }
}

This Terraform code uses a dynamic block to create multiple ingress rules from a list, instead of writing each rule manually.

Process Table

Step	Action	Input	Output	Notes
1	Start resource definition	No ingress rules yet	Resource block with dynamic ingress block	Setup for dynamic block processing
2	Evaluate for_each	var.ingress_rules list with 2 rules	Loop over 2 ingress rules	Terraform prepares to create 2 ingress blocks
3	First iteration	ingress.value = first rule	Create ingress block with first rule's ports and CIDRs	First ingress block generated
4	Second iteration	ingress.value = second rule	Create ingress block with second rule's ports and CIDRs	Second ingress block generated
5	Finish dynamic block	All rules processed	Resource has 2 ingress blocks	Dynamic block replaced repetition
6	Apply resource	Resource with 2 ingress blocks	Security group created with 2 ingress rules	Deployment reflects dynamic blocks

💡 All ingress rules processed, dynamic block replaced repeated code blocks

Status Tracker

Variable	Start	After 1	After 2	Final
ingress.value	undefined	{from_port=80, to_port=80, protocol="tcp", cidr_blocks=["0.0.0.0/0"]}	{from_port=443, to_port=443, protocol="tcp", cidr_blocks=["0.0.0.0/0"]}	No more rules

Key Moments - 3 Insights

Why does Terraform loop over var.ingress_rules in the dynamic block?

Terraform uses the for_each expression to repeat the block for each item in var.ingress_rules, as shown in execution_table rows 2-4.

How does using a dynamic block reduce repetition compared to writing blocks manually?

Instead of writing each ingress block by hand, the dynamic block automatically creates them for each rule, reducing code duplication (see execution_table rows 3 and 4).

What happens if var.ingress_rules is empty?

The dynamic block creates zero ingress blocks, so no repeated blocks appear, avoiding empty or unused code sections.

Visual Quiz - 3 Questions

Look at the execution_table, what is ingress.value during the second iteration?

A {from_port=80, to_port=80, protocol="tcp", cidr_blocks=["0.0.0.0/0"]}

B {from_port=443, to_port=443, protocol="tcp", cidr_blocks=["0.0.0.0/0"]}

C undefined

D Empty list

💡 Hint

Check execution_table row 4 under Input column

At which step does Terraform finish creating all ingress blocks?

A Step 5

B Step 4

C Step 3

D Step 6

💡 Hint

Look for 'Finish dynamic block' in execution_table

If var.ingress_rules had 3 rules instead of 2, how would execution_table change?

A Terraform would error out

B The number of iterations stays 2

C There would be 3 iterations creating ingress blocks

D Only the first 2 rules are processed

💡 Hint

Refer to how for_each loops over all items in the list (execution_table rows 2-4)

Concept Snapshot

Terraform dynamic blocks let you write one block that repeats for each item in a list.
Use for_each inside dynamic to loop.
Terraform creates one block per item automatically.
This reduces manual repetition and makes code cleaner.
If the list is empty, no blocks are created.
Dynamic blocks improve maintainability and reduce errors.

Full Transcript

This visual execution shows how Terraform dynamic blocks reduce repetition by looping over a list of ingress rules. Initially, the resource has a dynamic block with for_each set to var.ingress_rules. Terraform evaluates the list and loops over each rule. For each iteration, it creates an ingress block with the rule's ports and CIDRs. After processing all rules, the resource ends up with multiple ingress blocks without manually writing each one. Variables like ingress.value change each iteration to the current rule. This approach avoids copying the same block multiple times and makes the code easier to maintain. If the list is empty, no ingress blocks are created, keeping the resource clean. The execution table traces each step from start to finish, showing how the dynamic block replaces repeated code with a loop.

Practice

1. What is the main benefit of using dynamic blocks in Terraform?

easy

A. They replace the need for variables in Terraform configurations.

B. They improve the speed of Terraform plan and apply operations.

C. They reduce repetition by generating multiple nested blocks automatically.

D. They allow Terraform to run without a backend configuration.

Solution

1. Step 1: Understand the purpose of dynamic blocks

   Dynamic blocks let you create repeated nested blocks from a list or map without manually copying code.

2. Step 2: Compare benefits

   This reduces repetition and keeps code clean and scalable, unlike options about speed, variables, or backend.

3. Final Answer:

   They reduce repetition by generating multiple nested blocks automatically. -> Option C

4. Quick Check:

   Dynamic blocks reduce repetition = C [OK]

Hint: Dynamic blocks create repeated blocks from lists automatically [OK]

Common Mistakes:

• Thinking dynamic blocks speed up Terraform execution
• Confusing dynamic blocks with variables
• Believing dynamic blocks remove backend needs

2. Which of the following is the correct syntax to start a dynamic block in Terraform?

easy

A. dynamic "block_name" { for_each = var.list }

B. dynamic block_name { for_each = var.list }

C. dynamic block_name = var.list { }

D. dynamic "block_name" = var.list { }

Solution

1. Step 1: Recall dynamic block syntax

   Dynamic blocks use the keyword dynamic followed by the block name in quotes, then a block with for_each.

2. Step 2: Match syntax to options

   Only dynamic "block_name" { for_each = var.list } matches the correct syntax: dynamic "block_name" { for_each = var.list }.

3. Final Answer:

   dynamic "block_name" { for_each = var.list } -> Option A

4. Quick Check:

   Correct dynamic block syntax = D [OK]

Hint: Dynamic block name must be in quotes after keyword dynamic [OK]

Common Mistakes:

• Omitting quotes around block name
• Using equals sign instead of braces
• Placing for_each outside the block

3. Given this Terraform snippet:

variable "ports" { default = [80, 443] }

resource "aws_security_group" "example" {
  name = "example"

  dynamic "ingress" {
    for_each = var.ports
    content {
      from_port   = ingress.value
      to_port     = ingress.value
      protocol    = "tcp"
      cidr_blocks = ["0.0.0.0/0"]
    }
  }
}

How many ingress blocks will be created in the security group?

medium

A. Depends on AWS region

B. 1

C. 0

D. 2

Solution

1. Step 1: Analyze the for_each list

   The variable ports contains two values: 80 and 443.

2. Step 2: Count dynamic block iterations

   The dynamic block creates one ingress block per item in var.ports, so 2 blocks total.

3. Final Answer:

   2 -> Option D

4. Quick Check:

   List length = number of blocks = 2 [OK]

Hint: Dynamic blocks create one nested block per list item [OK]

Common Mistakes:

• Assuming only one block is created
• Thinking AWS region affects block count
• Confusing dynamic block with static block

4. Identify the error in this Terraform dynamic block snippet:

dynamic "egress" {
  for_each = var.rules
  content = {
    from_port   = egress.value.from
    to_port     = egress.value.to
    protocol    = "tcp"
  }
}

medium

A. Incorrect use of equals sign for content block

B. Missing quotes around block name "egress"

C. for_each must be outside the dynamic block

D. Variable var.rules cannot be used in dynamic blocks

Solution

1. Step 1: Check dynamic block content syntax

   The content must be a block, not assigned with equals sign.

2. Step 2: Identify correct syntax

   Correct syntax uses content { ... } without equals sign. The snippet incorrectly uses content = { ... }.

3. Final Answer:

   Incorrect use of equals sign for content block -> Option A

4. Quick Check:

   content block uses braces, no equals sign = B [OK]

Hint: Use content { } block, not content = { } [OK]

Common Mistakes:

• Using equals sign with content
• Placing for_each outside dynamic block
• Misquoting block name

5. You want to create multiple lifecycle_rule blocks in an aws_s3_bucket resource using a dynamic block. Your variable is a map with keys as rule names and values as rule details. Which approach correctly uses dynamic blocks to reduce repetition and handle the map structure?

hard

A. Use for_each = var.rules and access each rule with lifecycle_rule.key only inside content block.

B. Use for_each = var.rules and access each rule with lifecycle_rule.value inside content block.

C. Use count = length(var.rules) and index into var.rules inside content block.

D. Manually write each lifecycle_rule block without dynamic blocks.

Solution

1. Step 1: Understand dynamic block with map variable

   When using a map, for_each iterates over key-value pairs. The value is accessed with lifecycle_rule.value.

2. Step 2: Identify correct usage

   Use for_each = var.rules and access each rule with lifecycle_rule.value inside content block. correctly uses for_each = var.rules and accesses lifecycle_rule.value inside the content block to get rule details.

3. Final Answer:

   Use for_each = var.rules and access each rule with lifecycle_rule.value inside content block. -> Option B

4. Quick Check:

   Map iteration uses .value for content = A [OK]

Hint: Use .value to access map values inside dynamic block content [OK]

Common Mistakes:

• Using only .key without .value for map data
• Using count instead of for_each for maps
• Writing blocks manually instead of dynamic