2 Answers
- Newest
- Most votes
- Most comments
2
Hi,
Not a direct answer to above, but have you tried to use Snapstart instead? Could be an easier win than provisioned concurrency for cold start: https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html
0
It looks like our account is created 4 months ago. Seems new account will have low values for the quota. After we raised the quota increase request from AWS console, the allocated number is increased. After the increase we are able to set the provisioned concurrency values.
answered a year ago
Relevant content
- Accepted Answerasked 9 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
The snapstart is not available in ap-south-1
Interesting. So when looking at this page: https://aws.amazon.com/premiumsupport/knowledge-center/lambda-concurrency-limit-increase/#:~:text=Important%3A%20If%20you're%20using,invocations%20at%20any%20given%20time, it says: "The default concurrency limit per AWS Region is 1,000 invocations at any given time. However, note that new AWS accounts have reduced concurrency and memory quotas." Is your account a new one?
We created this account 4 months ago. Not sure how much recency qualifies for the "new" account in this case. I also asked for quota rise support.
It will depend on usage. If account was created 4 months ago and then barely used, the limitations may still apply. Let me know if issue goes away by raising limits
After we raised the quota increase, the number is increased, after that we are able to set the provisioned concurrency values.