Why outputs expose useful information in Terraform - Why It Works

Introduction

When you create infrastructure with Terraform, you often need to see important details about what was created. Outputs let you show these details clearly after Terraform finishes. This helps you use the created resources in other places or check that everything is correct.

When you want to see the IP address of a server you just created.

When you need to share resource IDs with other teams or tools.

When you want to confirm that your infrastructure has the expected names or tags.

When you want to pass information from one Terraform module to another.

When you want to quickly check important values without searching through the state file.

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" {
  value       = aws_instance.example.id
  description = "The ID of the created EC2 instance"
}

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

This Terraform file creates a small AWS EC2 instance.

The output blocks show the instance ID and its public IP address after creation.

This helps you quickly find these important details without digging into the state file.

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/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. All Terraform commands

should now work.

This command creates the infrastructure defined in the configuration file without asking for confirmation.

Terminal

terraform apply -auto-approve

Expected Output

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 - Skip manual approval to apply changes immediately

This command shows only the public IP address of the created instance, making it easy to copy or use in other commands.

Terminal

terraform output instance_public_ip

Expected Output

54.210.123.45

Key Concept

If you remember nothing else from this pattern, remember: Terraform outputs let you see and share important details about your created infrastructure easily and clearly.

Common Mistakes

Not defining outputs for important resource attributes.

Without outputs, you have to search the state file or AWS console to find key information, which is slow and error-prone.

Always define outputs for resource IDs, IPs, or other values you will need after deployment.

Using outputs to expose sensitive information without protection.

Outputs are visible to anyone with access to the Terraform state, risking data leaks.

Mark sensitive outputs with the 'sensitive = true' flag to hide them from normal output.

Summary

Use 'output' blocks in Terraform to show important resource details after deployment.

Run 'terraform apply' to create resources and see outputs immediately.

Use 'terraform output <name>' to get specific output values easily.