| Author here:
Let’s be clear on backups: Yes, I had backups everywhere. Across providers, in different countries. But I built a system tied to my AWS account number, my instances, my IDs, my workflows. When that account went down, all those “other” backups were just dead noise encrypted forever.
Bringing them up to the story only invites the 'just use your other backups' fallback, and ignores the real fragility of centralized dependencies. It is like this: the UK still maintains BBC Radio 4’s Analogue Emergency Broadcast—a signal so vital that if it’s cut, UK nuclear submarines and missile silos automatically trigger retaliation. No questions asked. That's how much stakes they place on a reliable signal. If your primary analogue link fails, the world ends. That's precisely how I felt when AWS pulled my account, because I’d tied my critical system to a single point of failure. If the account was just Read only, i will waited because i could have access to my data and rotated keys. AWS is the apex cloud provider on the planet. This isnt about redundancy or best practices. it's about how much trust and infrastructure we willingly lend to one system. Remember that if BBC Radio 4 signal get to fail for some reasons, the world will get nuked, only cockroaches will survive… and your RDS and EC2 billing fees. |
How and why? Are you saying you had encrypted backups on other providers, but... Didn't keep the encryption keys to those backups somewhere handy and unencrypted? Why not? Can you even call that “backups”?
BTW, this is the first time in all this saga I've seen you mention other providers. Smells fishy.