[redis_mlc]

> Normally I wouldn't doubt it but in this sort of situation

Then you're very misinformed.

As a cloud administrator, I see resource availability and account limits on a weekly basis going back years.

I tell people:

- to pre-provision at least some extra servers rather than wait for an autoscaling operation to fail.

- that new instance types often are rolled out gradually, and lead time is often 1 month in AWS

- that killing a 1000-node cluster then expecting to immediately rebuild it often doesn't work.

- for DR and BCP planning, each region (or AZ) should be able to handle enough load at all times in case one region (or AZ) is unavailable. I've never seen anybody do that, even after I told them, because cost.

[ldoughty]

For AWS, limit monitor is a handy tool for "small" customers:

https://aws.amazon.com/solutions/limit-monitor/

It starts having issues when you get to 5,000+ ec2 instances, but it's somewhat understandable that they don't aim to support that level of usage within a single AWS account.

On another bullet point: if you go serverless (API/HTTP Gateway, Lambda, Dynamo DB), you automatically get full region DR. I personally recommend HTTP Gateway if you can swing it, API gateway is only worth of it you are doing personal projects (mostly free tier) or are seriously leveraging the API gateway specific features

[yekta_]

Seems like there's some confusion on what that one really does.

It only notifies you about your own Service Limits, so you will know before you hit one in an unfortunate moment. It's important to monitor that, but it doesn't protect or notify you against cloud provider's own limitations. A scale-out event can still fail if AWS has no more extra capacity ("full") even if your limits allow you otherwise.

AFAIK there's currently no way to know it beforehand if they actually have the capacity or not.