Q: What is the `terraform_remote_state` data source and what are the risks of using it?
terraform_remote_state lets one Terraform module read outputs from another module's state file.
Want to master this scenario in a live sandbox? KodeKloud's HashiCorp Certified Terraform Associate (003) Interactive Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When terraform plan shows unexpected changes, my golden rule is: never apply blindly. Investigate the diff first. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
terraform_remote_state lets one Terraform module read outputs from another module's state file.
- Tight coupling — if the VPC module's output changes, the consuming module breaks.
- State access permissions — any module can read any state file it has S3 access to.
- State contains sensitive data — reading another state file may expose passwords, keys.
Remediation & Permanent Safeguards
Risks: Alternative: Use AWS SSM Parameter Store or Secrets Manager to share values between Terraform modules. Less coupling, better access control.
data "terraform_remote_state" "vpc" {
backend = "s3"
config = {
bucket = "my-tfstate"
key = "vpc/terraform.tfstate"
region = "us-east-1"
}
}
# Use VPC ID from another module
subnet_id = data.terraform_remote_state.vpc.outputs.private_subnet_id
- Tight coupling — if the VPC module's output changes, the consuming module breaks.
- State access permissions — any module can read any state file it has S3 access to.
- State contains sensitive data — reading another state file may expose passwords, keys.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Relying on legacy bucket ACLs instead of modern S3 Block Public Access and IAM bucket policies when configuring terraform remote state AWS recommends disabling ACLs (Bucket Owner Enforced) in favor of centralized declarative bucket policies and account-level Block Public Access controls.
-
Confusing SSE-S3 encryption with KMS customer-managed key (SSE-KMS) authorization policies when configuring terraform remote state
Accessing SSE-KMS encrypted objects requires both
s3:GetObjectandkms:Decryptpermissions; neglecting KMS key policies causes silent 403 Forbidden errors. - Using sequential timestamps or predictable prefixes for high-throughput S3 read and write keys when configuring terraform remote state Sequential key prefixes limit S3 horizontal partitioning; randomized hash prefixes distribute workloads across partitions to achieve 3,500 PUT and 5,500 GET requests/sec.
- Failing to audit S3 object delete markers when troubleshooting missing versioned objects when configuring terraform remote state Issuing a DELETE on a versioned bucket only adds a delete marker; engineers must retrieve previous versions or purge markers to restore data.