Hacker News Reader

Comment by zedpm | Hacker News Reader

Kudos for Amazon sorting out their status page. The last time this happened, the status page didn't show anything until hours after the outage began. I just noticed this one maybe 15 minutes ago, and 5-10 minutes later they acknowledged the problem.

On the other hand, I'm feeling a strong case of "Not this shit again". Wondering if US-East-1 is more trouble than it's worth, as these outages seem to happen mostly there.

View on HN

Us-east-1 is where all the shiny new features are released and where most customers are. From experience the other regions are much more reliable.

> Us-east-1 is where all the shiny new features are released

Not true at all. It'll be among the first for newer features, in as much as the US regions usually are among the first, but it's certainly not the first place code is deployed to.

All services in AWS start out software deployments in smaller regions where the blast radius of a software bug is likely to be smaller.

I thought us-east-1 had the most issues because it is the oldest region and thus uses the oldest hardware.

It’s primarily just due to the incredible scale of the region. It’s easily twice as large as any other, so any issues relating to scale appear there first and are fixed before they affect any of the other regions.

It might also be related to IAM and some other stuff being "based" there.

What do you mean "based" there?

As in, most global services run primarily within us-east-1, and have only subsystems running in each region.

For example, it's likely that the actual master data stores for IAM are solely within us-east-1, but the key data is cached and services run in each region.

Similarly, Cloudfront is theoretically a global service, but only ACM certificates set up within us-east-1 can be used with Cloudfront.

That may be changing. FIFO SQS queues were only available in the Ohio region until several months later.

Looks like November 17 to June 14.

[1] https://aws.amazon.com/about-aws/whats-new/2016/11/amazon-sq...

[2] https://aws.amazon.com/about-aws/whats-new/2017/06/amazon-sq...

Oregon seems to have most or all of the features. We have a task to move from us-east-1 to oregon, but haven't completed it yet.

We launched our production workload in us-west-2 (Oregon) 4 years ago for this exact reason and it was one of the best decisions we made. Our staging servers in us-east-1 have experienced all of the outages between then and now, but production hums right along. Of course we're ready to failover to us-east-1 if us-west-2 has trouble, but it's been far more stable (knock on wood).

Working for a consultancy and we pretty much always default to doing initial (MVP) deploys in Oregon these days. Feels like a no brainer at this point.

If us-east and us-west regions are only relevant to you because of the relative reliability, then I envy your situation because latency doesn't exist in your world.

us-east-2 is a thing, just saying.

It has been tribal knowledge for at least five years to stay away from us-east-1

Oregon sees almost the same speed of adoption of new features with way better reliability.

We just switched to US West Oregon and I'm not looking back.

Reply on news.ycombinator.com