Fess up. You know it was you.

    • Quazatron@lemmy.world
      link
      fedilink
      arrow-up
      33
      ·
      10 months ago

      Noob was told to change some parameters on an AWS EC2 instance, requiring a stop/start. Selected terminate instead, killing the instance.

      Crappy company, running production infrastructure in AWS without giving proper training and securing a suitable backup process.

    • ilinamorato@lemmy.world
      link
      fedilink
      arrow-up
      29
      ·
      10 months ago

      “Stop” is the AWS EC2 verb for shutting down a box, but leaving the configuration and storage alone. You do it for load balancing, or when you’re done testing or developing something for the day but you’ll need to go back to it tomorrow. To undo a Stop, you just do a Start, and it’s just like power cycling a computer.

      “Terminate” is the AWS EC2 verb for shutting down a box, deleting the configuration and (usually) deleting the storage as well. It’s the “nuke it from orbit” option. You do it for temporary instances or instances with sensitive information that needs to go away. To undo a Terminate, you weep profusely and then manually rebuild everything; or, if you’re very, very lucky, you restore from backups (or an AMI).

      • tslnox@reddthat.com
        link
        fedilink
        arrow-up
        7
        ·
        10 months ago

        Maybe there should be some warning message… Maybe a question requiring you to manually type “yes I want it” or something.

        • synae[he/him]@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          5
          ·
          10 months ago

          Maybe an entire feature that disables it so you can’t do it accidentally, call it “termination protection” or something