[foo4u]

The same functionality could have been accomplished by just allowing us to specify the max number of concurrent instances of a function that can be active at a time. With proper request queuing the problem would be solved. As usual, AWS solves a problem they failed to design for by charging for an overly complex solution. Flame me if you want but there are K8s serverless frameworks that address this out of the box.

[pavelrub]

Specifying the max number of concurrent lambda execution has been possible for years - it's called reserved concurrency.

This does nothing to solve the issue however. There are many use cases where you can't delay handling requests.