Root module concept in Terraform - Commands & Configuration

Introduction

Terraform uses modules to organize infrastructure code. The root module is the main folder where you run Terraform commands. It controls what resources get created and how.

When you start a new Terraform project and want to define your infrastructure in one place.

When you want to organize your cloud resources like servers, networks, and storage together.

When you want to apply changes to your infrastructure by running Terraform commands in a single directory.

When you want to call other modules from your main configuration to keep code clean.

When you want to manage your infrastructure lifecycle with Terraform safely and predictably.

Config File - main.tf

main.tf

terraform {
  required_version = ">= 1.0"
}

provider "aws" {
  region = "us-east-1"
}

resource "aws_s3_bucket" "example_bucket" {
  bucket = "example-root-module-bucket-12345"
  acl    = "private"
}

terraform block sets the Terraform version requirement.

provider "aws" configures AWS as the cloud provider and sets the region.

resource "aws_s3_bucket" "example_bucket" defines an S3 bucket resource named example_bucket.

This file is the root module because it is the main Terraform configuration where commands are run.

Commands

Initializes the Terraform working directory. It downloads provider plugins and prepares the environment.

Terminal

terraform init

Expected Output

Initializing the backend...



Initializing provider plugins...

- Finding latest version of hashicorp/aws...

- Installing hashicorp/aws v4.0.0...

- Installed hashicorp/aws v4.0.0 (signed by HashiCorp)



Terraform has been successfully initialized!



You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure.



If you ever set or change modules or backend configuration, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary.

Shows what Terraform will do before applying changes. It helps you verify the planned infrastructure changes.

Terminal

terraform plan

Expected Output

Refreshing Terraform state in-memory prior to plan...



An execution plan has been generated and is shown below.

Resource actions are indicated with the following symbols:

  + create



Terraform will perform the following actions:



  # aws_s3_bucket.example_bucket will be created

  + resource "aws_s3_bucket" "example_bucket" {

      + acl                         = "private"

      + bucket                      = "example-root-module-bucket-12345"

      + force_destroy               = false

      + id                          = (known after apply)

      + region                      = (known after apply)

      + tags                        = (known after apply)

    }



Plan: 1 to add, 0 to change, 0 to destroy.



─────────────────────────────────────────────────────────────────────────────

Applies the planned changes to create or update infrastructure without asking for confirmation.

Terminal

terraform apply -auto-approve

Expected Output

aws_s3_bucket.example_bucket: Creating...

aws_s3_bucket.example_bucket: Creation complete after 2s [id=example-root-module-bucket-12345]



Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

→

-auto-approve - Skips interactive approval before applying changes

Displays the current state of the infrastructure managed by Terraform in a human-readable format.

Terminal

terraform show

Expected Output

aws_s3_bucket.example_bucket:

  id = example-root-module-bucket-12345

  arn = arn:aws:s3:::example-root-module-bucket-12345

  bucket = example-root-module-bucket-12345

  acl = private

Key Concept

If you remember nothing else from this pattern, remember: the root module is the main Terraform folder where you define and run your infrastructure code.

Common Mistakes

Running Terraform commands in a different folder than where main.tf is located

Terraform won't find the root module configuration and will fail or create empty state.

Always run Terraform commands in the directory containing your root module files like main.tf.

Not running 'terraform init' before other commands

Terraform needs to download providers and initialize the environment; without it, commands fail.

Run 'terraform init' once before planning or applying changes.

Summary

Create a main.tf file as the root module to define your infrastructure resources.

Run 'terraform init' to prepare the working directory and download providers.

Use 'terraform plan' to preview changes and 'terraform apply' to create resources.

The root module is the main entry point for Terraform commands and controls your infrastructure.

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