Module outputs in Terraform - Time & Space Complexity

Time Complexity: Module outputs

O(n)

Understanding Time Complexity

When using Terraform modules, outputs let us share information from one module to another.

We want to understand how the time to get these outputs changes as we add more outputs.

Scenario Under Consideration

Analyze the time complexity of retrieving outputs from a module.

module "example" {
  source = "./modules/example"
  count  = var.instance_count
}

output "instance_ids" {
  value = [for m in module.example : m.instance_id]
}
    

This code calls a module multiple times and collects all instance IDs as output.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Retrieving each module instance's output value.
• How many times: Once per module instance (equal to var.instance_count).

How Execution Grows With Input

As the number of module instances grows, the number of output retrievals grows the same way.

Input Size (n)	Approx. API Calls/Operations
10	10 output retrievals
100	100 output retrievals
1000	1000 output retrievals

Pattern observation: The work grows directly with the number of module instances.

Final Time Complexity

Time Complexity: O(n)

This means the time to get all outputs grows in a straight line as you add more module instances.

Common Mistake

[X] Wrong: "Getting outputs from multiple modules happens all at once, so time stays the same no matter how many modules there are."

[OK] Correct: Each module output must be retrieved separately, so more modules mean more work and more time.

Interview Connect

Understanding how output retrieval scales helps you design efficient Terraform modules and predict deployment times.

Self-Check

"What if we combined all outputs into a single map inside the module instead of separate outputs? How would the time complexity change?"

Practice

1. What is the main purpose of output blocks in a Terraform module?

easy

A. To share information from inside the module to the outside

B. To define variables that the module accepts

C. To create resources inside the module

D. To delete resources after deployment

Solution

1. Step 1: Understand the role of output blocks

   Output blocks are used to expose values from a module so other parts of the Terraform configuration can use them.

2. Step 2: Differentiate outputs from variables and resources

   Variables are inputs to modules, resources create infrastructure, outputs share info outwards.

3. Final Answer:

   To share information from inside the module to the outside -> Option A

4. Quick Check:

   Outputs = share info outside module [OK]

Hint: Outputs pass info out of modules, variables bring info in [OK]

Common Mistakes:

• Confusing outputs with variables
• Thinking outputs create resources
• Assuming outputs delete resources

2. Which of the following is the correct syntax to define an output named instance_ip in a Terraform module?

easy

A. output "instance_ip" : aws_instance.example.public_ip

B. output instance_ip = aws_instance.example.public_ip

C. output "instance_ip" { value = aws_instance.example.public_ip }

D. output { instance_ip = aws_instance.example.public_ip }

Solution

1. Step 1: Recall Terraform output block syntax

   Outputs use the keyword output followed by the name in quotes, then a block with value = ....

2. Step 2: Match syntax to options

   output "instance_ip" { value = aws_instance.example.public_ip } matches the correct syntax: output "name" { value = ... }.

3. Final Answer:

   output "instance_ip" { value = aws_instance.example.public_ip } -> Option C

4. Quick Check:

   Output block = output "name" { value = ... } [OK]

Hint: Outputs need quotes and value assignment inside braces [OK]

Common Mistakes:

• Missing quotes around output name
• Using equals sign outside block
• Incorrect colon or braces placement

3. Given this module output block:

output "bucket_name" {
  value = aws_s3_bucket.my_bucket.id
}

And this root module code:

module "storage" {
  source = "./modules/s3"
}

output "name" {
  value = module.storage.bucket_name
}

What will be the value of the root module's name output after applying?

medium

A. The name of the S3 bucket resource type

B. Null because the module output is not defined

C. An error because outputs cannot be nested

D. The ID of the S3 bucket created by the module

Solution

1. Step 1: Understand module output propagation

   The module outputs the bucket's ID as bucket_name. The root module accesses it via module.storage.bucket_name.

2. Step 2: Confirm root output value

   The root output name simply passes through the module's output value, so it will be the bucket ID.

3. Final Answer:

   The ID of the S3 bucket created by the module -> Option D

4. Quick Check:

   Root output = module output value [OK]

Hint: Root outputs can reference module outputs directly [OK]

Common Mistakes:

• Thinking outputs cannot be nested or chained
• Confusing bucket ID with resource type name
• Assuming output is null if not explicitly set in root

4. You have this output block inside a module:

output "subnet_id" {
  value = aws_subnet.example
}

Why is this incorrect for outputting the subnet ID?

medium

A. The output value should reference a specific attribute, like aws_subnet.example.id

B. Output blocks cannot reference resources directly

C. The output name cannot be "subnet_id"

D. The module source path is missing

Solution

1. Step 1: Check output value correctness

   To output the subnet ID, the value must reference a specific attribute like aws_subnet.example.id, not the whole resource object.

2. Step 2: Identify correct attribute to output

   For subnet ID, use aws_subnet.example.id instead of the resource itself.

3. Final Answer:

   The output value should reference a specific attribute, like aws_subnet.example.id -> Option A

4. Quick Check:

   Output value = resource attribute, not resource object [OK]

Hint: Always output resource attributes, not whole resources [OK]

Common Mistakes:

• Outputting entire resource instead of attribute
• Wrong output block name
• Ignoring module source configuration

5. You want to create a module that outputs a list of public IPs from multiple instances it creates. Which output block correctly returns this list?

hard

A. output "public_ips" { value = aws_instance.example[0].public_ip }

B. output "public_ips" { value = [for inst in aws_instance.example : inst.public_ip] }

C. output "public_ips" { value = aws_instance.example[*].id }

D. output "public_ips" { value = aws_instance.example }

Solution

1. Step 1: Understand how to output multiple values

   When multiple instances exist, use a for-expression to collect their public IPs into a list.

2. Step 2: Match correct syntax for list output

   output "public_ips" { value = [for inst in aws_instance.example : inst.public_ip] } uses a for-expression to extract public_ip from each instance correctly.

3. Final Answer:

   output "public_ips" { value = [for inst in aws_instance.example : inst.public_ip] } -> Option B

4. Quick Check:

   Use for-expression to output lists from multiple resources [OK]

Hint: Use for-expressions to gather attributes from multiple resources [OK]

Common Mistakes:

• Outputting single attribute from multiple instances without list
• Using wrong attribute like id instead of public_ip
• Outputting entire resource object