Not able to set lambda reserved concurrency in new account

Hi,

I have a new account and only one lambda function in it. I cannot set the "reserved concurrency" of this lambda function as I get the error "The unreserved account concurrency can't go below 50". The unreserved concurrency is indeed 50. The same thing happens if I attempt to do it with the CLI.

I would like to set maximal 10 concurrent invocations of this function as to not overload an external backend. Why can't I set the reserved concurrency of this function?

主題

無伺服器運算

標籤

AWS Lambda

語言

English

AWS-User-7165951

已提問 2 年前檢視次數 1510 次

1 個回答

最新
最多得票
最多評論

已接受的答案

New accounts now get a max default concurrency of 50. If you need more, use the Service Quotas service to ask for an increase.

專家

Uri

已回答 2 年前

專家

Gary Mclean

已審閱 15 天前

AWS-User-7165951
2 年前
But why do I need to ask aws to increase it if I want exactly to limit the concurrency of my function ?
Uri 專家
2 年前
There is some internal limit that requires that there are at least 50 unreserved concurrency. As your limit is 50, setting reserved concurrency on a function will bring the remaining to less than 50, which is not allowed. Just ask for a small increase.

Not able to set lambda reserved concurrency in new account

相關內容