Terraform insights

Invalid ECS Task CPU/Memory Configuration Blocking Terraform Deployments

Terraform apply failures or ECS task launch failures occur when task definitions specify CPU and memory combinations not supported by Fargate, causing deployment rollbacks and service unavailability.

Terraform-Managed Lambda Concurrency Exhaustion Leading to S3 Throttling Cascade

When Lambda functions managed by Terraform reach reserved concurrency limits while processing S3 events, backpressure causes S3 request metrics to spike and queue depth to grow in dependent SQS queues, creating a cascading failure pattern across infrastructure components.

Terraform-Provisioned Consumer Lag Detected via SQS Queue Depth and Message Age

SQS queue depth (ApproximateNumberOfMessages) growing alongside ApproximateAgeOfOldestMessage indicates consumers provisioned via Terraform infrastructure-as-code are failing to keep pace with producers, often due to misconfigured CPU/memory limits in ECS task definitions or Lambda concurrency caps.

Missing CloudWatch Alarms for Infrastructure Provisioned by Terraform

Critical infrastructure components (Lambda, ECS, SQS, S3) provisioned via Terraform lack corresponding CloudWatch alarms, resulting in silent failures and extended mean-time-to-detection for production issues.

Multiple Lambda functions provisioned via Terraform compete for the same 1,000 concurrent execution account limit, causing throttling when aggregate demand exceeds quota, despite individual functions being properly sized.

S3 Lifecycle Policy Drift Causing Unexpected Storage Cost Increases

When S3 BucketSizeBytes grows exponentially for Standard storage class despite stable workload patterns, it often indicates S3 Lifecycle policies managed by Terraform are not being applied correctly, missing, or have drifted from desired state.