1 個回答
- 最新
- 最多得票
- 最多評論
0
The AWS Service Quotas page for Lambda has a Concurrent Executions page that contains monitoring. It's possible something is using more execution than you realize or perhaps your service quota is lower than the standard for some reason. I'd check there regardless of the fix.
Getting to the answer though, some potential fixes:
- Request a higher concurrent execution value in the Service Quotas area of the console
- Reduce or remove the configuration to add concurrency to the Lambda. I'm not sure of the exact sample you're using, but this may be in a configuration for the Lambda function or extracted in a generic configuration somewhere else.
- This documentation page will help shed some light on how it isn't necessarily reserved concurrency causing the problem, but could be executions in general: Reserved Concurrency
已回答 1 年前
相關內容
AWS 官方已更新 1 年前- AWS 官方已更新 2 年前
I tried creating the API in a region that has no functions, since execution quotas are based on regions, and I still had the error. I did request an increase to 20 concurrent executions to see if that will correct the error. I'll update the post once the request is complete.
Since this is an AWS template that I am using, I'm not able to change the configuration prior to creation. The Blog app I am trying to create is from the templates in AppSync. In AppSync, click on Create API. Step 1 in creating the API has an option to start from a sample project. I am trying to use the Blog App sample in order to learn how to connect the API to RDS using Lambda.