In this project, I used Terraform to define and manage AWS infrastructure through reusable configuration files. Just as a construction manager uses a blueprint to build consistent structures, Terraform uses .tf files to provision consistent cloud environments.
This infographic explains the Terraform lifecycle through a practical construction-site analogy.
Terraform is an Infrastructure as Code tool created by HashiCorp. It allows infrastructure to be defined, reviewed, version-controlled and provisioned through code.
Instead of manually creating resources through the AWS Management Console, Terraform allows engineers to define resources such as VPCs, subnets, EC2 instances, security groups, load balancers, databases and EKS clusters in configuration files.
Terraform follows a predictable workflow that helps engineers validate, review and safely provision cloud infrastructure.
Formats Terraform configuration files into a consistent and readable structure.
terraform fmt
Checks the configuration for syntax and structural errors.
terraform validate
Generates a preview of the resources Terraform intends to create, update or destroy.
terraform plan
Executes the approved plan and provisions the required infrastructure.
terraform apply
Safely removes the resources managed by the Terraform configuration.
terraform destroy
The configuration can create interconnected AWS resources while Terraform automatically determines their dependency order.
Desired infrastructure
Connects Terraform to AWS
Networking foundation
Traffic control
Application compute
Terraform improves reliability, repeatability and collaboration throughout the infrastructure lifecycle.
The same configuration can be used to create consistent infrastructure across multiple environments.
Resources are created from tested definitions rather than different manual console steps.
Terraform files can be stored in Git, reviewed through pull requests and tracked over time.
Teams can share modules, review proposed changes and maintain a common infrastructure design.
Terraform can manage a few resources or large, interconnected cloud environments.
Terraform can identify differences between the desired configuration and the actual cloud infrastructure.
Terraform can support cloud provisioning, application modernization, DevOps automation and enterprise platform management.
Create VPCs, subnets, route tables, gateways, EC2 instances, load balancers, databases and storage.
Use reusable Terraform code to provision Development, QA, UAT and Production environments consistently.
Provision Amazon EKS clusters, managed node groups, IAM roles and supporting networking components.
Integrate Terraform into deployment pipelines to review and provision infrastructure automatically.
Package frequently used infrastructure patterns into reusable modules for different teams and applications.
Use different Terraform providers to manage AWS, Azure, Google Cloud, Kubernetes, GitHub and other platforms.
These commands support the complete Terraform lifecycle, from initialization and validation to deployment and cleanup.
| Command | Purpose | Typical Use |
|---|---|---|
terraform init
|
Initializes the working directory and downloads the required providers and modules. | Run when starting a project or after changing providers, modules or backend configuration. |
terraform fmt
|
Formats Terraform configuration files. | Run before committing Terraform code to Git. |
terraform validate
|
Validates Terraform syntax and configuration structure. | Used to find configuration errors before planning. |
terraform plan
|
Displays the proposed infrastructure changes. | Review resources that will be added, changed or destroyed. |
terraform apply
|
Executes the proposed infrastructure changes. | Creates, updates or removes cloud resources. |
terraform show
|
Displays the current state or a saved execution plan. | Inspect details about Terraform-managed resources. |
terraform output
|
Displays values declared in output blocks. | Retrieve public IP addresses, DNS names, resource IDs and other useful values. |
terraform state list
|
Lists the resources currently tracked in Terraform state. | Review which resources are under Terraform management. |
terraform refresh
|
Updates Terraform's state information based on the real infrastructure. | Historically used to synchronize state; modern plan and apply operations normally perform refresh automatically. |
terraform destroy
|
Removes all resources managed by the current Terraform configuration. | Clean up learning environments and temporary infrastructure. |
Terraform state maps resources defined in configuration files to the real resources created in the cloud.
{
"type": "aws_instance",
"name": "web_server",
"attributes": {
"id": "i-0123456789abcdef0",
"instance_type": "t3.micro",
"private_ip": "10.0.1.25",
"tags": {
"Name": "Terraform-EC2"
}
}
}
A tested Terraform design can be reused with different variable values to create similar infrastructure for multiple environments.