Back to All Scenarios
PASSEDcloud / aws_ec2
EC2 Instance Failed Health Check — StatusCheckFailed_System
An EC2 instance failed the system status check due to underlying hardware issues. Instance is unreachable. AWS recommends stop/start to migrate to healthy hardware.
Pattern
AWS_CLOUD
Expected: AWS_EC2_FAILURE
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AWS_EC2_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 us-east-1. t3.large instance (i-0abc123). StatusCheckFailed_System=1. Instance running for 145 days. EBS volumes attached. No auto-recovery configured.
Injected Error Messages (1)
AWS EC2 system status check failed — instance i-0abc123 unreachable, StatusCheckFailed_System=1, underlying hardware issue, AWS recommends stop/start to migrate, no auto-recovery action configured
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_EC2_FAILURE)
- Severity: HIGH (expected CRITICAL)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnoo5z0017lig7s85w5suo