Not able to set the Lambda Provisioning causing error "unreserved account concurrency is 10"
We are facing the lambda cold start issues. We used java and kotlin to build our backend applications following the serverless and micro service approach to deploy the data services inside lambda and api composition for front end apps in another lambda. The front end request goes to API GW and then to API Composition Lambda and goes to other Data Lambdas.
In order to reduce the cold start, we are trying to use provisioned concurrency on our lambda. But When I tried to change the config for provisioned concurrency, I got the below error
“The maximum allowed provisioned concurrency is 0, based on the unreserved concurrency available (10) minus the minimum unreserved account concurrency (10).“
Pasted the screenshot for reference.
Then I checked the configuration, it says the number of unreserved account concurrency is 10. Pasted the screenshot below for reference.
Now I am stuck with not able to increase the unreserved account concurrency and not able to provision the lambda.
I didn't understand what is going wrong. Can some expert here explain, what I am missing here and help understand fix the issue ?
- 最新
- 最多得票
- 最多評論
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
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.
相關內容
AWS 官方已更新 3 年前- AWS 官方已更新 1 年前
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.