Bird
Raised Fist0
Terraformcloud~5 mins

Output values after apply in Terraform - Commands & Configuration

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction
When you create resources with Terraform, you often want to see important information about them after they are created. Output values let you display this information clearly after running your setup.
When you want to see the IP address of a server you just created.
When you need to get the URL of a website hosted on cloud resources.
When you want to share resource IDs with other teams or tools.
When you want to verify that your resources have the expected properties.
When you want to pass information from one Terraform configuration to another.
Config File - main.tf
main.tf
terraform {
  required_version = ">= 1.0"
}

provider "aws" {
  region = "us-east-1"
}

resource "aws_instance" "example" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
}

output "instance_id" {
  description = "The ID of the AWS instance"
  value       = aws_instance.example.id
}

output "instance_public_ip" {
  description = "The public IP address of the instance"
  value       = aws_instance.example.public_ip
}

This Terraform file creates a small AWS server instance.

The output blocks define values to show after the resources are created:

  • instance_id shows the unique ID of the server.
  • instance_public_ip shows the server's public IP address.
Commands
This command sets up Terraform in the current folder by downloading necessary plugins and preparing the environment.
Terminal
terraform init
Expected OutputExpected
Initializing the backend... Initializing provider plugins... - Finding latest version of hashicorp/aws... - Installing hashicorp/aws v4.0.0... - Installed hashicorp/aws v4.0.0 (signed by HashiCorp) Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure.
This command creates the resources defined in the configuration and automatically approves the changes without asking for confirmation.
Terminal
terraform apply -auto-approve
Expected OutputExpected
aws_instance.example: Creating... aws_instance.example: Still creating... [10s elapsed] aws_instance.example: Creation complete after 15s [id=i-0abcd1234efgh5678] Apply complete! Resources: 1 added, 0 changed, 0 destroyed. Outputs: instance_id = "i-0abcd1234efgh5678" instance_public_ip = "54.210.123.45"
→
-auto-approve - Automatically approve the apply without manual confirmation
This command shows only the public IP address output value from the last apply, useful for quick access.
Terminal
terraform output instance_public_ip
Expected OutputExpected
54.210.123.45
This command shows all output values defined in the configuration after the last apply.
Terminal
terraform output
Expected OutputExpected
instance_id = "i-0abcd1234efgh5678" instance_public_ip = "54.210.123.45"
Key Concept

If you remember nothing else from this pattern, remember: output values let you see and share important information about your created resources after Terraform finishes.

Common Mistakes
Not defining output blocks in the Terraform configuration.
Without output blocks, Terraform will not show any useful information after apply.
Always add output blocks for any resource details you want to see or share.
Running terraform output before terraform apply.
No outputs exist before resources are created, so the command returns empty or errors.
Run terraform apply first to create resources and generate outputs.
Using terraform apply without -auto-approve and expecting no prompt.
Terraform will pause and ask for confirmation, which can interrupt automated scripts.
Use -auto-approve flag in scripts to skip confirmation.
Summary
Define output blocks in your Terraform files to show resource details after creation.
Run terraform apply to create resources and see outputs immediately.
Use terraform output commands to view specific or all output values anytime after apply.

Practice

(1/5)
1. What is the main purpose of output values in a Terraform configuration?
easy
A. To create new cloud resources
B. To display important information after Terraform applies changes
C. To define variables used inside Terraform modules
D. To store Terraform state files remotely

Solution

  1. Step 1: Understand the role of output values

    Output values are used to show key information after Terraform finishes applying infrastructure changes.
  2. Step 2: Differentiate outputs from other Terraform features

    Variables define inputs, resources create infrastructure, and state files store deployment state. Outputs specifically display results.
  3. Final Answer:

    To display important information after Terraform applies changes -> Option B
  4. Quick Check:

    Outputs = display info after apply [OK]
Hint: Outputs show info after apply, not inputs or resources [OK]
Common Mistakes:
  • Confusing outputs with variables
  • Thinking outputs create resources
  • Mixing outputs with state storage
2. Which of the following is the correct syntax to define an output named instance_ip in Terraform?
easy
A. output "instance_ip" { value = aws_instance.example.private_ip }
B. output instance_ip = aws_instance.example.private_ip
C. output "instance_ip" = aws_instance.example.private_ip
D. output { instance_ip = aws_instance.example.private_ip }

Solution

  1. Step 1: Recall Terraform output block syntax

    Outputs use the block syntax: output "name" { value = ... }.
  2. Step 2: Match syntax to options

    output "instance_ip" { value = aws_instance.example.private_ip } matches the correct block syntax with quotes and value assignment.
  3. Final Answer:

    output "instance_ip" { value = aws_instance.example.private_ip } -> Option A
  4. Quick Check:

    Output block = output "name" { value = ... } [OK]
Hint: Outputs need block syntax with quotes and value key [OK]
Common Mistakes:
  • Missing quotes around output name
  • Using equals sign outside block
  • Incorrect block structure
3. Given this Terraform output block:
output "bucket_name" {
  value = aws_s3_bucket.my_bucket.id
}

What will Terraform display after terraform apply if the bucket ID is my-bucket-123?
medium
A. "aws_s3_bucket.my_bucket.id"
B. "my-bucket-123"
C. bucket_name = "my-bucket-123"
D. No output will be shown

Solution

  1. Step 1: Understand output display format

    Terraform outputs show the output name followed by an equals sign and the value.
  2. Step 2: Apply the known value

    The value aws_s3_bucket.my_bucket.id is "my-bucket-123", so output shows: bucket_name = "my-bucket-123".
  3. Final Answer:

    bucket_name = "my-bucket-123" -> Option C
  4. Quick Check:

    Output format = name = value [OK]
Hint: Outputs show name = value after apply [OK]
Common Mistakes:
  • Expecting only the value without name
  • Confusing resource attribute with output text
  • Thinking outputs are hidden by default
4. You wrote this output block:
output "db_password" {
  value = var.db_password
  sensitive = true
}

After terraform apply, you still see the password printed in the console. What is the likely cause?
medium
A. You ran terraform output -raw db_password after apply
B. You must set sensitive = false to hide output
C. Terraform does not support sensitive outputs
D. The output block syntax is invalid

Solution

  1. Step 1: Understand sensitive output behavior

    Sensitive outputs hide values in the terraform apply console and standard terraform output. However, terraform output -raw <name> bypasses this and shows the value.
  2. Step 2: Identify cause of exposure

    The likely cause is running terraform output -raw db_password, which reveals sensitive values.
  3. Final Answer:

    You ran terraform output -raw db_password after apply -> Option A
  4. Quick Check:

    Sensitive hides output unless -raw [OK]
Hint: Sensitive hides output unless -raw used [OK]
Common Mistakes:
  • Thinking sensitive = false hides output
  • Believing Terraform can't mark outputs sensitive
  • Assuming syntax error causes exposure
5. You want to output a list of instance IPs from multiple AWS instances created with a count. Which output block correctly returns all private IPs after apply?
resource "aws_instance" "web" {
  count = 3
  private_ip = "10.0.0.${count.index + 1}"
}

output "instance_ips" {
  value = ???
}
hard
A. aws_instance.web[0].private_ip
B. aws_instance.web.*
C. aws_instance.web.private_ip
D. [for i in aws_instance.web : i.private_ip]

Solution

  1. Step 1: Understand how to access multiple instances' attributes

    When using count, aws_instance.web is a list of resources. To get all private_ip values, use a for expression to extract each.
  2. Step 2: Evaluate options for correct syntax

    [for i in aws_instance.web : i.private_ip] uses a for expression to collect private_ip from each instance, which is valid and recommended.
  3. Final Answer:

    [for i in aws_instance.web : i.private_ip] -> Option D
  4. Quick Check:

    Use for expression to list attributes from count resources [OK]
Hint: Use for expressions to output lists from multiple resources [OK]
Common Mistakes:
  • Using wildcard (*) syntax without the attribute
  • Accessing single instance only
  • Trying to output resource without indexing