Over the past couple of weeks, I started thinking a bit more about adding resiliency to my personal projects and accounts.
You can follow my entire thought process on Twitter (see the embedded Tweet below),
but in this blog post I’m going to focus on Github.
Following AWS, the second most critical service for my projects is Github: 90% of my code is stored there (mostly in private projects), and I have to admit I never took a backup of this data.
So I finally decided to set some time aside to set up an automated process to backup my Github account, and I ended up relying on ECS (Fargate) and S3 Glacier.
This blog explains the architecture and implications of the final setup I decided to go with.