you are viewing a single comment's thread
view the rest of the comments
[–] 287 points 7 months ago (11 children)

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
  • hideshow 11 child comments
  • [–] 44 points 7 months ago (3 children)

    Never assume anything is gone when you hit delete.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 24 points 7 months ago (2 children)

    Except when it's your own data, then usually you're fucked.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 25 points 7 months ago (4 children)

    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
  • parent
  • hideshow 4 child comments
  • [–] 8 points 7 months 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
  • parent