Back to All Scenarios
PASSEDcloud / aws_lambda
Lambda Function Throttled — Concurrent Execution Limit
An AWS Lambda function is being throttled because the account-level concurrent execution limit has been reached. Event-driven processing completely stalled.
Pattern
AWS_CLOUD
Expected: AWS_LAMBDA_THROTTLE
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | AWS_LAMBDA_THROTTLE | 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 Lambda function 'process-orders'. Account limit: 1000 concurrent. Currently 1000/1000 from a traffic spike. SQS trigger backing up. DLQ filling.
Injected Error Messages (1)
AWS Lambda throttled — function 'process-orders' hitting account-level concurrent execution limit (1000/1000), TooManyRequestsException, SQS backlog: 15,000 messages, DLQ: 230 messages
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_LAMBDA_THROTTLE)
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnoo60001clig7o6n137pr