State encryption at rest in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable encryption for the Terraform state backend.

Terraform

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "state.tfstate"
    region = "us-west-2"
    [1] = true
  }
}

Drag options to blanks, or click blank then click option'

Aencrypt

Bencryption

Cenable_encryption

Dstate_encryption

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'encryption' instead of 'encrypt'

Using 'enable_encryption' which is not a valid attribute

Using 'state_encryption' which does not exist

The correct attribute to enable encryption at rest in the S3 backend is encrypt set to true.

2fill in blank

medium

Complete the code to specify the KMS key for encrypting the Terraform state.

Terraform

terraform {
  backend "s3" {
    bucket         = "my-terraform-state"
    key            = "state.tfstate"
    region         = "us-west-2"
    encrypt        = true
    [1] = "arn:aws:kms:us-west-2:123456789012:key/abcd-1234-efgh-5678"
  }
}

Drag options to blanks, or click blank then click option'

Akms_arn

Bkms_key

Ckms_key_id

Dencryption_key

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'kms_key' which is not recognized

Using 'encryption_key' which is invalid

Using 'kms_arn' which is not the correct attribute

The correct attribute to specify the KMS key ARN in the S3 backend is kms_key_id.

3fill in blank

hard

Fix the error in the backend configuration to properly enable encryption at rest.

Terraform

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "state.tfstate"
    region = "us-west-2"
    encrypt = [1]
  }
}

Drag options to blanks, or click blank then click option'

A1

B"true"

CTrue

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around true, making it a string

Using capitalized True which is invalid in Terraform

Using 1 instead of true for boolean

The encrypt attribute expects a boolean value true without quotes.

4fill in blank

hard

Fill both blanks to configure the S3 backend with encryption and a KMS key.

Terraform

terraform {
  backend "s3" {
    bucket         = "my-terraform-state"
    key            = "state.tfstate"
    region         = "us-west-2"
    [1] = true
    [2] = "arn:aws:kms:us-west-2:123456789012:key/abcd-1234-efgh-5678"
  }
}

Drag options to blanks, or click blank then click option'

Aencrypt

Bkms_key_id

Cencryption_key

Denable_encryption

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'enable_encryption' instead of 'encrypt'

Using 'encryption_key' instead of 'kms_key_id'

Mixing up the order of attributes

Use encrypt to enable encryption and kms_key_id to specify the KMS key ARN.

5fill in blank

hard

Fill all three blanks to configure the S3 backend with encryption, KMS key, and versioning enabled.

Terraform

terraform {
  backend "s3" {
    bucket          = "my-terraform-state"
    key             = "state.tfstate"
    region          = "us-west-2"
    [1]  = true
    [2]  = "arn:aws:kms:us-west-2:123456789012:key/abcd-1234-efgh-5678"
    [3] = true
  }
}

Drag options to blanks, or click blank then click option'

Aencrypt

Bkms_key_id

Cversioning

Denable_versioning

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'enable_versioning' instead of 'versioning'

Forgetting to enable versioning

Incorrect attribute names for encryption

Use encrypt to enable encryption, kms_key_id for the KMS key, and versioning to enable versioning of the state files.

Practice

1. What is the main purpose of enabling state encryption at rest in Terraform?

easy

A. To reduce the size of the Terraform state file

B. To speed up Terraform plan and apply operations

C. To automatically backup the state file to multiple regions

D. To protect the Terraform state file from unauthorized access

Solution

1. Step 1: Understand what state encryption means

   Encryption at rest means protecting stored data from unauthorized reading.

2. Step 2: Apply this to Terraform state files

   Terraform state files contain sensitive infrastructure data, so encrypting them protects this data.

3. Final Answer:

   To protect the Terraform state file from unauthorized access -> Option D

4. Quick Check:

   State encryption = protect data [OK]

Hint: Encryption protects stored state data from unauthorized access [OK]

Common Mistakes:

• Confusing encryption with performance improvement
• Thinking encryption reduces file size
• Assuming encryption automatically backs up data

2. Which of the following is the correct way to enable encryption for an S3 backend in Terraform?

easy

A. encryption_enabled = yes

B. encrypt = true

C. enable_encryption = on

D. kms_encryption = true

Solution

1. Step 1: Recall the S3 backend encryption syntax

   The correct attribute to enable encryption is encrypt = true.

2. Step 2: Verify other options are invalid

   Other options are not valid Terraform backend configuration keys.

3. Final Answer:

   encrypt = true -> Option B

4. Quick Check:

   Correct syntax = encrypt = true [OK]

Hint: Use exact key 'encrypt = true' to enable S3 backend encryption [OK]

Common Mistakes:

• Using incorrect attribute names
• Using 'yes' or 'on' instead of true
• Confusing KMS key setting with encryption toggle

3. Given this Terraform backend configuration snippet for S3:

backend "s3" {
  bucket = "my-terraform-state"
  key    = "state.tfstate"
  region = "us-east-1"
  encrypt = true
  kms_key_id = "arn:aws:kms:us-east-1:123456789012:key/abcd-1234"
}

What is the effect of specifying kms_key_id here?

medium

A. It uses the specified KMS key to encrypt the state file instead of the default AWS key

B. It disables encryption and uses the KMS key only for access control

C. It backs up the state file to the KMS key's region

D. It automatically rotates the state file encryption key daily

Solution

1. Step 1: Understand the role of kms_key_id in S3 backend

   Specifying kms_key_id tells Terraform to use a custom AWS KMS key for encryption.

2. Step 2: Compare with default behavior

   If kms_key_id is not set, AWS uses a default managed key for encryption.

3. Final Answer:

   It uses the specified KMS key to encrypt the state file instead of the default AWS key -> Option A

4. Quick Check:

   kms_key_id = custom encryption key [OK]

Hint: kms_key_id sets custom encryption key, not disables encryption [OK]

Common Mistakes:

• Thinking kms_key_id disables encryption
• Confusing kms_key_id with backup location
• Assuming automatic key rotation

4. You wrote this backend configuration for S3:

backend "s3" {
  bucket = "my-bucket"
  key = "terraform.tfstate"
  region = "us-west-2"
  encrypt = "true"
}

Terraform throws an error when initializing. What is the problem?

medium

A. The key attribute is missing

B. The bucket name is invalid

C. The value for encrypt should be a boolean, not a string

D. The region value is incorrect

Solution

1. Step 1: Check the encrypt attribute type

   Terraform expects encrypt to be a boolean (true/false), not a string.

2. Step 2: Confirm other attributes are correct

   Bucket name, key, and region are valid and present.

3. Final Answer:

   The value for encrypt should be a boolean, not a string -> Option C

4. Quick Check:

   encrypt must be boolean true/false [OK]

Hint: Use true without quotes for boolean values in Terraform [OK]

Common Mistakes:

• Putting boolean values in quotes
• Assuming bucket or region is wrong without checking
• Missing required attributes

5. You want to ensure your Terraform state stored in an S3 bucket is encrypted using a specific KMS key. Which configuration snippet correctly achieves this?

hard

A. backend "s3" {
bucket = "my-secure-bucket"
key = "prod/terraform.tfstate"
region = "us-east-1"
encrypt = true
kms_key_id = "arn:aws:kms:us-east-1:123456789012:key/secure-key"
}

B. backend "s3" {
bucket = "my-secure-bucket"
key = "prod/terraform.tfstate"
region = "us-east-1"
encrypt = false
kms_key_id = "arn:aws:kms:us-east-1:123456789012:key/secure-key"
force_destroy = true
}

C. backend "s3" {
bucket = "my-secure-bucket"
key = "prod/terraform.tfstate"
region = "us-east-1"
encrypt = true
kms_key_id = ""
force_destroy = true
}

D. backend "s3" {
bucket = "my-secure-bucket"
key = "prod/terraform.tfstate"
region = "us-east-1"
encrypt = true
kms_key_id = "arn:aws:kms:us-east-1:123456789012:key/secure-key"
force_destroy = true
}

Solution

1. Step 1: Enable encryption with a specific KMS key

   Set encrypt = true and provide the kms_key_id ARN for custom encryption.

2. Step 2: Verify other options are incorrect

   A has encrypt = false (disables encryption); C has empty kms_key_id; A, C, D include invalid force_destroy parameter (causes terraform init error).

3. Final Answer:

   Configuration with encrypt=true and kms_key_id set -> Option A

4. Quick Check:

   Valid S3 backend with custom KMS encryption [OK]

Hint: Use encrypt=true and kms_key_id to encrypt state with custom KMS key [OK]

Common Mistakes:

• Disabling encryption by setting encrypt=false
• Using empty kms_key_id
• Adding invalid parameters like force_destroy to backend config