how to set a lambda quote template to the previous default of 1000

0

It seems like the recent switch to as-needed provisioned concurrency left a lot of loose ends. The thing I am dealing with currently is that in addition to having to wait for support to approve my single-tenant customers for 1000 reserved concurrency, I also have no way of requesting just 1000 via an organization template. The minimum you can request is 1001.

Is there a way to set the requested reserved concurrency for new accounts in my organization to 1000?

fdllc
已提問 7 個月前檢視次數 168 次
1 個回答
0

Hi,

just to avoid any confusion, reserved concurrency is the maximum number of concurrent instances you want to allocate to your function. When a function has reserved concurrency, no other function can use that concurrency.

Every account has a default limit of 1000 concurrent executions, see AWS Lambda limits. This means you can set the reserved concurrency to at most 900 as you can reserve up to the unreserved account concurrency value minus 100, see concurrency configuration.

So, in order to set the function reserved concurrency to 1000, you will to increase the account concurrency to 1100. See this post on how to increase the limits.

profile pictureAWS
專家
已回答 7 個月前
  • Hi Ben,

    Every account has a default limit of 1000 concurrent executions

    I wish that were still the case but sadly this is not true any more. Most new accounts now get 10 default reserved concurrent executions. I am not sure if that is documented anywhere but unfortunately when creating new accounts this is what is happening in practice. Some searching around this forum should confirm what I am saying.

    Best, Dave

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南