1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Hello.
I thought it was related to the number of concurrent Lambda executions in the AWS account itself.
This should be the total for the AWS account region, not for each Lambda, so depending on the number of concurrent executions in the first Lambda, the second Lambda will also be affected.
https://docs.aws.amazon.com/lambda/latest/dg/lambda-concurrency.html
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 1年前
- AWS公式更新しました 1年前
- AWS公式更新しました 1年前
- AWS公式更新しました 3年前
Let me explain the detail, our account region has 2000 concurrency. We set concurrent limit A lambda 250 and B lambda 50. when A lambda request increase sharply, A reach concurrent 250 and throttling. But B concurrency only reach less than 10, B throttling also. We found B lambda request has no increase just like common. why B follow A throttling ?