Recently, one of my websites went down. After noticing, I checked my EC2 dashboard and saw the instance stopped. AWS had emailed me to say that due to a physical hardware issue, it was terminated. When an instance is terminated, all of its data is lost. Luckily, all of my data is backed up automatically every night.<\/p>\n
Since I don’t use RDS, I have to manually manage data redundancy. After a few disasters, I came up with a solution to handle it<\/a>. I trigger a nightly cron-job to run a shell script. That script takes a MySQL dump and uploads it to S3.<\/p>\n As long as I have the user generated data, everything else is replaceable.\u00a0 The website that went down is a fitness tracking app<\/a>. Every day users record their martial arts progress. Below are the ten steps taken to bring everything back up.<\/p>\n Use this as a checklist to make sure you don’t forget any steps. Read through the blog posts that I hyperlinked to get more details.<\/p>\n","protected":false},"excerpt":{"rendered":" Recently, one of my websites went down. After noticing, I checked my EC2 dashboard and saw the instance stopped. AWS had emailed me to say that due to a physical hardware issue, it was terminated. When an instance is terminated, all of its data is lost. Luckily, all of my data is backed up automatically … <\/p>\n\n