Terraform Registry modules - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Terraform Registry module?

A Terraform Registry module is a reusable package of Terraform configuration files shared publicly or privately to simplify infrastructure setup.

beginner

How do you add a module from the Terraform Registry to your configuration?

You add a module block with the source set to the module's address on the Terraform Registry, specifying version and inputs as needed.

beginner

Why use Terraform Registry modules instead of writing your own configuration from scratch?

Modules save time, reduce errors, and provide tested, community or vendor-supported infrastructure components you can trust.

intermediate

What is the purpose of the 'version' argument in a Terraform Registry module block?

The 'version' argument locks the module to a specific release version to ensure consistent and predictable infrastructure deployments.

intermediate

How can you find input variables required by a Terraform Registry module?

Input variables are documented on the module's Registry page and can also be found in the module's variables.tf file.

What does the 'source' attribute in a Terraform module block specify?

A The location of the module code, such as a Terraform Registry address

B The cloud provider to use

C The output variables of the module

D The Terraform version required

The 'source' attribute tells Terraform where to find the module code, often a Registry address.

Which of the following is NOT a benefit of using Terraform Registry modules?

A Reusability of infrastructure code

B Simplified configuration management

C Automatic cloud cost reduction

D Community-tested best practices

Terraform modules help with code reuse and best practices but do not automatically reduce cloud costs.

How do you specify which version of a Terraform Registry module to use?

A Using the 'version' argument inside the module block

B By naming the module folder with the version number

C By setting the Terraform CLI version

D By changing the provider version

The 'version' argument inside the module block locks the module to a specific release.

Where can you find documentation about a Terraform Registry module's inputs and outputs?

A In the Terraform state file

B In the Terraform CLI help command

C In the cloud provider's console

D On the module's page in the Terraform Registry

The Registry page lists inputs, outputs, and usage instructions for the module.

What happens if you omit the 'version' argument when using a Terraform Registry module?

A Terraform will fail to initialize

B Terraform uses the latest available version of the module

C Terraform uses the oldest version of the module

D Terraform ignores the module

Without a version specified, Terraform defaults to the latest module version.

Explain how to use a Terraform Registry module in your Terraform configuration.

Think about the block you write in your .tf files to include a module.

Describe the benefits of using Terraform Registry modules for infrastructure management.

Consider why you would choose a ready-made module over writing your own code.

Practice

1. What is the main purpose of using Terraform Registry modules in your infrastructure code?

easy

A. To reuse tested infrastructure code easily

B. To write all infrastructure code from scratch

C. To avoid using any external code

D. To manually configure cloud resources without code

Solution

1. Step 1: Understand Terraform Registry modules

   Terraform Registry modules are pre-built, reusable pieces of infrastructure code shared publicly or privately.

2. Step 2: Identify the main benefit

   Using these modules helps you avoid rewriting code and ensures you use tested, reliable configurations.

3. Final Answer:

   To reuse tested infrastructure code easily -> Option A

4. Quick Check:

   Terraform Registry modules = reuse code easily [OK]

Hint: Modules = reuse tested code, save time [OK]

Common Mistakes:

• Thinking modules require writing all code manually
• Believing modules prevent code reuse
• Confusing modules with manual resource setup

2. Which of the following is the correct syntax to include a Terraform Registry module in your configuration?

easy

A. module "example" { source = "terraform-aws-modules/vpc/aws" version = "3.0.0" }

B. resource "example" { source = "terraform-aws-modules/vpc/aws" version = "3.0.0" }

C. module "example" (source = "terraform-aws-modules/vpc/aws", version = "3.0.0")

D. include "example" { source = "terraform-aws-modules/vpc/aws" version = "3.0.0" }

Solution

1. Step 1: Recognize the correct block type

   Terraform modules are included using the module block, not resource or include.

2. Step 2: Check syntax for module block

   The correct syntax uses curly braces with key-value pairs for source and version.

3. Final Answer:

   module "example" { source = "terraform-aws-modules/vpc/aws" version = "3.0.0" } -> Option A

4. Quick Check:

   Use module block with source and version [OK]

Hint: Use module block with source and version keys [OK]

Common Mistakes:

• Using resource block instead of module
• Using parentheses instead of braces
• Using include keyword which is invalid

3. Given this Terraform module block:

module "network" {
  source  = "terraform-aws-modules/vpc/aws"
  version = "3.0.0"
  name    = "my-vpc"
  cidr    = "10.0.0.0/16"
}

What will happen when you run terraform init?

medium

A. Terraform downloads the latest version ignoring the specified version

B. Terraform throws an error because version is missing

C. Terraform downloads version 3.0.0 of the VPC module from the registry

D. Terraform ignores the module and continues without it

Solution

1. Step 1: Understand terraform init behavior with modules

   When terraform init runs, it downloads modules specified with source and version.

2. Step 2: Check version usage

   The version is specified as "3.0.0", so Terraform downloads exactly that version from the registry.

3. Final Answer:

   Terraform downloads version 3.0.0 of the VPC module from the registry -> Option C

4. Quick Check:

   terraform init downloads specified module version [OK]

Hint: terraform init downloads modules with specified version [OK]

Common Mistakes:

• Assuming version is optional and causes error
• Thinking terraform ignores version and downloads latest
• Believing terraform skips modules on init

4. You wrote this module block:

module "db" {
  source = "terraform-aws-modules/rds/aws"
  version = "1.0.0"
  engine = "mysql"
}

When running terraform init, you get an error: Module version 1.0.0 not found. What is the likely cause?

medium

A. The source URL is incorrect and does not point to a module

B. The specified version 1.0.0 does not exist in the Terraform Registry for this module

C. The engine parameter is invalid and causes version error

D. Terraform init requires internet disabled to find modules

Solution

1. Step 1: Analyze the error message

   The error says version 1.0.0 not found, meaning Terraform cannot find that version in the registry for the module.

2. Step 2: Check common causes

   Either the version is mistyped or does not exist. The source looks correct, and engine parameter does not affect version lookup.

3. Final Answer:

   The specified version 1.0.0 does not exist in the Terraform Registry for this module -> Option B

4. Quick Check:

   Version not found error = wrong or missing version [OK]

Hint: Check module version exists in registry before using [OK]

Common Mistakes:

• Blaming source URL when it is correct
• Thinking parameters cause version errors
• Assuming terraform init works offline for modules

5. You want to use a Terraform Registry module but customize it with your own settings. Which approach is best practice?

hard

A. Use the module without specifying version to always get latest

B. Copy the module code into your project and edit it directly

C. Ignore the module and write all resources manually

D. Use the module with source and version, then override variables in your configuration

Solution

1. Step 1: Understand module customization

   Terraform modules accept input variables to customize behavior without changing module code.

2. Step 2: Identify best practice

   Using source and version ensures stable code, and overriding variables lets you customize safely.

3. Final Answer:

   Use the module with source and version, then override variables in your configuration -> Option D

4. Quick Check:

   Customize modules via variables, keep source and version fixed [OK]

Hint: Override variables, don't copy module code [OK]

Common Mistakes:

• Copying module code causes maintenance issues
• Not specifying version risks unexpected changes
• Ignoring modules wastes time and effort