1 Answer
- Newest
- Most votes
- Most comments
0
It could be your account and corresponding region is already reaching Lambda's concurrent execution limit.
To fix this, you can either remove or reduce the ReservedConcurrentExecutions of your lambda functions or you can request AWS support to increase the concurrent execution limit.
answered 2 years ago
Relevant content
- asked 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
Thank you for the advice. As I can see on the quota page, the current utilization is 0, whereas applied quota value is currently 50. Do you know how many concurrent executions are required for aws-content-analysis? Also, does increasing this value would cost me? I am using a free-tier account.