this post was submitted on 05 Aug 2025
92 points (96.9% liked)

Tech

1679 readers
225 users here now

A community for high quality news and discussion around technological advancements and changes

Things that fit:

Things that don't fit

Community Wiki

founded 1 year ago
MODERATORS
 

A software engineer has warned against trusting cloud data storage services in a painstakingly detailed blog post detailing their own “complete digital annihilation” at the hands of AWS admins. Developer Abdelkader Boudih, pen name Seuros, says they had been a fee-paying AWS subscriber for a decade, with the cloud service becoming a firm part of their workflow. Suffice to say, the developer’s long-standing relationship with AWS has now ended acrimoniously.

you are viewing a single comment's thread
view the rest of the comments
[–] bitcrafter@programming.dev 13 points 1 day ago (5 children)

On top of all the other horrors, am I the only one seriously bothered by the fact that every dry-run is just a single fat-finger away from deleting all of a customer's data across all of AWS? I know that whenever I design a script to do something as dangerous as this, at the very least the default behavior is for it to do a dry-run so that if you want it to actually go ahead and make the changes you have to pass in an additional argument such as --confirm-deletion; for something this dangerous and apparently irreversible, I would probably also prompt the user to type "IAMSURE" before proceeding.

[–] fubarx@lemmy.world 4 points 1 day ago (3 children)

Protip: Never use the console or CLI.

Just use CDK. Test deleting and redeploying. Script the whole deployment process so it can be updated multiple times a day against different accounts by different people. Never worry about fat-fingering nothing.

[–] bitcrafter@programming.dev 1 points 18 hours ago (1 children)

That sounds even more reasonable to me!

What does "CDK" refer to?

[–] bamboo@lemmy.blahaj.zone 3 points 17 hours ago (1 children)
[–] bitcrafter@programming.dev 2 points 16 hours ago

Ah, so just adding the irony of AWS not even using its own tools to prevent these kinds of mishaps.

load more comments (1 replies)
load more comments (2 replies)