Sensitive output values in Terraform - Commands & Configuration

Introduction

Sometimes you want to keep certain output information private, like passwords or keys. Terraform lets you mark outputs as sensitive so they don't show up in normal command outputs. This helps keep secrets safe while still sharing important info.

When you output a database password from Terraform but don't want it to appear in the terminal.

When you share Terraform state with your team but want to hide API keys in outputs.

When you automate deployments and need to pass secret values without exposing them in logs.

When you want to prevent accidental copying of sensitive data from Terraform output.

When you use Terraform outputs in scripts but want to keep secrets secure.

Config File - main.tf

main.tf

terraform {
  required_version = ">= 1.0"
}

output "db_password" {
  value     = "supersecret123"
  sensitive = true
}

output "app_url" {
  value = "https://myapp.example.com"
}

This Terraform file defines two outputs.

db_password is marked as sensitive = true so Terraform hides it in normal output.

app_url is a normal output and will show in the terminal.

Commands

This command sets up Terraform in the current folder by downloading necessary plugins and preparing the environment.

Terminal

terraform init

Expected Output

Initializing the backend...



Initializing provider plugins...

- Finding latest version of hashicorp/random...

- Installing hashicorp/random v3.4.3...

- Installed hashicorp/random v3.4.3 (signed by HashiCorp)



Terraform has been successfully initialized!

This command applies the Terraform configuration to create or update resources and outputs the results. The -auto-approve flag skips manual confirmation.

Terminal

terraform apply -auto-approve

Expected Output

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.



Outputs:



app_url = "https://myapp.example.com"



Note: sensitive output "db_password" is hidden.

→

-auto-approve - Automatically approve the apply without asking for confirmation

This command shows the outputs from the last apply. Sensitive outputs are hidden to protect secrets.

Terminal

terraform output

Expected Output

app_url = "https://myapp.example.com"



Note: sensitive output "db_password" is hidden.

This command shows the value of the sensitive output explicitly. Use this carefully because it reveals the secret.

Terminal

terraform output db_password

Expected Output

supersecret123

Key Concept

If you remember nothing else from this pattern, remember: marking outputs as sensitive hides them from normal Terraform output to protect secrets.

Common Mistakes

Not setting sensitive = true on secret outputs

Secrets like passwords will show in terminal output and logs, risking exposure.

Always add sensitive = true to outputs that contain secret or private information.

Trying to see sensitive output with just terraform output

Terraform hides sensitive outputs by default, so you won't see the secret value.

Use terraform output <output_name> to explicitly view a sensitive output when needed.

Summary

Use sensitive = true in output blocks to keep secrets hidden from normal Terraform output.

Run terraform apply to apply changes and see non-sensitive outputs.

Use terraform output <name> to view sensitive outputs carefully when needed.

Practice

1. What is the main purpose of marking an output as sensitive = true in Terraform?

easy

A. To hide the output value from the standard Terraform output display

B. To make the output value publicly accessible

C. To increase the output value size limit

D. To automatically encrypt the output value in the state file

Solution

1. Step 1: Understand the role of sensitive outputs

   Marking an output as sensitive hides it from the normal Terraform output display to protect secrets.

2. Step 2: Clarify what sensitive does not do

   Sensitive does not make outputs public, increase size, or encrypt state automatically.

3. Final Answer:

   To hide the output value from the standard Terraform output display -> Option A

4. Quick Check:

   sensitive output hides value [OK]

Hint: Sensitive outputs hide secrets from console output [OK]

Common Mistakes:

• Thinking sensitive makes output public
• Assuming sensitive encrypts state file
• Believing sensitive increases output size

2. Which of the following is the correct syntax to declare a sensitive output in Terraform?

easy

A. output "db_password" { value = var.db_password
sensitive = true }

B. output "db_password" { value = var.db_password sensitive = true }

C. output "db_password" { value = var.db_password; sensitive = true }

D. output "db_password" { value = var.db_password, sensitive = true }

Solution

1. Step 1: Recall Terraform block syntax

   Terraform blocks use new lines or spaces between arguments without semicolons or commas.

2. Step 2: Identify correct syntax for sensitive output

   The correct syntax places sensitive = true on a new line inside the output block without semicolons or commas.

3. Final Answer:

   output "db_password" { value = var.db_password sensitive = true } -> Option A

4. Quick Check:

   Terraform blocks use new lines, no semicolons [OK]

Hint: Terraform blocks use new lines, no semicolons or commas [OK]

Common Mistakes:

• Using semicolons inside blocks
• Using commas between arguments
• Placing sensitive outside the output block

3. Given this Terraform output declaration:

output "api_key" {
  value     = var.api_key
  sensitive = true
}

What will Terraform display when you run terraform output?

medium

A. The actual API key value

B. An error saying output is sensitive

C. No output at all

D. <sensitive> placeholder instead of the value

Solution

1. Step 1: Understand sensitive output display behavior

   Terraform replaces sensitive output values with <sensitive> to avoid showing secrets.

2. Step 2: Confirm output command behavior

   Running terraform output shows <sensitive> for sensitive outputs, not the real value or errors.

3. Final Answer:

   <sensitive> placeholder instead of the value -> Option D

4. Quick Check:

   sensitive outputs show <sensitive> [OK]

Hint: Sensitive outputs show <sensitive> instead of real value [OK]

Common Mistakes:

• Expecting actual secret value to display
• Thinking terraform throws error for sensitive outputs
• Assuming no output is shown at all

4. You wrote this output block:

output "admin_password" {
  value = var.admin_password
  sensitive = "true"
}

Terraform gives an error. What is the problem?

medium

A. The value attribute cannot reference variables

B. The sensitive attribute must be a boolean, not a string

C. The output name cannot be admin_password

D. Missing a comma between value and sensitive

Solution

1. Step 1: Check the sensitive attribute type

   The sensitive attribute expects a boolean (true/false), not a string with quotes.

2. Step 2: Identify the error cause

   Using quotes around true makes it a string, causing Terraform syntax error.

3. Final Answer:

   The sensitive attribute must be a boolean, not a string -> Option B

4. Quick Check:

   sensitive = true (no quotes) [OK]

Hint: Boolean values in Terraform have no quotes [OK]

Common Mistakes:

• Putting quotes around boolean true/false
• Adding commas inside blocks
• Misnaming output blocks

5. You want to output a database password securely and also allow other Terraform configurations to access it without exposing it in the console. Which approach is best?

hard

A. Store the password in a public output without sensitive flag

B. Print the password normally in output and rely on user caution

C. Declare output with sensitive = true and use terraform output -json to pass value programmatically

D. Remove the output block and hardcode the password in other configs

Solution

1. Step 1: Protect password in output

   Marking output as sensitive hides it from console output, preventing accidental exposure.

2. Step 2: Enable programmatic access

   Using terraform output -json allows other configs or scripts to read the secret safely without showing it on screen.

3. Final Answer:

   Declare output with sensitive = true and use terraform output -json to pass value programmatically -> Option C

4. Quick Check:

   Use sensitive output + json output for safe secret sharing [OK]

Hint: Use sensitive output plus JSON output for safe secret sharing [OK]

Common Mistakes:

• Printing secrets openly in outputs
• Hardcoding secrets in configs
• Ignoring sensitive flag for secrets