Learn how Terraform state tracks infrastructure resources, stores resource information, supports remote backends, and helps manage Infrastructure as Code.
Terraform State Workflow
Read Current State
Compare Configuration
Create Execution Plan
Apply Infrastructure Changes
Update Terraform State
Introduction
Terraform state is one of the core components of Terraform. It allows Terraform to maintain information about the infrastructure resources that it manages.
When you create or modify infrastructure, Terraform uses state information to understand what resources already exist and how they relate to your configuration.
Understanding Terraform state is important when working with larger infrastructure environments, teams, remote backends, and reusable Infrastructure as Code.
Core Concepts
These concepts explain how Terraform tracks infrastructure and manages state across different environments and workflows.
Terraform state is a record of the infrastructure resources that Terraform manages and the information Terraform needs to understand their current state.
Key Topics
Terraform commonly stores infrastructure state in a state file, allowing Terraform to track resource information between operations.
Key Topics
Remote state stores Terraform state in a shared backend instead of keeping the state only on a local machine.
Key Topics
State locking helps prevent multiple Terraform operations from modifying the same state at the same time.
Key Topics
Local State
By default, Terraform can maintain state information locally in the working directory.
The state file contains information that Terraform uses to map configuration resources to the infrastructure resources it manages.
Example Local Project
terraform-project/ │ ├── main.tf ├── variables.tf ├── outputs.tf │ └── terraform.tfstate
Simplified State Example
{
"version": 4,
"terraform_version": "1.x",
"resources": [
{
"type": "aws_instance",
"name": "web_server"
}
]
}State Information
Terraform state contains information about the resources managed by the Terraform configuration.
This information can include resource identifiers, attributes, relationships, and other metadata required for Terraform to understand the managed infrastructure.
State Workflow
Terraform uses state information throughout the infrastructure management workflow.
Terraform Configuration
│
▼
terraform plan / apply
│
▼
Terraform State
│
▼
Cloud InfrastructureTerraform reads existing state information to understand the infrastructure it currently manages.
Terraform compares configuration and current infrastructure information to determine the required changes.
Terraform creates an execution plan describing the infrastructure actions it intends to perform.
Terraform creates, updates, or removes resources according to the approved configuration.
After infrastructure changes are completed, Terraform updates the state information it manages.
State Commands
Terraform provides state commands that can help inspect resources tracked by the current state and perform specific state management operations.
State operations should be performed carefully because they can change how Terraform maps configuration resources to existing infrastructure.
Common State Commands
# List resources tracked by Terraform terraform state list # Show information about a resource terraform state show aws_instance.web_server # Move a resource in the state terraform state mv old_resource new_resource # Remove a resource from state terraform state rm aws_instance.web_server
Backend Configuration Example
terraform {
backend "s3" {
bucket = "terraform-state-bucket"
key = "production/terraform.tfstate"
region = "us-east-1"
}
}Remote State
Remote state stores Terraform state using a configured backend instead of relying only on a local state file.
Remote state is useful for shared infrastructure workflows where multiple users or automation systems need access to the same infrastructure state.
State Locking
When multiple users or automation systems manage the same infrastructure, concurrent operations can create conflicts.
State locking can help protect the infrastructure workflow by preventing conflicting Terraform operations from modifying the same state at the same time.
Teams can work with a centralized infrastructure state instead of maintaining separate local copies.
Locking can help prevent multiple Terraform operations from changing the same state simultaneously.
State management practices help reduce the risk of conflicting infrastructure operations.
Benefits
Terraform state allows Terraform to understand which resources it manages and how those resources are configured.
Terraform compares configuration, state information, and infrastructure data to determine what changes may be required.
State information helps Terraform understand relationships between different infrastructure resources.
Remote state makes it easier for teams to work with shared infrastructure configurations.
Modules and State
Terraform modules can expose infrastructure information through output values.
The root module can then reference those outputs when working with infrastructure created by reusable child modules.
Module Output Example
# Root module output
output "server_ip" {
value = module.web_server.public_ip
}Learning Roadmap
Follow these steps to understand how Terraform uses and manages infrastructure state.
Learn why Terraform needs state to track the infrastructure resources it manages.
Create infrastructure and understand how Terraform records resource information in its state.
Learn how to inspect and manage resources tracked by Terraform state.
Learn why shared infrastructure environments often use a remote backend for state storage.
Understand how locking can help prevent conflicting Terraform operations.
Protect state files, avoid unnecessary manual changes, and use an appropriate backend for your workflow.
Best Practices
Treat Terraform state carefully because it can contain important infrastructure information.
Use an appropriate shared backend when multiple users or automation systems manage the same infrastructure.
Avoid directly editing state files unless you fully understand the consequences and have a safe recovery process.
Commands that modify state can affect how Terraform tracks existing infrastructure resources.
Use a backend and workflow that can help prevent conflicting concurrent infrastructure operations.
Review Terraform plans before applying changes to understand how configuration updates affect managed infrastructure.
Continue Learning
Learn the fundamentals of Terraform and Infrastructure as Code.
📦Learn how to create flexible Terraform configurations with variables and output values.
🧩Learn how to organize reusable infrastructure configurations using Terraform modules.
Next Step
Practice inspecting Terraform state, understanding resource tracking, using state commands, and learning how remote state fits into larger infrastructure workflows.