173
What's the worst way you ever broke production? (lemm.ee)
submitted 2 years ago by to c/asklemmy@lemmy.world
103 comments fedilink hide all child comments
 

Fess up. You know it was you.

you are viewing a single comment's thread
view the rest of the comments
[–] 51 points 2 years ago (7 children)

Did you know that "Terminate" is not an appropriate way to stop an AWS EC2 instance? I sure as hell didn't.

  • permalink
  • fedilink
  • source
  • hideshow 7 child comments
    •
  • [–] 16 points 2 years ago (5 children)

    Explain more?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 32 points 2 years 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 29 points 2 years 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).

  • permalink
  • fedilink
  • source
  • parent
  • [–] 10 points 2 years ago (2 children)

    Apparently Terminate means stop and destroy. Definitely something to use with care.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •