IDrive e2

S3-compatible storage with per-account regional endpoints. It is S3-compatible, which means blitcp supports it out of the box: pick the idrive 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

shown in your IDrive e2 dashboard (per region)
e2 endpoints are per-account — copy the exact endpoint string from the dashboard; the preset asks for it verbatim. Region: Not needed — the endpoint encodes it.

Where the keys come from

IDrive e2 dashboard → Access Keys → Create Access Key.

Set it up once

$ blitcp creds add myidrive
  Type [s3/azure/gcs/ssh/smb — or a preset: r2/b2/wasabi/…]: idrive
  IDrive e2 — S3-compatible. Keys: …
  Endpoint: https://…copied-from-dashboard…
  Endpoint: shown in your IDrive e2 dashboard (per region)
  Access key ID: ********
  Secret access key: ********
  Default bucket (blank = none): backups

Then copy

blitcp ~/photos myidrive:backups/photos          # upload, dedup + verify on
blitcp myidrive: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

Buckets are region-bound; create the bucket in the same region as the endpoint you saved.

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