Back to All Scenarios
PASSEDcloud / aws_route53
AWS: Route 53 Health Check Failed — DNS Failover Not Triggering
A Route 53 health check is failing but the failover record is not activating because the failover record was misconfigured.
Pattern
AWS_CLOUD
Expected: AWS_DNS_FAILURE
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AWS_DNS_FAILURE | AWS_CLOUD | |
| Severity Assessment | CRITICAL | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
AWS Route 53 hosted zone. Primary endpoint down. Health check ID hc-00004 failing. Failover routing policy but secondary record missing health check association. DNS still resolving to dead endpoint.
Injected Error Messages (1)
AWS Route 53 failover broken — health check hc-00004 failing (primary endpoint down), but DNS failover not triggering, secondary record missing health check association, clients still resolving to dead IP
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_DNS_FAILURE)
- Severity: HIGH (expected CRITICAL)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnr8vb09bilig75cm8jm3y