Why Dependency inversion with modules in Terraform? - Purpose & Use Cases

The Big Idea

Discover how breaking your cloud setup into smart blocks saves hours of headaches and endless fixes!

The Scenario

Imagine you are building a cloud setup where one part depends on another, like a web server needing a database. You write all the code in one big file, mixing everything together.

When you want to change the database or reuse the web server setup somewhere else, you have to dig through the tangled code and fix many places.

The Problem

This manual way is slow because every change risks breaking something else.

It's easy to make mistakes, and hard to test parts separately.

Sharing or reusing code is painful because everything is tightly connected.

The Solution

Dependency inversion with modules means you separate parts into independent blocks (modules).

Each module only knows what it needs, not the details of others.

This makes your setup flexible, easier to change, and reuse.

Before vs After

✗ Before

resource "aws_instance" "web" {
  ami = "ami-123"
  depends_on = [aws_db_instance.db]
}
resource "aws_db_instance" "db" {
  engine = "mysql"
}

✓ After

module "db" {
  source = "./modules/db"
}
module "web" {
  source = "./modules/web"
  db_endpoint = module.db.endpoint
}

What It Enables

You can build cloud setups that are easy to update, test, and reuse by swapping parts without breaking everything.

Real Life Example

A company wants to switch from one database provider to another without rewriting the whole infrastructure. Using modules with dependency inversion, they just replace the database module and update the web module input.

Key Takeaways

Manual cloud code mixes parts and is hard to change.

Dependency inversion with modules separates concerns and hides details.

This leads to flexible, reusable, and safer infrastructure code.

Practice

1. What does dependency inversion mean in Terraform modules?

easy

A. Modules cannot accept variables

B. Modules depend on inputs instead of creating resources themselves

C. Modules always create all resources internally

D. Modules must be written in the root configuration

Solution

1. Step 1: Understand module dependency principle

   Dependency inversion means modules should not create resources directly but rely on inputs.

2. Step 2: Identify correct description

   Modules depend on inputs instead of creating resources themselves correctly states modules depend on inputs, making them flexible and reusable.

3. Final Answer:

   Modules depend on inputs instead of creating resources themselves -> Option B

4. Quick Check:

   Dependency inversion = Modules use inputs [OK]

Hint: Modules get resource info via inputs, not by creating resources [OK]

Common Mistakes:

• Thinking modules must create all resources internally
• Assuming modules cannot accept variables
• Believing modules must be in root config

2. Which of the following is the correct way to pass a resource ID to a module in Terraform?

easy

A. module "example" { resource_id = aws_instance.example.id }

B. module "example" { input_id = aws_instance.example.id }

C. module "example" { instance_id = var.instance_id }

D. module "example" { instance_id = aws_instance.example.id }

Solution

1. Step 1: Identify correct variable passing syntax

   Modules accept variables by name; the value can be a resource attribute like aws_instance.example.id.

2. Step 2: Check option correctness

   module "example" { instance_id = aws_instance.example.id } correctly passes instance_id with the resource ID aws_instance.example.id.

3. Final Answer:

   module "example" { instance_id = aws_instance.example.id } -> Option D

4. Quick Check:

   Pass resource ID as variable = module "example" { instance_id = aws_instance.example.id } [OK]

Hint: Use variable name = resource.attribute to pass IDs [OK]

Common Mistakes:

• Using undefined variable names like resource_id or input_id
• Passing resource IDs without variable names
• Confusing variable and resource references

3. Given this Terraform root module snippet:

resource "aws_vpc" "main" {
  cidr_block = "10.0.0.0/16"
}

module "network" {
  source = "./modules/network"
  vpc_id = aws_vpc.main.id
}

What is the expected behavior of the network module?

medium

A. It ignores the VPC ID and creates a subnet only

B. It creates a new VPC inside the module

C. It uses the existing VPC ID passed as input

D. It fails because VPC ID cannot be passed as input

Solution

1. Step 1: Analyze root module resource and module call

   The root module creates an aws_vpc resource and passes its ID to the network module as vpc_id.

2. Step 2: Understand module behavior with input

   The network module uses the passed vpc_id to configure resources inside that VPC, not create a new one.

3. Final Answer:

   It uses the existing VPC ID passed as input -> Option C

4. Quick Check:

   Module uses input vpc_id = It uses the existing VPC ID passed as input [OK]

Hint: Modules use passed IDs to link resources, not recreate them [OK]

Common Mistakes:

• Assuming module creates a new VPC ignoring input
• Thinking passing resource IDs is invalid
• Believing module fails without explicit VPC creation

4. You have this module call:

module "db" {
  source = "./modules/db"
  subnet_id = aws_subnet.app.id
}

Inside the module, the variable is declared as variable "subnet" { type = string }. What error will occur?

medium

A. Error: Unknown variable 'subnet_id' in module

B. Error: Variable 'subnet' not provided

C. No error, variable names can differ

D. Error: aws_subnet.app.id is invalid

Solution

1. Step 1: Compare variable name and input argument

   The module expects a variable named 'subnet' but the input is 'subnet_id'.

2. Step 2: Understand Terraform variable matching

   Terraform matches input arguments to variable names exactly. 'subnet_id' does not match any variable, causing an unsupported argument error.

3. Final Answer:

   Error: Unknown variable 'subnet_id' in module -> Option A

4. Quick Check:

   Variable name mismatch causes unknown variable error [OK]

Hint: Variable names must match exactly between module and call [OK]

Common Mistakes:

• Assuming variable names can differ
• Confusing variable name with resource attribute name
• Ignoring error messages about missing variables

5. You want to create a reusable module for an AWS security group that attaches to any VPC. Which approach follows dependency inversion best?

hard

A. Module accepts a VPC ID as input and creates security group in that VPC

B. Module hardcodes a VPC ID inside the module code

C. Module requires the user to create security group outside and passes its ID

D. Module creates its own VPC and security group inside

Solution

1. Step 1: Understand dependency inversion for modules

   Modules should not create dependent resources like VPCs but accept them as inputs.

2. Step 2: Evaluate options for best practice

   Module accepts a VPC ID as input and creates security group in that VPC accepts VPC ID as input and creates the security group inside that VPC, following dependency inversion.

3. Final Answer:

   Module accepts a VPC ID as input and creates security group in that VPC -> Option A

4. Quick Check:

   Pass dependencies as inputs for flexibility [OK]

Hint: Pass VPC ID as input; module creates resources inside it [OK]

Common Mistakes:

• Hardcoding resource IDs inside modules
• Modules creating dependent resources themselves
• Requiring users to create resources outside without module help