Back to All Scenarios
PASSEDcloud / aws_ssm
AWS: SSM Parameter Store Rate Limit Hit
Application hitting AWS SSM Parameter Store rate limits during deployment. Config fetches failing across all services.
Pattern
AWS_CLOUD
Expected: AWS_RATE_LIMIT
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AWS_RATE_LIMIT | AWS_CLOUD | |
| Severity Assessment | HIGH | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
AWS SSM Parameter Store. 40 services fetching parameters simultaneously during rolling deployment. GetParameter rate limit: 40 TPS. All services failing startup.
Injected Error Messages (1)
AWS SSM rate limit — 40 services simultaneously fetching parameters during deployment, GetParameter 40 TPS limit exceeded, ThrottlingException, services failing to start
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_RATE_LIMIT)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnr8vc09c2lig74gkdvzjg