21–30 of 219 posts
Does Amazon host its core infrastructure in us-east-1?
why wouldn't they?
After 2017 I'll never use US-east-1 again. Hell... I should have learned that particular lesson in 2011 but it took two catastrophic failures for me to figure it out.
There are numerous threads here on HN covering the topic "why does US-east-1 suck so hard."
https://news.ycombinator.com/item?id=13756082 is just one example.
Does Amazon host its core infrastructure in us-east-1?
[9:37 AM PST] We are seeing impact to multiple AWS APIs in the US-EAST-1 Region. This issue is also affecting some of our monitoring and incident response tooling, which is delaying our ability to provide updates.
I thought the whole point of AWS that it was a distributed system with no one point of failure? In that case, how did it have an outage?
I guess on a load balancer or DNS level? A request has to hit a single domain name / IP before it's load balanced to the distributed system right?
If this outage isn’t the catalyst to get the Amazon side of the house to finally move out of US-east, I don’t know what will be. Or at least be multi-region. Although the cost to make all of Amazon commerce, logistics, and digital truly multi-region is probably an order of magnitude more than the impact of this outage.
I thought the whole point of AWS that it was a distributed system with no one point of failure? In that case, how did it have an outage?
Does Amazon host its core infrastructure in us-east-1?
why wouldn't they?
"Neighbors in Tennessee city worry as Amazon packages pile up outside home"
Does Amazon host its core infrastructure in us-east-1?
I thought this story was about this house x-) "Neighbors in Tennessee city worry as Amazon packages pile up outside home" https://www.youtube.com/watch?v=qVQjEB2sxBw