Root module concept in Terraform - Mini Project: Build & Apply

Terraform Root Module Setup

📖 Scenario: You are setting up a basic Terraform project to manage cloud infrastructure. The root module is the main folder where Terraform configuration files live. It defines resources and variables for your infrastructure.

🎯 Goal: Build a simple Terraform root module that defines a provider and a resource with variables.

📋 What You'll Learn

Create a Terraform configuration file named main.tf.

Define the aws provider with a region variable.

Create a resource of type aws_s3_bucket with a bucket name variable.

Use variables for region and bucket name with default values.

💡 Why This Matters

🌍 Real World

Terraform root modules are the starting point for managing cloud infrastructure as code. They organize resources and variables in one place.

💼 Career

Understanding root modules is essential for cloud engineers and DevOps professionals to build and maintain infrastructure reliably and repeatably.

1

Create the Terraform provider block

In the main.tf file, write a Terraform provider block for aws using the variable region for the region setting.

Terraform

# Your code here

Hint

The provider block tells Terraform which cloud provider to use. Use var.region to get the region from a variable.

2

Add variables for region and bucket name

Below the provider block in main.tf, add two variable blocks named region and bucket_name. Set their default values to "us-east-1" and "my-terraform-bucket" respectively.

Terraform

provider "aws" {
  region = var.region
}

# Your code here

Hint

Variables let you customize your Terraform configuration. Use variable "name" { default = "value" } syntax.

3

Create an S3 bucket resource using the bucket_name variable

Add a resource block of type aws_s3_bucket named my_bucket in main.tf. Set the bucket attribute to use the variable bucket_name.

Terraform

provider "aws" {
  region = var.region
}

variable "region" {
  default = "us-east-1"
}

variable "bucket_name" {
  default = "my-terraform-bucket"
}

# Your code here

Hint

Resources define infrastructure components. Use resource "type" "name" { attribute = value } syntax.

4

Add output to show the bucket name

Add an output block named bucket_name_output in main.tf that outputs the value of the aws_s3_bucket.my_bucket.bucket attribute.

Terraform

provider "aws" {
  region = var.region
}

variable "region" {
  default = "us-east-1"
}

variable "bucket_name" {
  default = "my-terraform-bucket"
}

resource "aws_s3_bucket" "my_bucket" {
  bucket = var.bucket_name
}

# Your code here

Hint

Outputs let you see important information after Terraform applies changes. Use output "name" { value = ... } syntax.

Practice

1. What is the root module in Terraform?

easy

A. A Terraform provider plugin

B. A special Terraform resource type

C. A remote backend configuration

D. The main folder where Terraform commands are run and resources are defined

Solution

1. Step 1: Understand the root module role

   The root module is the main folder where you write your Terraform code and run commands.

2. Step 2: Differentiate from other concepts

   It is not a resource type, backend, or provider plugin but the main working directory.

3. Final Answer:

   The main folder where Terraform commands are run and resources are defined -> Option D

4. Quick Check:

   Root module = main Terraform folder [OK]

Hint: Root module is your main Terraform folder [OK]

Common Mistakes:

• Confusing root module with provider or backend
• Thinking root module is a resource type
• Assuming root module is a plugin

2. Which command must be run inside the root module folder to initialize Terraform?

easy

A. terraform apply

B. terraform init

C. terraform plan

D. terraform validate

Solution

1. Step 1: Identify the initialization command

   terraform init sets up the working directory by downloading providers and preparing the backend.

2. Step 2: Confirm command location

   This command must be run inside the root module folder where the Terraform files exist.

3. Final Answer:

   terraform init -> Option B

4. Quick Check:

   Initialize Terraform = terraform init [OK]

Hint: Use 'terraform init' to start in root module folder [OK]

Common Mistakes:

• Running terraform apply before init
• Confusing init with plan or validate
• Running commands outside root module folder

3. Given this root module folder structure:

root-module/
  main.tf
  variables.tf
  modules/
    network/
      main.tf

Which statement is true about the root module?

medium

A. It can call the network module inside the modules folder

B. It must be empty to work correctly

C. It cannot use modules from subfolders

D. It only contains variables and no resources

Solution

1. Step 1: Understand root module and submodules

   The root module can call other modules located in subfolders like modules/network.

2. Step 2: Evaluate options

   It can call the network module inside the modules folder correctly states the root module can call the network module. Other options are false.

3. Final Answer:

   It can call the network module inside the modules folder -> Option A

4. Quick Check:

   Root module calls submodules = true [OK]

Hint: Root module can call modules in subfolders [OK]

Common Mistakes:

• Thinking root module cannot use submodules
• Assuming root module must be empty
• Believing root module only has variables

4. You run terraform apply in your root module folder but get an error: "No configuration files found". What is the likely cause?

medium

A. You ran the command outside the root module folder

B. You forgot to run terraform init first

C. Your Terraform version is outdated

D. You have no internet connection

Solution

1. Step 1: Analyze the error message

   "No configuration files found" means Terraform cannot find .tf files in the current folder.

2. Step 2: Identify common cause

   This usually happens if you run terraform apply outside the root module folder where the files exist.

3. Final Answer:

   You ran the command outside the root module folder -> Option A

4. Quick Check:

   Run commands inside root module folder [OK]

Hint: Run commands inside root module folder with .tf files [OK]

Common Mistakes:

• Assuming init missing causes this error
• Blaming Terraform version or internet
• Not checking current folder location

5. You want to organize your Terraform project with a root module that calls two child modules: network and compute. Which folder structure and root module code is correct?

hard

A. root/
main.tf
network.tf
compute.tf

# main.tf does not call modules

B. root/
network/
main.tf
compute/
main.tf

# main.tf calls modules from root folder

C. root/
main.tf
modules/
network/
main.tf
compute/
main.tf

# main.tf calls both modules with module blocks

D. root/
main.tf
modules/
network/
main.tf
compute/
main.tf

# main.tf does not call any modules

Solution

1. Step 1: Understand proper module folder structure

   Child modules should be inside a modules folder under root for clarity and best practice.

2. Step 2: Confirm root module calls child modules

   The root module's main.tf must include module blocks to call network and compute modules.

3. Final Answer:

   Folder with modules subfolder and main.tf calling modules -> Option C

4. Quick Check:

   Root calls modules in modules/ folder [OK]

Hint: Put child modules in modules/ and call them in root main.tf [OK]

Common Mistakes:

• Placing modules outside modules/ folder
• Not calling modules in root main.tf
• Confusing separate folders as root module