Hacker News Reader

Comment by Rezo | Hacker News Reader

Did you try simply asking AWS to raise the limit? It even suggests so on your linked page.

In my experience, every limit is immediately relaxed when requested; number of VPCs (I see people do horrible things to work around this all the time! Just ask!), EC2s / region, SES limits (need to send 10 million emails / day? No problem!), API Gateways / account, total ASGs... I believe all of these are there to keep you from shooting yourself in the foot through automation gone wrong or inexperience.

I've seen some crazy complicated architectures, where just sending an email or lifting up the phone solves the thing within an hour.

View on HN

I've been surprised/impressed by their quick and painless limit increases. It makes sense to have low default limits so people don't accidentally spin up a thousand instances or send a million emails. It seems the limits are mostly there to protect you from a bug or test in early development costing you a bunch of money.

>I believe all of these are there to keep you from shooting yourself in the foot through automation gone wrong or inexperience.

Also to prevent you from racking up huge bills in case an api key is compromised, and the attacker is able to spin up tons of instances for a botnet or something on your dime.

No! Thank you for pointing that out; I've always taken "limit" to mean hard but I shall no longer.

We had other reasons to move and it did end up working well for that project and others, but I can obviously only say that with hindsight.

They need to write that in big bold letters.

>number of VPCs (I see people do horrible things to work around this all the time! Just ask!)

I'm intrigued.

There are some limits they can't/don't want to increase.

I'm yet to find a limit that they won't adjust - what ones are you referring to?

S3 buckets are one I've seen. But there's not really a reason to have 100 s3 buckets, much less more than that.

Yes, that's one that you may not be able to change. From memory, they put that one in place to prevent the equivalent of bucket name squatting (since every bucket has a corresponding public domain name).

Reads/sec on a Kinesis shard is capped at 5 and can't be adjusted.

Reply on news.ycombinator.com