Terraform Remote Backend with S3 and Azure Storage: Complete Guide

Terraform Remote Backend with S3 and Azure Storage#

Learn why remote backends are important, how Terraform stores state remotely, and how teams use S3 or Azure Storage for safer collaboration.

What is a Terraform backend?#

A backend controls where Terraform stores state. Local backend stores state on your machine. Remote backends store state in a shared location.

Why use remote backend?#

• Team collaboration.
• State locking.
• Better backup and access control.
• CI/CD support.
• Avoid local laptop dependency.

S3 backend example#

terraform { backend "s3" { bucket = "my-terraform-state-bucket" key = "dev/network/terraform.tfstate" region = "ap-south-1" dynamodb_table = "terraform-locks" encrypt = true } }

Azure Storage backend example#

terraform { backend "azurerm" { resource_group_name = "rg-tfstate" storage_account_name = "mystatestorage" container_name = "tfstate" key = "dev/network/terraform.tfstate" } }

Backend migration#

terraform init -migrate-state

Best practices#

• Use separate state keys per environment.
• Enable encryption.
• Restrict backend access.
• Use locking where supported.
• Back up state.
• Do not store backend credentials in Git.

Related guides#

• Terraform Learning Path
• Terraform State File Explained