AWS us-east-1 down • Hacker News Board

Re: AWS us-east-1 down

#201

Post by inopinatus » Tue, Jun 13, 2023, 9:21 PM UTC

TremendousJudge wrote: post #68

kroltan wrote: 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.

It's also usually extremely US-centric. Nobody outside of North America has any idea what "PDT" or "Mountain Time" means.

Unnecessary reflux obtained during US-Australian collaboration from insufficiently specific references to "east coast time".

Re: AWS us-east-1 down

#202

Post by stephenc123 » Tue, Jun 13, 2023, 9:22 PM UTC

intsunny wrote: post #28

For those wondering: Currently PDT is 7 hours behind UTC. AWS can do so many things, reporting critical outage updates in UTC is not one of those things.

I've set the option on the below page to UTC

https://health.aws.amazon.com/health/status#settings

As I'm logged in, it persists across browser sessions.

Re: AWS us-east-1 down

#203

Post by ulrashida » Tue, Jun 13, 2023, 9:22 PM UTC

throaway87c10f0 wrote: post #164

Mysterious lack of "AWS is bad for the internet because it is so centralized" dialog up in here. edit: for those that would downvote: HN _just_ yesterday: https://news.ycombinator.com/item?id=36295352 https://news.ycombinator.com/item?id=36295305

Why a throwaway for this post? Not like this is some deep whistleblowing or career risk.

Re: AWS us-east-1 down

#204

Post by luhn » Tue, Jun 13, 2023, 9:24 PM UTC

adubashi wrote: post #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

I have never had a production issue in other regions due to a us-east-1 outage. The worst that ever happened was I had to wait to update a Cloudfront distribution because the control plane (based in us-east-1) was down, but the existing configuration continued working fine throughout.

I don't know what the architecture of IAM looks like, but somehow it's never suffered a global outage.

AWS is really, really good at regional isolation.

Re: AWS us-east-1 down

#205

Post by underbluewaters » Tue, Jun 13, 2023, 9:26 PM UTC

kobalsky wrote: post #71

dijit wrote: 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. $$$$$$$$$$$$$$

This should be logarithmic

Re: AWS us-east-1 down

#206

Post by akira2501 » Tue, Jun 13, 2023, 9:28 PM UTC

andrewmcwatters wrote: post #74

impulser_ wrote: post #69

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?

There's a lot of software, iirc even Amazon's own dashboards, that simply defaults to us-east-1.

That's my favorite part of Amazon's console. That miniature heart attack you have when you ask "WHERE ARE ALL MY LAMBDAS AND DYNAMO INSTANCES?"

Then you realize that they just switched you back to us-east-1 for some reason and a wave of familiar relief washes over you.

Re: AWS us-east-1 down

#207

Post by jdlyga » Tue, Jun 13, 2023, 9:29 PM UTC

Most stuff is back up, but AWS MediaConvert still seems to be down.

Re: AWS us-east-1 down

#208

Post by JoBrad » Tue, Jun 13, 2023, 9:29 PM UTC

inconceivable wrote: post #100

jjice wrote: post #89

Earlier quoted context omitted.

As a side note, I wonder if businesses won't even accept cash if they can't go through their POS system. If not, it's a shame that these modern internet connected POSs lock out stuff like that.

some restaurants have their owner or manager run square or stripe on their cell phone.

I was at a swim meet last week, and one of the food trucks was using Apple Tap to Pay because Toast didn't have a solution that worked for them, on site. After they finish up at an area, they then enter a single transaction for all of the day's business into Toast.

Re: AWS us-east-1 down

#209

Post by jedberg » Tue, Jun 13, 2023, 9:30 PM UTC

adubashi wrote: post #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

Usually it only prevents changes, but the runtime isn't affected.

Re: AWS us-east-1 down

#210

Post by jacobr1 » Tue, Jun 13, 2023, 9:31 PM UTC

tazjin wrote: post #94

TremendousJudge wrote: post #68

Earlier quoted context omitted.

It's also usually extremely US-centric. Nobody outside of North America has any idea what "PDT" or "Mountain Time" means.

Everyone knows "Mountain Time". It is when you go to the mountains on vacation, and don't spend much time adhering to a strict schedule, instead taking leisurely strolls around the fields and promising vague things like "I'll try to be back for dinner".

Closely related, yet distinct from, Island Time