HCL Basics Understanding Block Structure

Terraform configurations use the HashiCorp Configuration Language (HCL), a block-oriented syntax designed to be both human-readable and machine-friendly. Understanding HCL’s block structure is key to writing clear, maintainable, and reusable infrastructure-as-code. Why block-oriented HCL matters

Clear structure: Each block type has an explicit responsibility, which improves readability and simplifies reviews.
Flexibility and modularity: Use only the block types required for a given task — combine them as needed to model your infrastructure.
Reusable patterns: Well-defined blocks make modules and shared patterns easier to maintain and scale across teams.

Quick overview — common block types

provider: Connects Terraform to a target platform (AWS, Azure, GCP, etc.). Acts as the adapter to the platform’s API.
resource: Declares the resources Terraform will create and manage (VMs, networks, storage).
data: Reads information about existing resources or remote data sources without creating them.
variable: Parameterizes values so configurations are reusable across environments.
output: Exposes values from a run for use by users, CI/CD systems, or other modules.
terraform: Configures Terraform-specific settings, e.g., backends and required providers.
module: Groups related resources into reusable units by referencing other directories or remote modules.
import (conceptual): Not an HCL block — terraform import CLI brings existing resources into state management.

Summary table of block types, uses, and short examples

Block type	Typical use case	Example (single-line)
provider	Configure authentication and API endpoints for a platform	`provider "aws" { region = "us-west-2" }`
resource	Create or manage infrastructure objects	`resource "aws_instance" "web" { ami = "ami-123", instance_type = "t2.micro" }`
data	Reference existing resources or remote data	`data "aws_ami" "ubuntu" { most_recent = true, owners = ["099720109477"] }`
variable	Define configurable inputs for modules or root modules	`variable "instance_count" { type = number, default = 2 }`
output	Export computed values after apply	`output "instance_ip" { value = aws_instance.web.public_ip }`
terraform	Configure CLI/Backend behavior and provider constraints	`terraform { required_version = ">= 1.0" }`
module	Reuse and compose configuration from another folder or registry	`module "network" { source = "./modules/network" }`
import (conceptual)	Bring external resources into Terraform state (CLI)	Use the `terraform import` command (no HCL block)

Practical examples provider block

provider "aws" {
  region = "us-west-2"
}

resource block

resource "aws_instance" "web" {
  ami           = "ami-0abcdef1234567890"
  instance_type = "t2.micro"
  tags = {
    Name = "web-server"
  }
}

data block

data "aws_ami" "ubuntu" {
  most_recent = true
  owners      = ["099720109477"]
  filter {
    name   = "name"
    values = ["ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-*"]
  }
}

variable and output

variable "instance_count" {
  type    = number
  default = 2
}

output "web_ips" {
  value = aws_instance.web.*.public_ip
}

module and terraform

terraform {
  required_version = ">= 1.0"
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "prod/terraform.tfstate"
    region = "us-west-2"
  }
}

module "network" {
  source = "./modules/network"
  cidr   = "10.0.0.0/16"
}

Additional tips

Order is flexible: HCL does not require a strict order for blocks, but grouping related blocks improves readability.
Keep modules focused: Design modules to do one thing well (networking, compute, storage) and expose a small set of variables and outputs.
Use terraform fmt and terraform validate as part of CI to enforce style and catch errors early.

An infographic titled "Terraform Block Types" showing labeled boxes for blocks like provider, resource, data, variable, output, terraform, module, and import. Each box gives a one-line description of that block's purpose in Terraform configurations.

Note that while the infographic includes “import” for conceptual completeness, Terraform does not provide an HCL “import” block. To bring existing resources into Terraform’s state, use the terraform import CLI command.

With that foundation, we’ll now examine the provider block. Further reading and references

Terraform documentation — https://www.terraform.io/docs
HCL language documentation — https://github.com/hashicorp/hcl
Terraform CLI: terraform import — https://www.terraform.io/cli/import

Course Introduction

Preparing Your Environment

Terraform Foundations

The Core Terraform Workflow

Terraform CLI

Terraform File Structure and Organization

Terraform Configuration - Fundamentals

Understading and Managing Terraform State

Marking Code Reusable

Refactoring Terraform State

Terraform Modules

Managing Resource Behavior and Dependencies

Securing Terraform Configurations

Terraform Troubleshooting

HCP Terraform

HCL Basics Understanding Block Structure

Watch Video