AWS: CloudFront Serving Stale Content After Cache Invalidation Failed
A CloudFront cache invalidation request failed silently. Users seeing old version of the website despite deployment.
Pattern
AWS_CLOUD
Expected: AWS_CDN_STALE
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
Metric
Expected
Actual
Result
Pattern Recognition
AWS_CDN_STALE
AWS_CLOUD
Severity Assessment
MEDIUM
HIGH
Incident Correlation
N/A
None
Cascade Escalation
N/A
No
Remediation
—
Auto-Heal — Corax resolves autonomously
Scenario Conditions
AWS CloudFront distribution E1ABC. Invalidation request for /* returned InProgress but never completed. TTL: 86400s. Users seeing old assets.
Injected Error Messages (1)
AWS CloudFront stale cache — invalidation stuck in 'InProgress' state for 2 hours, users seeing old website version, TTL 86400s, deployment completed but CDN not updated
Neural Engine Root Cause Analysis
AWS cloud infrastructure event detected — an EC2 instance may be unreachable or in a stopped state, an RDS database is experiencing issues, a load balancer has unhealthy targets, or a Lambda function is failing. AWS service disruptions can cascade across dependent resources and affect application availability.
Remediation Plan
1. Check the AWS Health Dashboard and Personal Health Dashboard for any active service events.
2. For EC2 issues, check instance status checks (system and instance), review CloudWatch metrics, and check VPC security group rules.
3. For RDS, verify database instance status, check storage and connection limits, and review slow query logs.
4. For ELB issues, check target group health checks and verify backend instances are responding.
5. For Lambda, review CloudWatch Logs for invocation errors and check IAM permissions and VPC connectivity.
Improvements Applied
Pattern classified as AWS_CLOUD (expected AWS_CDN_STALE)