- cross-posted to:
- selfhosted@lemmy.world
- cross-posted to:
- selfhosted@lemmy.world
You must log in or register to comment.
I decided to look at right leaning site and they are blaming the outage on the Chinese. I’m just flabbergasted that they are still using the rhetoric that the Chinese government is trying to dismantle our democracy… They have serious blinders on thinking America needs help to fall into a fascist dictatorship. If the media is pointing to foreign enemies the real enemy is sitting in the
white houseMar-a-Logo.
the saddest episode of AWSatar: the last route mangler
FTFY
is the point of this comic to express how a single point of failure can bring a system down and the dns here definitely feels like a single point.
So is that an issue with DynamoDB’s system, or Amazon’s usage thereof?
not sure, it looks like its a different system that manages the DNS for DynamoDB. it got out of sync and deleted all the DynamoDB DNS records, that then broke all the internal AWS stuff
AWS is mostly built on AWS.
Yes, DNS started failing to properly fill name lookups. So, DynamoDB started failing. That started making security and other AWS services fail. Which in turn made higher level services fail.
It truly was a house of cards kind of moment.
Reading that article as a layman, I got the impression there were a lot of falling dominoes.
Unexpected behavior, leading to unexpected inputs to systems, often leads to failures. Put simply, nobody thought X would happen on Y service or at Z level, so nobody wrote code to handle that scenario. May sound crazy at first, but it’s quite hard to cover all possible scenarios when writing code… Or with life in general.
