State locking with DynamoDB in Terraform - Mini Project: Build & Apply

State locking with DynamoDB

📖 Scenario: You are setting up Terraform to manage your cloud infrastructure safely. To avoid multiple people changing the infrastructure at the same time, you want to use a locking mechanism. DynamoDB can help by locking the Terraform state file during changes.

🎯 Goal: Create a DynamoDB table for Terraform state locking and configure Terraform backend to use it.

📋 What You'll Learn

Create a DynamoDB table named exactly terraform-lock-table

Set the primary key attribute to LockID of type string

Enable server-side encryption for the table

Configure Terraform backend to use the DynamoDB table terraform-lock-table for state locking

Use an S3 bucket named exactly terraform-state-bucket for storing the Terraform state

💡 Why This Matters

🌍 Real World

Terraform state locking prevents multiple users from applying changes simultaneously, avoiding conflicts and corrupted state. DynamoDB is a common choice for locking because it is fast and reliable.

💼 Career

Cloud engineers and DevOps professionals use Terraform with state locking to manage infrastructure safely and collaborate effectively in teams.

1

Create DynamoDB table resource

Create a Terraform resource called aws_dynamodb_table named terraform_lock_table with the table name terraform-lock-table. Set the attribute LockID as a string type hash key.

Terraform

# Your code here to create the DynamoDB table resource

Hint

Use resource "aws_dynamodb_table" "terraform_lock_table" {} with name, hash_key, and attribute blocks.

2

Enable server-side encryption

Add server-side encryption to the aws_dynamodb_table.terraform_lock_table resource by setting server_side_encryption block with enabled = true.

Terraform

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

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

  # Add server-side encryption block here
  # Your code here
}

Hint

Add server_side_encryption { enabled = true } inside the DynamoDB resource.

3

Configure Terraform backend with S3 and DynamoDB

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

Terraform

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

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

  server_side_encryption {
    enabled = true
  }
}

terraform {
  backend "s3" {
    # Your code here
  }
}

Hint

Use terraform { backend "s3" { ... } } with the exact bucket, key, region, and dynamodb_table values.

4

Add AWS provider configuration

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

Terraform

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

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

  server_side_encryption {
    enabled = true
  }
}

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

# Add AWS provider configuration below
# Your code here

Hint

Add provider "aws" { region = "us-east-1" } at the top of your Terraform file.

Practice

1. What is the main purpose of using a DynamoDB table in Terraform state management?

easy

A. To lock the Terraform state and prevent concurrent changes

B. To store Terraform configuration files

C. To host Terraform modules

D. To run Terraform commands remotely

Solution

1. Step 1: Understand Terraform state locking

   Terraform uses state locking to avoid multiple users changing infrastructure at the same time, which can cause conflicts.

2. Step 2: Role of DynamoDB in locking

   DynamoDB acts as a lock store to keep the Terraform state safe by preventing concurrent modifications.

3. Final Answer:

   To lock the Terraform state and prevent concurrent changes -> Option A

4. Quick Check:

   State locking = prevent concurrent changes [OK]

Hint: DynamoDB locks state to avoid conflicts [OK]

Common Mistakes:

• Thinking DynamoDB stores config files
• Confusing locking with module hosting
• Assuming DynamoDB runs Terraform commands

2. Which Terraform backend configuration snippet correctly enables state locking with DynamoDB?

easy

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

B. backend "local" { path = "./terraform.tfstate" dynamodb_table = "terraform-lock" }

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

D. backend "gcs" { bucket = "mybucket" dynamodb_table = "terraform-lock" }

Solution

1. Step 1: Identify backend type supporting DynamoDB locking

   Only the S3 backend supports DynamoDB for state locking in Terraform.

2. Step 2: Check for required parameters

   The S3 backend requires bucket, key, region, and dynamodb_table to enable locking.

3. Final Answer:

   backend "s3" with bucket, key, region, and dynamodb_table -> Option C

4. Quick Check:

   S3 backend + dynamodb_table = locking enabled [OK]

Hint: Use S3 backend with dynamodb_table for locking [OK]

Common Mistakes:

• Adding dynamodb_table to unsupported backends
• Missing key or region in S3 backend
• Using local backend with DynamoDB

3. Given this backend configuration, what happens if two users run terraform apply at the same time?

backend "s3" {
  bucket         = "mybucket"
  key            = "prod/terraform.tfstate"
  region         = "us-west-2"
  dynamodb_table = "tf-locks"
}

medium

A. Both users can apply changes simultaneously without issues

B. Terraform will lock the state in DynamoDB, allowing only one user to apply at a time

C. Terraform will throw an error because DynamoDB is not supported

D. The state file will be overwritten causing conflicts

Solution

1. Step 1: Understand DynamoDB locking behavior

   DynamoDB table is used to lock the state file so only one user can modify it at a time.

2. Step 2: Effect on concurrent applies

   If two users run apply simultaneously, one will get the lock and the other will wait or fail until the lock is released.

3. Final Answer:

   Terraform locks state in DynamoDB, allowing one user at a time -> Option B

4. Quick Check:

   DynamoDB lock = single user apply [OK]

Hint: DynamoDB locks state to serialize applies [OK]

Common Mistakes:

• Assuming simultaneous applies succeed
• Thinking DynamoDB is unsupported
• Believing state file overwrites happen

4. You configured your Terraform backend with DynamoDB locking but receive this error: Error locking state: ConditionalCheckFailedException. What is the most likely cause?

medium

A. Terraform version is too old to support DynamoDB locking

B. The S3 bucket name is misspelled

C. The backend block is missing the region parameter

D. The DynamoDB table does not exist or has incorrect permissions

Solution

1. Step 1: Understand the error meaning

   ConditionalCheckFailedException usually means DynamoDB cannot perform the lock operation, often due to missing table or permission issues.

2. Step 2: Check backend configuration and AWS resources

   If the DynamoDB table does not exist or Terraform lacks permission to access it, locking fails with this error.

3. Final Answer:

   DynamoDB table missing or permission issues -> Option D

4. Quick Check:

   ConditionalCheckFailedException = DynamoDB table or permissions [OK]

Hint: Check DynamoDB table existence and permissions first [OK]

Common Mistakes:

• Blaming S3 bucket name for DynamoDB error
• Ignoring Terraform version compatibility
• Overlooking missing region parameter

5. You want to ensure your Terraform state locking is highly available and prevents accidental unlocks. Which combination of DynamoDB table settings is best practice?

hard

A. Enable point-in-time recovery and use a strong primary key with consistent read

B. Use a simple primary key and disable point-in-time recovery to reduce costs

C. Use eventual consistency and no encryption for faster locking

D. Create multiple DynamoDB tables for locking in different regions

Solution

1. Step 1: Identify high availability features

   Point-in-time recovery protects against accidental deletes or corruption of the lock table.

2. Step 2: Understand locking consistency needs

   Using a strong primary key and consistent reads ensures reliable lock state and prevents race conditions.

3. Step 3: Evaluate other options

   Disabling recovery or using eventual consistency risks losing lock data or causing conflicts; multiple tables add complexity without benefit.

4. Final Answer:

   Enable point-in-time recovery and use strong primary key with consistent read -> Option A

5. Quick Check:

   Recovery + strong key + consistency = best locking [OK]

Hint: Enable recovery and strong keys for safe locking [OK]

Common Mistakes:

• Disabling recovery to save money
• Using eventual consistency causing conflicts
• Creating multiple tables unnecessarily