Matt The Horwood@lemmy.horwood.cloud to Selfhosted@lemmy.worldEnglish · 2 days agoAWS is having a bad dayhealth.aws.amazon.comexternal-linkmessage-square150fedilinkarrow-up1497
arrow-up1497external-linkAWS is having a bad dayhealth.aws.amazon.comMatt The Horwood@lemmy.horwood.cloud to Selfhosted@lemmy.worldEnglish · 2 days agomessage-square150fedilink
minus-squareB0rax@feddit.orglinkfedilinkEnglisharrow-up4·edit-21 day ago Case in point: Netflix runs on AWS and experienced no issues during this thing. But Netflix did encounter issues. For example the account cancel page did not work.
minus-squareNorah (pup/it/she)@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up1·14 hours agoI would say that’s a pretty minor issue that isn’t related to the functioning of the service itself.
minus-squarekbobabob@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up1·11 hours agoIt’s probably by design that the only thing that didn’t work was the cancel page
minus-squareNorah (pup/it/she)@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up2·11 hours agoThat’s honestly just a tin-foil hat sort of take, that entirely relies on planning for an unprecedented AWS outage specifically to screw over customers.
minus-squarekbobabob@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up1·4 hours agoWhat I meant by that is that they probably didn’t care if that service has a robust backup solution like authentication or something would.
But Netflix did encounter issues. For example the account cancel page did not work.
I would say that’s a pretty minor issue that isn’t related to the functioning of the service itself.
It’s probably by design that the only thing that didn’t work was the cancel page
That’s honestly just a tin-foil hat sort of take, that entirely relies on planning for an unprecedented AWS outage specifically to screw over customers.
What I meant by that is that they probably didn’t care if that service has a robust backup solution like authentication or something would.