State disaster recovery in Terraform - Mini Project: Build & Apply

State Disaster Recovery with Terraform

📖 Scenario: You are managing infrastructure using Terraform. To protect your infrastructure state from accidental loss or corruption, you want to set up a remote backend with state locking and versioning.This helps you recover your infrastructure state if something goes wrong.

🎯 Goal: Set up a Terraform backend configuration that stores state remotely in an AWS S3 bucket with state locking using DynamoDB.This ensures your Terraform state is safe and recoverable in case of disasters.

📋 What You'll Learn

Create a Terraform backend configuration using AWS S3

Enable state locking with DynamoDB table

Specify the S3 bucket name as my-terraform-state-bucket

Specify the DynamoDB table name as terraform-lock-table

Set the AWS region to us-east-1

💡 Why This Matters

🌍 Real World

Terraform state files hold the current infrastructure status. Losing or corrupting them can cause deployment failures or resource duplication. Using remote state with locking prevents concurrent changes and protects state files.

💼 Career

Cloud engineers and DevOps professionals must ensure infrastructure state is safely stored and recoverable. This knowledge is essential for managing infrastructure as code in real environments.

1

Create the S3 bucket resource

Create a Terraform resource called aws_s3_bucket named terraform_state_bucket with the bucket name set to "my-terraform-state-bucket".

Terraform

# Your code here to create the S3 bucket resource

Hint

Use resource "aws_s3_bucket" "terraform_state_bucket" {} and set the bucket attribute.

2

Create the DynamoDB table resource for state locking

Create a Terraform resource called aws_dynamodb_table named terraform_lock_table with the table name set to "terraform-lock-table", billing mode set to "PAY_PER_REQUEST", and a hash key named LockID of type "S".

Terraform

resource "aws_s3_bucket" "terraform_state_bucket" {
  bucket = "my-terraform-state-bucket"
}

# Your code here to create the DynamoDB table resource

Hint

Use resource "aws_dynamodb_table" "terraform_lock_table" {} and define the name, billing_mode, hash_key, and attribute block.

3

Configure the Terraform backend

Add a terraform block with a backend "s3" configuration that sets bucket to "my-terraform-state-bucket", key to "terraform.tfstate", region to "us-east-1", and dynamodb_table to "terraform-lock-table".

Terraform

resource "aws_s3_bucket" "terraform_state_bucket" {
  bucket = "my-terraform-state-bucket"
}

resource "aws_dynamodb_table" "terraform_lock_table" {
  name         = "terraform-lock-table"
  billing_mode = "PAY_PER_REQUEST"
  hash_key     = "LockID"

  attribute {
    name = "LockID"
    type = "S"
  }
}

# Your code here to add the terraform backend configuration

Hint

Use a terraform block with a backend "s3" block inside. Set the required attributes exactly as specified.

4

Add provider configuration for AWS

Add a Terraform provider "aws" block with the region set to "us-east-1".

Terraform

terraform {
  backend "s3" {
    bucket         = "my-terraform-state-bucket"
    key            = "terraform.tfstate"
    region         = "us-east-1"
    dynamodb_table = "terraform-lock-table"
  }
}

resource "aws_s3_bucket" "terraform_state_bucket" {
  bucket = "my-terraform-state-bucket"
}

resource "aws_dynamodb_table" "terraform_lock_table" {
  name         = "terraform-lock-table"
  billing_mode = "PAY_PER_REQUEST"
  hash_key     = "LockID"

  attribute {
    name = "LockID"
    type = "S"
  }
}

# Your code here to add the AWS provider configuration

Hint

Add a provider "aws" block and set the region attribute.

Practice

1. What is the main purpose of using remote state storage in Terraform for disaster recovery?

easy

A. To create backups of your source code

B. To speed up Terraform plan and apply commands

C. To safely store the Terraform state file and enable recovery if lost or corrupted

D. To automatically update Terraform providers

Solution

1. Step 1: Understand Terraform state role

   The Terraform state file tracks your infrastructure resources and their current status.

2. Step 2: Importance of remote storage for disaster recovery

   Storing state remotely protects it from local loss or corruption, enabling recovery.

3. Final Answer:

   To safely store the Terraform state file and enable recovery if lost or corrupted -> Option C

4. Quick Check:

   Remote state protects infrastructure info = D [OK]

Hint: Remote state stores your infra info safely for recovery [OK]

Common Mistakes:

• Confusing state storage with code backup
• Thinking remote state speeds up commands
• Assuming remote state updates providers

2. Which of the following is the correct syntax to configure an S3 backend for Terraform state with versioning enabled?

easy

A. backend "s3" { bucket = "mybucket" key = "state.tfstate" region = "us-east-1" versioning = true }

B. backend "s3" { bucket = "mybucket" key = "state.tfstate" region = "us-east-1" }

C. backend "s3" { bucket = "mybucket" key = "state.tfstate" region = "us-east-1" encrypt = true }

D. backend "s3" { bucket = "mybucket" key = "state.tfstate" region = "us-east-1" versioning = "enabled" }

Solution

1. Step 1: Review S3 backend configuration syntax

   The S3 backend block supports bucket, key, region, and encrypt but not versioning directly.

2. Step 2: Understand versioning setup

   Versioning is enabled on the S3 bucket itself, not via Terraform backend config.

3. Final Answer:

   backend "s3" { bucket = "mybucket" key = "state.tfstate" region = "us-east-1" } -> Option B

4. Quick Check:

   Versioning is bucket setting, not backend config = C [OK]

Hint: Versioning is set on S3 bucket, not in Terraform backend block [OK]

Common Mistakes:

• Trying to set versioning inside backend block
• Confusing encrypt with versioning
• Using wrong data types for versioning

3. Given this Terraform backend configuration snippet, what will happen if the local state file is deleted but the remote backend is intact?

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

medium

A. Terraform will prompt to reinitialize the backend and then sync state

B. Terraform will fail because the local state file is missing

C. Terraform will create a new empty state file and overwrite remote state

D. Terraform will automatically download the remote state and continue

Solution

1. Step 1: Understand backend initialization behavior

   Terraform requires backend initialization to connect local config with remote state.

2. Step 2: Effect of missing local state file

   If local state is missing, Terraform prompts to reinitialize backend to sync remote state locally.

3. Final Answer:

   Terraform will prompt to reinitialize the backend and then sync state -> Option A

4. Quick Check:

   Missing local state triggers reinit and sync = B [OK]

Hint: Missing local state triggers backend reinit and sync prompt [OK]

Common Mistakes:

• Assuming Terraform fails immediately
• Thinking Terraform overwrites remote state blindly
• Believing Terraform auto-downloads without reinit

4. You configured an S3 backend for Terraform state but forgot to enable bucket versioning. What problem might you face during disaster recovery?

medium

A. Terraform will create duplicate state files

B. Terraform will refuse to initialize the backend

C. State file will be encrypted automatically

D. You cannot recover previous versions of the state file if it gets corrupted

Solution

1. Step 1: Role of versioning in disaster recovery

   Versioning allows keeping multiple versions of the state file to recover from mistakes or corruption.

2. Step 2: Consequence of missing versioning

   Without versioning, if the state file is overwritten or corrupted, previous versions are lost permanently.

3. Final Answer:

   You cannot recover previous versions of the state file if it gets corrupted -> Option D

4. Quick Check:

   No versioning means no state history recovery = A [OK]

Hint: No versioning means lost state history on corruption [OK]

Common Mistakes:

• Thinking Terraform blocks backend init without versioning
• Assuming encryption is automatic
• Believing duplicate state files are created

5. You want to ensure your Terraform state is protected against accidental deletion and corruption. Which combination of practices provides the best disaster recovery setup?

hard

A. Use remote backend with S3 bucket having versioning and server-side encryption enabled

B. Use local state files with manual backups on your computer

C. Use remote backend with S3 bucket without versioning but with encryption enabled

D. Use remote backend with local file copy enabled

Solution

1. Step 1: Identify best remote backend features for disaster recovery

   Remote backend with S3 bucket versioning keeps multiple state versions; encryption protects data confidentiality.

2. Step 2: Compare options

   Local files lack safety; no versioning risks losing history; local copy doesn't protect against corruption.

3. Final Answer:

   Use remote backend with S3 bucket having versioning and server-side encryption enabled -> Option A

4. Quick Check:

   Versioning + encryption on remote backend = best recovery [OK]

Hint: Combine versioning and encryption on remote backend for best safety [OK]

Common Mistakes:

• Relying on local files only
• Skipping versioning on S3 bucket
• Confusing local copy with remote backup