[reese_john]

  For our region that limit is set to 1000. That might sound like a lot when you start, but you quickly realise it’s easy to reach once you have enough Lambdas and you scale up. We found ourselves hitting that limit a lot once our traffic and therefore our demands from our system started scaling.

You can file a support ticket to have that limit raised.

https://docs.aws.amazon.com/servicequotas/latest/userguide/r...

[Jamie9912]

That's really annoying though.. Why should I have to go out of my way to increase capacity given that i'm paying for it anyway?

[ebbp]

Generally these limits exist so customers don’t accidentally spend more than they intend to — e.g. implementing a sort of infinite loop where Lambdas call each other constantly. Sounds implausible but I’ve seen that more than once!

[danielklnstein]

I understand the sentiment behind your frustration - but it's worth noting that these support tickets are usually answered really quickly.

Specifically as it relates to Lambdas there's solid rationale behind these limits, but I agree that in many other cases the limits seem arbitrary and annoying.

[tuetuopay]

The quotas are there for one good reason: the system running wild consuming way too much.

- for limited resources like IPs, it avoids one customer eating all the stock. Yes he’s paying for them, but other customers wouldn’t be able to get some anymore, generating frustrated users and revenue loss - for most other "infinite stock" resources, it avoids the bill exploding. It’s good for the customer, but also for the provider as they’re sure to be paid and not take a billing decline or sucking up all of a startup’s money.

[adobrawy]

One of the official reasons for the quota is to protect consumers from shooting themselves in the foot when they configure something incorrectly and start using the maximum available autoscaling resources which quickly makes bill to explode.