That’s an entirely different type of problem, and avoidable by just using us-east-2 (I still don’t understand why people default to us-east-1 unless they require some highly specific services).
replyIs it that easily avoidable? A lot of AWS's control plane seems to have dependencies on us-east-1, or at least that's what it's looked like as a non-us-east-1 user during recent outages.
replyI don't know how much it's improved, but a bunch of URLs they use unnecessarily have region specific details in them.
replyI remember a Workspaces outage about 5 or 6 years ago, and the problem for us was that the redirect link in the console had US East 1 in it.
The workspaces themselves weren't in US East 1 and nothing relied on US East 1.
Emailing users who needed it an alternative link with a different region in the URL for the login redirect fixed it for us.
Sympathy. Railway is going to have numerous people blaming them for this outage. When us-east-1 fails, it is headline news, so you are not to blame.
replyDuring my 5 years of my startup, we had only 1 outage due to AWS because we picked us-west-2 as the primary reason. If anyone starting a company and picks us-east-1 as the primary reason, they should be fired. There's absolutely no reason to be in that region.
replyWhy do people want to be in that region? Is it the default or something?
replyI know some workloads help to be colocated but all these places are connected by fiber and every cloud has a worldwide CDN it seems.
If my cloud provider brings my startup down, it's my problem. If they bring all the startups down, that's their problem.
replyAnd we all celebrate it since we can't do any work
reply