495
AWS is having a bad day (health.aws.amazon.com)
submitted 1 year ago by to c/selfhosted@lemmy.world
149 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 59 points 1 year ago (13 children)

It's mostly a skill issue for services that go down when USE-1 has issues in AWS - if you actually know your shit, then you don't get these kinds of issues.

Case in point: Netflix runs on AWS and experienced no issues during this thing.

And yes, it's scary that so many high-profile companies are this bad at the thing they spend all day doing

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 13 child comments
    •
  • [–] 22 points 1 year ago (3 children)

    Yeah, if you're a major business and don't have geographic redundancy for your service, you need to rework your BCDR plan.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 5 points 1 year ago*

    Absolutely this. We are based out of one region, but also have a second region as a quick disaster recovery option, and we have people 24/7 who can manage the DR process. We're not big enough to have live redundancy, but big enough that an hour of downtime would be a big deal.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 1 year ago (1 child)

    What's the general plan of action when a company's base region shits the bed?

    Keep dormant mirrored resources in other regions?

    I presumed the draw of us-east-1 was its lower cost, so if any solutions involve spending slightly more money, I'm not surprised high profile companies put all their eggs in one basket.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 1 year ago

    I presumed the draw of us-east-1 was its lower cost

    At no time is pub-cloud cheaper than priv-cloud.

    The draw is versatility, as change didn't require spinning up hardware. No one knew how much the data costs would kill the budget, but now they do.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 1 year ago* (last edited 1 year ago) (4 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 1 year ago (3 children)

    I would say that's a pretty minor issue that isn't related to the functioning of the service itself.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 0 points 1 year ago (2 children)

    It's probably by design that the only thing that didn't work was the cancel page

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •