this post was submitted on 21 Oct 2025
115 points (100.0% liked)
technology
24206 readers
286 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
About the AWS thing. Am i the only one who thinks it was a cyber attack? The US had done a cyber attack on China awhile before, and this would be a perfect way for China to say, "Fuck off." And it comes at a time where the Dutch are seizing a Chinese company, and the US is putting its tariffs back on. Among other things. I will be watching to see if theres another one in the coming months. We might be in a tit for tat cyber spiral between the US and China the way Israel and Iran did for awhile there.
Nah, it’s always DNS.
Well, they always SAY its DNS. That doesn't mean that's what it actually was.
Does it count as a self-inflicted cyberattack if you play layoff roulette with your senior staff and piss off anyone else remaining via RTO chumpfuckery to the point that you hemorrhage engineers left and right for multiple consecutive years, up until you get to the point where none of the new hires know how to fix your bread and butter when it inevitably goes tits up? Because maybe that framing would work.
But no, it was DNS. More specifically, a DynamoDB instance became unreachable by their control plane due to failed DNS resolution. Then, big bada boom. Recovery took significantly longer than usual on account of the aforementioned staffing issue.
How does this have anything to do with layoffs? They say this every AWS outage from years ago. It was a race condition on a DNS setting that wiped out a major one. Don’t artiunute to malice which is likely stupidity. DNS is incredibly easy to eff up and impossible to alert on
I'm not saying that a disgruntled ex-employee did something, I'm saying that due to brain drain -- in part due to layoffs in the name of "cost cutting" -- AWS had no experienced staff left who knew how to not fall into one of the incredibly easy DNS pitfall traps, and moreover, this had a direct impact on recovery time. It is 100% stupidity at an upper management level.
No chance it was a cyber attack. This is a very regular occurance, and it's because AWS is a labyrinthian nightmare of independently developed services that all rely on one another in a terribly incestous way.
It's an ongoing problem with AWS that has happened before and will happen again. The reason why it seems bigger is that more companies than ever have AWS services and social media blows everything up into grand historical events. It's simply the result of an old system that has experienced a lot of growth and changes which are held together with duct tape, paperclips, and chewing gum. The obvious fixes are too expensive and slower than just putting up with waiting for the DNS caches to clear and resolve over the course of several days. Basically, the fault lies with privatization and all the "optimization" that comes with system design under capitalism.
https://www.youtube.com/watch?v=KFvhpt8FN18
I found a YouTube link in your comment. Here are links to the same video on alternative frontends that protect your privacy:
I had a thought that it might be some sort of error that occurred from the merger of ring and flock, along with some sort of direct backdoor access given to the fash.
I have zero evidence for this, it's just idle speculation.