Backend initialization and migration in Terraform - Step-by-Step Execution

Process Flow - Backend initialization and migration

Start: No backend configured

↓

Configure backend in terraform block

↓

Run 'terraform init'

↓

Terraform checks backend config

↓

If backend changed?

Yes→Prompt migration

↓

Run 'terraform init -migrate-state'

↓

State migrated to new backend

↓

Backend initialized

↓

Terraform ready for plan/apply

Terraform initializes backend configuration, detects changes, and migrates state if needed to prepare for infrastructure management.

Execution Sample

Terraform

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "prod/terraform.tfstate"
    region = "us-east-1"
  }
}

# Run: terraform init

This code configures an S3 backend for Terraform state and initializes it.

Process Table

Step	Action	Backend Config Detected	Migration Needed?	Command Run	Result
1	Start with no backend configured	None	N/A	N/A	No backend initialized
2	Add backend block with S3 config	S3 backend with bucket=my-terraform-state	N/A	N/A	Backend config ready
3	Run 'terraform init'	S3 backend detected	No	terraform init	Backend initialized, state ready
4	Change backend bucket to 'my-new-bucket'	S3 backend with bucket=my-new-bucket	Yes	terraform init	Prompt migration needed
5	Run 'terraform init -migrate-state'	S3 backend with bucket=my-new-bucket	No	terraform init -migrate-state	State migrated to new backend
6	Backend initialized with new config	S3 backend with bucket=my-new-bucket	No	N/A	Terraform ready for use

💡 Backend initialized and state migrated if needed, ready for terraform plan/apply

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
backend_config	None	S3 bucket=my-terraform-state	S3 bucket=my-terraform-state	S3 bucket=my-new-bucket	S3 bucket=my-new-bucket	S3 bucket=my-new-bucket
migration_needed	N/A	N/A	No	Yes	No	No
state_location	Local	Local	S3:my-terraform-state	S3:my-terraform-state	S3:my-new-bucket	S3:my-new-bucket

Key Moments - 3 Insights

Why does Terraform ask for migration when the backend bucket changes?

Because the backend configuration changed (see step 4 in execution_table), Terraform needs to move the state file to the new backend location to keep track of resources.

What happens if you run 'terraform init' without migration after changing backend?

Terraform will detect the backend change and prompt for migration (step 4). Without migration, the state won't be moved, causing errors.

How does Terraform know where the state file is stored?

Terraform reads the backend configuration (backend_config variable) to determine the state location (state_location variable). This updates after migration.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Terraform detect that migration is needed?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Check the 'Migration Needed?' column in execution_table rows

According to variable_tracker, what is the state_location after step 5?

A S3:my-new-bucket

B Local

C S3:my-terraform-state

D None

💡 Hint

Look at the 'state_location' row under 'After Step 5' column

If you do not run 'terraform init -migrate-state' after changing backend, what will happen?

A Terraform will ignore backend change

B Terraform will automatically migrate state

C Terraform will prompt migration but state remains in old backend

D Terraform will delete the state file

💡 Hint

Refer to step 4 and the explanation in key_moments about migration prompt

Concept Snapshot

Terraform backend initialization:
- Configure backend in terraform block
- Run 'terraform init' to initialize
- If backend changes, Terraform prompts migration
- Run 'terraform init -migrate-state' to move state
- Backend ready for terraform plan/apply

Full Transcript

Terraform backend initialization starts with no backend configured. You add a backend block specifying storage details like an S3 bucket. Running 'terraform init' reads this config and sets up the backend. If you later change backend settings, Terraform detects this and asks if you want to migrate the state file. Running 'terraform init -migrate-state' moves the state to the new backend. After this, Terraform is ready to manage infrastructure with the updated backend.