Back to All Scenarios
PASSEDcloud / aws_rds
RDS Storage Full — Writes Failing
An RDS PostgreSQL instance hit its allocated storage limit. All write operations failing. Autoscaling storage not enabled.
Pattern
AWS_CLOUD
Expected: AWS_RDS_STORAGE
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AWS_RDS_STORAGE | 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 RDS db.r5.large. PostgreSQL 15. Allocated 100GB, used 100GB. Storage autoscaling: disabled. FreeStorageSpace CloudWatch alarm firing.
Injected Error Messages (2)
AWS RDS storage full — instance prod-db at 100% storage (100GB/100GB), all INSERT/UPDATE operations failing with 'FATAL: could not extend file', autoscaling not enabled
Application returning 500 errors — all database write operations failing, user registrations, orders, and updates rejected, read operations still working
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_RDS_STORAGE)
- Severity: HIGH (expected CRITICAL)
Tested: 2026-04-02Monitors: 2 | Incidents: 2Test ID: cmnhnoo5z0019lig73l2aox9s