Why dynamic blocks reduce repetition in Terraform - The Real Reasons

The Big Idea

Discover how one simple feature can save you hours of repetitive work and headaches!

The Scenario

Imagine you need to create many similar parts in your cloud setup, like multiple firewall rules or repeated resource settings. Writing each one by hand means copying and changing the same code again and again.

The Problem

Manually repeating code is slow and tiring. It's easy to make mistakes, like forgetting to update a value or adding inconsistent settings. This can cause errors and waste time fixing them.

The Solution

Dynamic blocks let you write the repeated part just once and tell the system to create many copies with different details automatically. This keeps your code clean, easy to read, and less error-prone.

Before vs After

✗ Before

resource "aws_security_group" "example" {
  ingress {
    from_port = 80
    to_port = 80
    protocol = "tcp"
    cidr_blocks = ["0.0.0.0/0"]
  }
  ingress {
    from_port = 443
    to_port = 443
    protocol = "tcp"
    cidr_blocks = ["0.0.0.0/0"]
  }
}

✓ After

resource "aws_security_group" "example" {
  dynamic "ingress" {
    for_each = [80, 443]
    content {
      from_port = ingress.value
      to_port = ingress.value
      protocol = "tcp"
      cidr_blocks = ["0.0.0.0/0"]
    }
  }
}

What It Enables

You can quickly create many similar configurations with less code, making your cloud setup faster and safer to manage.

Real Life Example

When setting up a firewall, instead of writing each rule separately, you use dynamic blocks to generate all needed rules from a list of ports, saving time and avoiding mistakes.

Key Takeaways

Manual repetition wastes time and risks errors.

Dynamic blocks automate repeated code parts.

This leads to cleaner, safer, and faster cloud configurations.

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