Terraform file organization - Commands & Configuration

Introduction

When you build infrastructure with Terraform, organizing your files well helps you find things easily and avoid mistakes. Good file organization keeps your setup clear and simple to manage.

When your Terraform setup grows beyond a single file and you want to keep related resources grouped.

When you want to separate variables, outputs, and resource definitions for clarity.

When you work with a team and want everyone to understand the structure quickly.

When you plan to reuse parts of your configuration in different projects.

When you want to keep sensitive information separate from main resource files.

Config File - main.tf

main.tf

terraform {
  required_version = ">= 1.0"
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 4.0"
    }
  }
}

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

resource "aws_instance" "example" {
  ami           = var.ami_id
  instance_type = var.instance_type
  tags = {
    Name = "example-instance"
  }
}

This file sets the Terraform version and AWS provider details. It also defines an AWS EC2 instance resource using variables for the AMI ID and instance type.

Separate files like variables.tf and outputs.tf would hold variable definitions and outputs respectively to keep things organized.

Commands

This command initializes the Terraform working directory. It downloads the provider plugins and prepares the environment to run Terraform commands.

Terminal

terraform init

Expected Output

Initializing the backend...



Initializing provider plugins...

- Finding hashicorp/aws versions matching "~> 4.0"...

- 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.

This command checks your Terraform files for syntax errors and basic mistakes without making any changes to real infrastructure.

Terminal

terraform validate

Expected Output

Success! The configuration is valid.

This command shows what Terraform will do when you apply your configuration. It previews the changes without making them.

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_instance.example will be created

  + resource "aws_instance" "example" {

      + ami           = "ami-0c55b159cbfafe1f0"

      + instance_type = "t2.micro"

      + tags          = {

          + "Name" = "example-instance"

        }

    }



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

This command applies the planned changes to create or update your infrastructure. The flag skips the confirmation prompt to make it faster.

Terminal

terraform apply -auto-approve

Expected Output

aws_instance.example: Creating...

aws_instance.example: Still creating... [10s elapsed]

aws_instance.example: Creation complete after 15s [id=i-0abcd1234efgh5678]



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

→

-auto-approve - Skips the manual approval step to apply changes immediately.

Key Concept

If you remember nothing else from this pattern, remember: organizing Terraform files by purpose (variables, resources, outputs) keeps your infrastructure code clear and easy to manage.

Common Mistakes

Putting all Terraform code in one big file.

It becomes hard to find and update parts of your setup, leading to mistakes and confusion.

Split your code into multiple files like variables.tf, main.tf, and outputs.tf to separate concerns.

Not running terraform validate before applying changes.

You might apply broken or invalid configurations that cause errors or unexpected results.

Always run terraform validate to catch syntax errors early.

Ignoring terraform init when starting a new project or after changing providers.

Terraform won't download necessary plugins, causing commands to fail.

Run terraform init to prepare your working directory before other commands.

Summary

Use separate Terraform files to organize variables, resources, and outputs clearly.

Run terraform init to set up your environment before planning or applying changes.

Use terraform validate to check your files for errors before applying.

Use terraform plan to preview changes and terraform apply to make them happen.