DigitalOcean Spaces

Simple S3-compatible object storage in DigitalOcean regions. It is S3-compatible, which means blitcp supports it out of the box: pick the spaces 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://<region>.digitaloceanspaces.com
Regions like nyc3, ams3, sgp1, fra1. Region: The datacenter slug from the endpoint (e.g. nyc3).

Where the keys come from

DigitalOcean control panel → API → Spaces Keys → Generate New Key.

Set it up once

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

Then copy

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

Spaces bundles a CDN; blitcp talks to the origin endpoint.

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