The data fetched from Github is zipped and uploaded to an S3 bucket, where it will transition to Glacier after one day.Backups of my Github account are taken via an ECS on Fargate Task Definition, with execution triggered periodically by a CloudWatch Event Rule, and secrets (i.e., the Github PAT) pulled from Parameter Store.A thread 🧵- Marco Lancini June 21, 2021Īt a high level, this is how the final setup looks like:

In the past couple of weeks, I started thinking a bit more about adding resiliency into my personal projects/accounts. This blog explains the architecture and implications of the final setup I decided to go with. 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. You can follow my entire thought process on Twitter (see the embedded Tweet below),īut in this blog post I’m going to focus on Github.įollowing 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. Over the past couple of weeks, I started thinking a bit more about adding resiliency to my personal projects and accounts.

Aws glacier for personal backup