News for hackers. Stuff that matters.
Re:Tell HN: HN Moved from M5 to AWS by dralley on Friday July 08, 2022 @10:16PM (#32030716)
I hope this is only temporary. Where else will we discuss AWS outages when AWS goes down?

Not even a joke.

Re:Tell HN: HN Moved from M5 to AWS by cherioo on Friday July 08, 2022 @10:18PM (#32030733)
The IP appears to be us-west-2, so we will still be able to discuss us-east-1 outages alright!
Re:Tell HN: HN Moved from M5 to AWS by ignoramous on Friday July 08, 2022 @10:53PM (#32031046)
but... the s3 buckets are in us-east-1, and postgres in ap-southeast-2. More regions better than one, for maximum impact with minimum effort.
Re:Tell HN: HN Moved from M5 to AWS by pmoriarty on Saturday July 09, 2022 @06:28AM (#32033653)
The more regions a service is scattered over the greater the odds are that a single region outage somewhere in AWS will take down the whole service.

Consider the extreme case where your service is scattered over every AWS region: here an outage of any AWS region is guaranteed to take down your service.

Compare that to the case where your service is bound to only one region: then the odds of a single region outage taking down your entire service is reduced to 1 out of however many regions AWS has (assuming each region has an equal chance of suffering an outage).

To guard against outages, the failover service has to be scattered over entirely different regions (or, even better, on an entirely different service provider... which is probably a good idea anyway).

Re:Tell HN: HN Moved from M5 to AWS by ignoramous on Saturday July 09, 2022 @08:58AM (#32034654)
> The more regions a service is scattered over the greater the odds are that a single region outage somewhere in AWS will take down the whole service.

Agree. I think I should have suffixed a /s to my comment above.

> To guard against outages, the failover service has to be scattered over entirely different regions (or, even better, on an entirely different service provider... which is probably a good idea anyway).

Something, something... the greatest trick the devil (bigcloud) ever pulled...

Re:Tell HN: HN Moved from M5 to AWS by pojzon on Saturday July 09, 2022 @02:59AM (#32032575)
Is there at least one case when whole region went down ;)) ?
Re:Tell HN: HN Moved from M5 to AWS by withinboredom on Saturday July 09, 2022 @03:10AM (#32032639)
At least once, in 2012? I remember because just two days before we had fully switched over to AWS and hadn’t done multi-region yet. We got our first downtime in 10 years and there was nothing we could do, unlike when we had the servers in a colo. We were at the mercy of Amazon. After that, we moved everything back to real physical servers.
Re:Tell HN: HN Moved from M5 to AWS by samspenc on Saturday July 09, 2022 @02:48PM (#32038115)
Per the spreadsheet here https://awsmaniac.com/aws-outages/ :

There seem to have been multiple "full" outages in 2011-12 in AWS' us-east-1 region, which, granted, is the oldest AWS region and likely has a bunch of legacy stuff. By "full" outages I mean that a few core services fell over but the entire region become inaccessible due to those core failures.

Re:Tell HN: HN Moved from M5 to AWS by pojzon on Wednesday July 13, 2022 @03:22AM (#32079869)
Its over 10 years ago tho. Are there any RECENT full region outages ?

Im forseeing a full downtime in Frankfurt this winter tho. Germany is in really bad position when it comes to electricity.

Re:Tell HN: HN Moved from M5 to AWS by banana_giraffe on Friday July 08, 2022 @10:26PM (#32030803)
It appears to be pointing at a bare EC2 instance, no doubt a lift-and-shift.

Even during the most extreme AWS events, my EC2 instances running dedicated servers kept seeing Internet traffic.

Re:Tell HN: HN Moved from M5 to AWS by pmoriarty on Saturday July 09, 2022 @06:42AM (#32033733)
> Even during the most extreme AWS events, my EC2 instances running dedicated servers kept seeing Internet traffic.

You were just lucky enough not to have been affected by AWS outages, but many others were.

You can get a lot of resilience to failure on AWS, but simply spinning up a dedicated EC2 instance is not nearly enough.

Re:Tell HN: HN Moved from M5 to AWS by f0e4c2f7 on Friday July 08, 2022 @10:22PM (#32030775)
If architected correctly, stuff deployed into aws stays up during all but the most extreme outages.
Re:Tell HN: HN Moved from M5 to AWS by fulafel on Saturday July 09, 2022 @03:42AM (#32032838)
Of those "correctly" architected apps, most are not properly tested for the failovers and won't actually work as architected (because of your own bugs or because aws failover stuff has bugs and you can't even test it).

Eg, falls over due to steep traffic spikes caused by outages when autoscaling mechanisms get previously unseen levels of load increases and enter some yoyo oscillation pattern, whole AZ is overloaded because all the failovers from the other failing AZ triggering at once, hit circuit breakers, spin up too slowly to ever pass health checks etc. Or can't detect something becoming glacially slow but not outright failing.

See eg https://www.theverge.com/2021/12/22/22849780/amazon-aws-is-d... & https://www.theverge.com/2020/11/25/21719396/amazon-web-serv... etc (many more examples are out there)

Re:Tell HN: HN Moved from M5 to AWS by oars on Friday July 08, 2022 @10:32PM (#32030864)
And then where do we discuss these extreme outages?
Re:Tell HN: HN Moved from M5 to AWS by mekster on Saturday July 09, 2022 @12:11AM (#32031562)
Better to discuss the next day when it's over than seeing bunch of upset comments realtime posted.
Re:Tell HN: HN Moved from M5 to AWS by atmosx on Saturday July 09, 2022 @10:18AM (#32035327)
If the AWS status wasn’t a static HTML page, I would agree.
Re:Tell HN: HN Moved from M5 to AWS by VoidWhisperer on Saturday July 09, 2022 @12:09AM (#32031553)
HAM Radio
Re:Tell HN: HN Moved from M5 to AWS by namecheapTA on Saturday July 09, 2022 @12:40AM (#32031756)
People joke but from the top of a decent mountain I can reach 45 miles into the bay area from me on a $150 2m radio in my truck with rooftop antenna.
Re:Tell HN: HN Moved from M5 to AWS by loxias on Saturday July 09, 2022 @01:40AM (#32032132)
That is so cool. If I had that (truck+radio) I'd be very tempted to scatter a few cheap relay nodes at good locations in the bay area. Monkeybrains+comcast is quite reliable.
Re:Tell HN: HN Moved from M5 to AWS by iasay on Saturday July 09, 2022 @04:09AM (#32032992)
The problem with that is the only people you have to talk to is hams.

(Ex ham)

Re:Tell HN: HN Moved from M5 to AWS by nwh5jg56df on Saturday July 09, 2022 @06:02AM (#32033521)
Well same for computers & the internet :)
Re:Tell HN: HN Moved from M5 to AWS by iasay on Saturday July 09, 2022 @06:16AM (#32033585)
Fair point!
Re:Tell HN: HN Moved from M5 to AWS by staticassertion on Friday July 08, 2022 @11:43PM (#32031395)
If there's an extreme AWS outage, you're pretty much stuck to in-person or POTS.
Re:Tell HN: HN Moved from M5 to AWS by shawnz on Friday July 08, 2022 @10:37PM (#32030900)
where did you discuss outages of HN's previous provider?
Re:Tell HN: HN Moved from M5 to AWS by dralley on Friday July 08, 2022 @11:19PM (#32031229)
Less people are interested in outages of HN's previous provider.
Re:Tell HN: HN Moved from M5 to AWS by rubyist5eva on Friday July 08, 2022 @10:38PM (#32030913)
reddit.... shudders
Re:Tell HN: HN Moved from M5 to AWS by mariojv on Saturday July 09, 2022 @01:28AM (#32032050)
Re:Tell HN: HN Moved from M5 to AWS by Pakdef on Friday July 08, 2022 @10:45PM (#32030986)
Twitter is nice for learning about outages...
Re:Tell HN: HN Moved from M5 to AWS by lazylion2 on Saturday July 09, 2022 @05:04AM (#32033247)
/r/sysadmin