Secret management integration (Vault, Secrets Manager) in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a Vault provider in Terraform.

Terraform

provider "vault" {
  address = "[1]"
}

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

A"http://127.0.0.1:8500"

B"https://secretsmanager.aws.com"

C"https://vault.example.com"

D"http://localhost:8200"

Attempts:

3 left

💡 Hint

Common Mistakes

Using AWS Secrets Manager URL instead of Vault URL.

Using incorrect port numbers.

Leaving the address blank.

The Vault provider requires the Vault server address. "http://localhost:8200" is the default Vault server URL.

2fill in blank

medium

Complete the code to read a secret from Vault using Terraform data source.

Terraform

data "vault_generic_secret" "example" {
  path = "[1]"
}

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

A"secret/data/myapp/config"

B"aws/secretsmanager/myapp"

C"kv/myapp/config"

D"secret/myapp/config"

Attempts:

3 left

💡 Hint

Common Mistakes

Using AWS Secrets Manager path format.

Using KV v1 path format without /data/.

Incorrect secret engine path.

The path "secret/data/myapp/config" is the correct Vault KV v2 path format to read secrets.

3fill in blank

hard

Fix the error in the Terraform code to retrieve AWS Secrets Manager secret.

Terraform

data "aws_secretsmanager_secret_version" "example" {
  secret_id = [1]
}

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

A"example-secret-id"

B"aws_secretsmanager_secret.example.id"

Caws_secretsmanager_secret.example.id

Dexample-secret-id

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the secret ID string.

Using resource references incorrectly.

Using variable names without quotes.

The secret_id must be a string literal with the secret's ID or ARN, so it needs quotes around it.

4fill in blank

hard

Fill both blanks to define a Vault secret resource with a dynamic key and value.

Terraform

resource "vault_generic_secret" "example" {
  path = "secret/data/[1]"
  data_json = jsonencode({
    [2] = "mysecretvalue"
  })
}

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

Amyapp

Bconfig

Cpassword

Dusername

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect path segments.

Using keys that don't match secret content.

Confusing path and key names.

The path should be "secret/data/myapp" and the key inside the secret data should be "password" to store the secret value.

5fill in blank

hard

Fill all three blanks to output the secret value from Vault data source in Terraform.

Terraform

output "db_password" {
  value = data.vault_generic_secret.[1].data.[2]["[3]"]
}

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

Aexample

Bdata

Cpassword

Dsecret

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong data source name.

Accessing secret keys incorrectly.

Confusing Vault KV v1 and v2 data structure.

The data source name is "example", the Vault KV v2 secret data is under "data", and the key for the password is "password".

Practice

1. What is the main purpose of integrating Terraform with a secret management tool like Vault or AWS Secrets Manager?

easy

A. To securely store and access sensitive data like passwords and API keys outside the code

B. To speed up Terraform plan and apply operations

C. To automatically generate Terraform configuration files

D. To monitor cloud resource usage and billing

Solution

1. Step 1: Understand secret management purpose

   Secret management tools keep sensitive data safe and separate from code to reduce risk.

2. Step 2: Connect to Terraform integration goal

   Terraform uses these tools to fetch secrets securely during infrastructure deployment without hardcoding them.

3. Final Answer:

   To securely store and access sensitive data like passwords and API keys outside the code -> Option A

4. Quick Check:

   Secret management = Secure external storage [OK]

Hint: Secrets keep sensitive data out of code [OK]

Common Mistakes:

• Thinking secret managers speed up Terraform
• Confusing secret management with billing tools
• Assuming secret managers generate configs

2. Which Terraform block correctly configures AWS Secrets Manager to read a secret named db_password?

easy

A. variable "db_password" { default = "aws_secretsmanager_secret.db_password" }

B. resource "aws_secretsmanager_secret" "example" { name = "db_password" }

C. provider "aws" { secret_name = "db_password" }

D. data "aws_secretsmanager_secret_version" "example" { secret_id = "db_password" }

Solution

1. Step 1: Identify correct Terraform data source for reading secret

   Terraform uses data "aws_secretsmanager_secret_version" to read secret values from AWS Secrets Manager.

2. Step 2: Check syntax correctness

   The block uses secret_id = "db_password" to specify the secret name, which is correct for reading.

3. Final Answer:

   data "aws_secretsmanager_secret_version" "example" { secret_id = "db_password" } -> Option D

4. Quick Check:

   Read secret = data source block [OK]

Hint: Use data block to read secrets, not resource [OK]

Common Mistakes:

• Using resource block to read secrets
• Putting secret name in provider block
• Assigning secret as variable default incorrectly

3. Given this Terraform snippet using Vault provider:

data "vault_generic_secret" "db" {
  path = "secret/data/database"
}

output "db_password" {
  value = data.vault_generic_secret.db.data["password"]
}

What will be the output if the secret at secret/data/database contains {"password": "pass123"}?

medium

A. "data.vault_generic_secret.db.data[\"password\"]"

B. "pass123"

C. Error: secret not found

D. null

Solution

1. Step 1: Understand Vault data source usage

   The vault_generic_secret data source reads secrets at the given path and stores them in data map.

2. Step 2: Access the password key in output

   The output accesses data.vault_generic_secret.db.data["password"], which matches the secret's password value "pass123".

3. Final Answer:

   "pass123" -> Option B

4. Quick Check:

   Output secret value = "pass123" [OK]

Hint: Access secret data map keys directly [OK]

Common Mistakes:

• Expecting error if secret exists
• Outputting the literal string instead of value
• Confusing data structure keys

4. You wrote this Terraform code to read a secret from AWS Secrets Manager:

data "aws_secretsmanager_secret_version" "db" {
  secret_id = aws_secretsmanager_secret.db.name
}

resource "aws_secretsmanager_secret" "db" {
  name = "my_db_password"
}

Terraform plan fails with error: Reference to undeclared resource. What is the problem?

medium

A. The resource block is missing required parameters

B. The secret_id should be a string, not a resource attribute

C. The data source references the resource before it is declared

D. Terraform cannot read secrets from AWS Secrets Manager

Solution

1. Step 1: Analyze resource and data source order

   The data source references aws_secretsmanager_secret.db.name before the resource is declared, causing a dependency error.

2. Step 2: Understand Terraform resource referencing rules

   Terraform requires resources to be declared before referencing them in data sources to resolve dependencies correctly.

3. Final Answer:

   The data source references the resource before it is declared -> Option C

4. Quick Check:

   Reference order matters in Terraform [OK]

Hint: Declare resources before referencing them [OK]

Common Mistakes:

• Using resource attributes as string literals
• Ignoring declaration order
• Assuming Terraform can't read AWS secrets

5. You want to securely pass a database password stored in Vault to an AWS RDS instance using Terraform. Which approach follows best practices?

hard

A. Use vault_generic_secret data source to fetch password, then pass it as password argument in aws_db_instance resource without storing it in Terraform state

B. Hardcode the password in Terraform variables and update Vault manually

C. Store the password in a local file and read it in Terraform

D. Create the RDS instance first, then manually update password in Vault

Solution

1. Step 1: Identify secure secret retrieval method

   Using vault_generic_secret data source fetches the password securely at runtime without hardcoding.

2. Step 2: Pass secret directly to resource without storing in state

   Passing the secret as an argument avoids exposing it in Terraform files or state, following best practices.

3. Final Answer:

   Use vault_generic_secret data source to fetch password, then pass it as password argument in aws_db_instance resource without storing it in Terraform state -> Option A

4. Quick Check:

   Fetch secrets dynamically and avoid hardcoding [OK]

Hint: Fetch secrets dynamically, never hardcode passwords [OK]

Common Mistakes:

• Hardcoding secrets in variables
• Storing secrets in local files
• Manual secret updates outside Terraform