Comment

Comment on Claude Code deletes developers' production setup, including its database and snapshots — 2.5 years of records were nuked in an instant

fubarx@lemmy.world ⁨1⁩ ⁨month⁩ ago

Given that the infrastructure description included the DataTalks.Club website, this resulted in a full wipe of the setup for both sites, including a database with 2.5 years of records, and database snapshots that Grigorev had counted on as backups. The operator had to contact Amazon Business support, which helped restore the data within about a day.

Non-story. He let Terraform zap his production site without offsite backups. But then support restored it all back.

I’d be more alarmed that a ‘destroy’ command is reversible.

source

Sort:hotnew top

CubitOom@infosec.pub ⁨1⁩ ⁨month⁩ ago
Distributed Non Consensual Backup

source
- eager_eagle@lemmy.world ⁨1⁩ ⁨month⁩ ago
  new kink unlocked
  
  source
db2@lemmy.world ⁨1⁩ ⁨month⁩ ago
Never assume anything is gone when you hit delete.

source
- Vlyn@lemmy.zip ⁨1⁩ ⁨month⁩ ago
  Except when it’s your own data, then usually you’re fucked.
  
  source
  - msage@programming.dev ⁨1⁩ ⁨month⁩ ago
    Usually not.
    
    But you might need a pay a professional.
    
    source
    Vlyn@lemmy.zip ⁨1⁩ ⁨month⁩ ago
    We already do, but that still doesn’t mean you’re safe.
    
    theguardian.com/…/unisuper-google-cloud-issue-acc…
    
    source
zr0@lemmy.dbzer0.com ⁨1⁩ ⁨month⁩ ago
For technical reasons, you never immediately delete records, as it is computationally very intense.

For business reasons, you never want to delete anything at all, because data = money.

source
- jaybone@lemmy.zip ⁨1⁩ ⁨month⁩ ago
  Back in the day, before virtualized services was all “the cloud” as it is today, if you were re-provisioning storage hardware resources that might be used by another customer, you would “scrub” disks by writing from /dev/random and /dev/null to the disk. If you somehow kept that shit around and something “leaked”, that was a big boo boo and a violation of your service agreement and customer would sue the fuck out of you. But now you just contact support and they have a copy laying around. 🤷
  
  source
- wewbull@feddit.uk ⁨1⁩ ⁨month⁩ ago
  Retaining data can mean violating legal obligations. Hidden backups can be a lawyers playground.
  
  source
  - zr0@lemmy.dbzer0.com ⁨1⁩ ⁨month⁩ ago
    Sure. Go ahead and find them based on pure speculation. First you have to put down $100k for all the forensics. Even if you would win the case, show me who is capable of doing something like that.
    
    source
- brbposting@sh.itjust.works ⁨1⁩ ⁨month⁩ ago
  Thought it could be a liability sometimes! Maybe that ship sailed
  
  source