Wasabi backups

Flat-rate hot cloud storage, S3-compatible, no egress charges. It is S3-compatible, which means blitcp supports it out of the box: pick the wasabi preset in creds add, paste your keys, and every transfer gets blitcp's usual treatment — content-hash deduplication before upload, verified writes after, and incremental re-runs that skip unchanged files.

Endpoint

https://s3.<region>.wasabisys.com
Regions like us-east-1, eu-central-1, ap-northeast-1. Region: Same value as in the endpoint.

Where the keys come from

Wasabi console → Access Keys → Create New Access Key.

Set it up once

$ blitcp creds add mywasabi
  Type [s3/azure/gcs/ssh/smb — or a preset: r2/b2/wasabi/…]: wasabi
  Wasabi — S3-compatible. Keys: …
  Region: your-region
  Endpoint: https://s3.….wasabisys.com
  Access key ID: ********
  Secret access key: ********
  Default bucket (blank = none): backups

Then copy

blitcp ~/photos mywasabi:backups/photos          # upload, dedup + verify on
blitcp mywasabi:backups/photos ~/restore     # download

Re-running the same upload only transfers new or changed files. Duplicate content inside the tree is uploaded once. Credentials live in blitcp's AES-256-GCM encrypted credentials file — see the cloud storage guide for the full creds manager.

Notes

Wasabi bills a 90-day minimum retention per object — fine for backups, mind it for fast-churning trees.

Also supported: Cloudflare R2 · Backblaze B2 · DigitalOcean Spaces · Scaleway Object Storage · Hetzner Object Storage · IDrive e2 · Storj · Oracle OCI Object Storage · iCloud Drive