Live data from Hacker News

AWS us-east-1 down

news.ycombinator.com

111–120 of 331 posts

Re: AWS us-east-1 down

#111

https://health.aws.amazon.com/health/status reports: Increased Error Rates and Latencies Jun 13 12:08 PM PDT We are investigating increased error rates and latencies in the US-EAST-1 Region. They list Lambda as the only affected service

certificate manager also down (I know because I tried to update an ssl cert for cloudfront which only allows US-East-1 ssl certs, maybe someone will eventually fix that to allow any region to have the ssl cert for cloudfront)

Re: AWS us-east-1 down

#112
post #4

I wonder if this is a coincidence or if us-east-1 is simply down enough that I'm just experiencing selection bias; but I posted a poll on twitter earlier today: https://twitter.com/dijit/status/1668678588713824257 Contents: > Has anyone ever actually had customers accept an outage because AWS was down; or is this just cloud evangelicalism copium? > [ ] Yeah, outages free pass > [ ] No, they say to use AZ's

it's important to inform customers about the resiliency of their systems and let them pick how far they are going to invest for it. then you get to eat popcorn when stuff explodes. * single server event. $ * multi server event. $$ * single az event. $$$ * multi az event. $$$$ * global provider event. $$$$$ * cross provider event. $$$$$$ * alien invasion. $$$$$$$$$$$$$$

Just need to deploy your service on Mars AND Earth. Duh

Re: AWS us-east-1 down

#113
post #60

Earlier quoted context omitted.

Semi-related: if you ever feel the need to report times to a global audience, not only make sure to always report the timezone (even if it is the same as the user's), but also use UTC offsets rather than timezone names. Life is too short to remember what each timezone name means and converting to it, UTC offsets are much easier on the mental calculator.

just report it in epoch seconds

Julian Date

Re: AWS us-east-1 down

#116

https://health.aws.amazon.com/health/status reports: Increased Error Rates and Latencies Jun 13 12:08 PM PDT We are investigating increased error rates and latencies in the US-EAST-1 Region. They list Lambda as the only affected service

I suppose "increased error rates and latencies" is technically true when the error rate is 100% and the latency is "until we fix it"

Re: AWS us-east-1 down

#117
post #17

https://health.aws.amazon.com/health/status reports: Increased Error Rates and Latencies Jun 13 12:08 PM PDT We are investigating increased error rates and latencies in the US-EAST-1 Region. They list Lambda as the only affected service

They've added a dozen or so more as potentially down now. Anything that uses IAM, which I suspect is the core of the issue.

They have 41 services listed now.

Re: AWS us-east-1 down

#118
It doesn't matter if your infra is in another region, because there will almost always be transitive dependencies on us-east-1. IAM is deployed in us-east-1 and there will always be a transitive dependency on us-east-1

Re: AWS us-east-1 down

#119
post #46

Why is it always us-east-1 though? I have always stayed away from that region because it seems significantly less reliable than other regions.

It's the: * Largest (DDoS'd most, most complex, scaling issues etc) * Oldest (More time for weird idiosyncrasies to take hold) * Where most testing happens * Where new products are deployed first

It's also

* The only place where the IAM dashboard can be accessed from. I need to access it NOW. I can't.

Re: AWS us-east-1 down

#120

Why does everyone keep deploying their products to this one region when it always seems like the one that fails? We don't use big cloud were I work, so maybe I'm missing something. Does East-1 offer something other don't?

Instance types, for one. us-east-1 has all the latest instance types and more of them. We could not run some of our workloads in any other region.
Post reply on HN