GitBackups

Storage guides

Back up GitHub to Wasabi

Gitbackups backs up your GitHub repositories on a schedule into a bucket you own. This guide sets up Wasabi for it in about five minutes. You end up with:

  • A private bucketYours. The backups stay if you leave.
  • A narrow keyOnly what backups need, on one bucket.
  • A cleanup ruleClears the leftovers of a failed upload.

How Gitbackups connects to Wasabi

  • Gitbackups talks to Wasabi’s S3-compatible API at https://s3.<region>.wasabisys.com, with virtual-hosted addressing.
  • Each run uploads every repository as a git bundle file, at <prefix><owner>/<repo>/<timestamp>-<id>.bundle. The files are yours: if you stop using Gitbackups, they stay where they are.
  • It never lists your bucket. Every file it writes is recorded on our side, so retention deletes only files Gitbackups wrote, and the newest backup of each repository is never deleted.
  • On GitHub, Gitbackups is a GitHub App that asks for read access to repository contents and nothing more.

1. Create the bucket

  • Wasabi console → Buckets → Create Bucket.
  • Note the region you pick. You will need it in step 6.
  • Leave versioning off (see step 5).

2. Create a key for Gitbackups only

  • Access Keys → Create Access Key.
  • Choose Sub-User, not Root User, then Create.
  • Choose Show to reveal the secret, then download the CSV or copy both values. Wasabi won’t show them again.

3. Give it these four permissions, and no more

  • Wasabi takes S3 policy documents. Attach the policy below to that sub-user.
  • Replace BUCKET with your bucket, and gitbackups/ with your prefix.
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "GitbackupsArchives",
      "Effect": "Allow",
      "Action": [
        "s3:PutObject",
        "s3:GetObject",
        "s3:DeleteObject",
        "s3:AbortMultipartUpload"
      ],
      "Resource": "arn:aws:s3:::BUCKET/gitbackups/*"
    }
  ]
}

4. Add the incomplete-upload cleanup rule

Bucket → Settings → Lifecycle.

Add a rule to delete incomplete multipart uploads after 1 day.

5. Versioning: leave it off

We recommend no versioning. Every run uploads a full archive, and the newest backup of every repository is never deleted, whatever your retention setting says. Versioning on top of full archives multiplies your storage bill by the number of runs you keep, for a second copy of data you already have.

6. Connect it in Gitbackups

In Gitbackups, choose Wasabi as your storage. Here is each field in the form, and what Wasabi calls the value that goes in it.

  1. Region
    No label of its own

    The region you picked in step 1, as a code like eu-central-1. Wasabi’s list of service URLs shows each region’s code.

  2. Endpointoptional
    Service URL

    Leave it blank and we build https://s3.<region>.wasabisys.com, or paste the service URL Wasabi lists for your region.

  3. BucketrequiredThe name only. Not a URL.
    No label of its own

    What you named the bucket in step 1.

  4. Path prefixoptionalUse one if anything else writes to this bucket.
    No label of its own

    The folder in your step 3 policy, e.g. gitbackups/. Must match it exactly.

  5. Access key IDrequiredWe only ever show its last four characters.
    Access Key

    Shown when you create the key in step 2.

  6. Secret access keyrequiredEncrypted on arrival. Never shown again.
    Secret Key

    Behind Show on the same screen. Lost it? Create a new key.

Then press Test connection. Gitbackups writes a small file under your prefix, reads it back, deletes it, and starts and aborts one empty multipart upload. If a step is refused, the screen tells you which permission is missing.

Start backing up

Sign up for Gitbackups, install the GitHub App, and point it at your Wasabi bucket.

Setting up a different provider? AWS S3 · Cloudflare R2 · Backblaze B2 · MinIO and other S3-compatible storage