Hacker News new | past | comments | ask | show | jobs | submit login

> AWS will also honor pretty large quota increases without batting an eye, while Azure (and sometimes even GCP) would send similar numbers "for review" and take their sweet time.

I have so many bad experiences with limit increases on AWS.

I just went through one trying to get concurrent AWS Lambda executions increased from the default 1.000 in a region to 10.000. I had to open a support case, fill out an optional questionnaire (which turned out to be not optional at all), the support engineer had to forward the questionnaire to the AWS Lambda service team and they came back a few days later with: oh, you can have 5.000 concurrent executions.

Even worse a few years ago (not sure if that's still the case) we tried to get an increase of the sum of storage available as EBS-volumes. That took quite a bit back and forth with AWS and in the end we learned that they do reserve such EBS-storage for a customer no matter if the customer uses it or not. And mind: We didn't request something like guaranteed available EBS-storage, but instead just the ability to request more storage.




Yeah, this seems to be heavily service dependent.

EC 2 and ELB increases are relatively easy to come by, but for some services like Media Services things has to get reviewed by the service team which can take a while.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: