AWS Lambda throttled, but no evidence in the metrics

2
votes

When running Lambda in high concurrency, I receive error CloudWatch logs below (which I haven't seen anywhere else on the web!).

Execution failed due to configuration error: Lambda was throttled while using the Lambda Execution Role to set up for the Lambda function

When I check the "Throttled invocations" metric, it doesn't show these throttles.

Why doesn't the metric show these throttles? Has anyone seen this throttle error before? It is not the usual throttle error.

1
amazon-web-servicesaws-lambdaamazon-cloudwatch
Interesting. To my eye, this is saying the Lambda service got throttled itself, internally, by another service (IAM? STS? S3? EC2? Something else? Maybe even another component of the Lambda service?) while it was trying to access or allocate some kind of resource on your behalf ("while using the Lambda Execution Role"). Of course, that probably wouldn't be a "configuration error," although most errors that occur "while using the Lambda Execution Role" would be related to insufficient permissions on the role. - Michael - sqlbot
What I'm suggesting is that the error message you are seeing is actually the result of some variant of a template, inside Lambda itself, that looks something like Execution failed due to configuration error: ${internal_error}. Rather than a pure, proper throttling event, this was something different. Note for example the similar patterns here and here. - Michael - sqlbot
I got the same error when calling aws lambda. There is no evidence in throttling metrics and in cloud watch as well. - Pawel

1 Answers

1
votes

For me it was API Gateway throttling that caused this issue even though I wasn't even near throttling limits - after removing limit on API GW(going back to default settings) I haven't faced this issue anymore