There is no way to reserve Lambda concurrency without reducing the unreserved concurrency, but the unreserved concurrency can be easily increased with a support request, which you can open directly from the Service Quotas page: https://us-east-1.console.aws.amazon.com/servicequotas/home/services/lambda/quotas/L-B99A9384
Answer from Shahar Mosek on Stack Overflowamazon web services - AWS Lambda limit concurrency from Unreserved concurrency pool - Stack Overflow
How does Lambda reserved concurrency interact with Cloudwatch Events?
AWS Lambda Reserved Concurrency
Better understanding in Lambda concurrency and power
Videos
Hey! Maybe this is a dumb question, maybe a coincidence.
We have a lambda configured to use Reserved Concurrency = 5.
Sometimes this lambda takes more than a minute run and, when we trigger this lambda with more than 50 requests ( it is fired by sqs ), we notice that the lambda returns 5 by 5 and it ends its execution all 5 together.
For example, we have a bunch of requests which takes 5 seconds to process each, if we trigger our lambda with 40 requests if one take more than 30s, the lambda return 5 of the results together after 30 seconds, even if the others takes less than 2 or 3s.
Is this a common behavior for lambdas with reserved concurrency?
It sends 5 requests, waits until all 5 executes then send more 5? Or it send 5 requests, when one ends it sends another one to keep 5 itens running concurrently?