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
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
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.