Mastering Terraform Meta Arguments: count, depends_on, and for_each for AWS Infrastructure

Day-08 AWS Terraform Meta Arguments | count, depends_on, for_each

Terraform’s count, for_each, and depends_on meta arguments enable scalable AWS infrastructure. A 3-bucket example demonstrates how count creates multiple resources with unique identifiers.

Why This Matters

Terraform’s ideal model assumes resources are immutable, but real-world use requires managing dynamic scaling and dependencies. Misusing count can lead to resource recreation costs, while for_each ensures stable identities, reducing operational friction.

Key Insights

• “count creates multiple identical resources with numeric indexes, as shown in the S3 bucket example.”
• “for_each provides stable resource identities using maps/sets, avoiding recreation from order changes.”
• “depends_on explicitly controls resource creation order, essential for dependencies like IAM roles.”

Working Example

resource "aws_s3_bucket" "bucket_example" {
  count = 3
  bucket = "my-bucket-${count.index}"
}

resource "aws_s3_bucket" "bucket_foreach" {
  for_each = toset(["bucket-a", "bucket-b"])
  bucket = each.value
}

resource "aws_s3_bucket" "primary" {
  bucket = "primary-bucket"
}
resource "aws_s3_bucket" "secondary" {
  bucket = "secondary-bucket"
  depends_on = [aws_s3_bucket.primary]
}

Practical Applications

• Use Case: Deploying multiple identical S3 buckets with count for staging environments.
• Pitfall: Using count for resources requiring stable identities may lead to recreation on list reordering.

References:

• https://dev.to/amit_kumar_7db8e36a64dd45/-day-08-aws-terraform-meta-arguments-2im0

---