Oracle OCI Object Storage

OCI's object storage via its S3-compatibility endpoint. It is S3-compatible, which means blitcp supports it out of the box: pick the oracle 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://<namespace>.compat.objectstorage.<region>.oraclecloud.com
The namespace is on the tenancy details page; regions like eu-frankfurt-1. Region: The OCI region identifier from the endpoint.

Where the keys come from

OCI console → your user → Customer Secret Keys → Generate Secret Key.

Set it up once

$ blitcp creds add myoracle
  Type [s3/azure/gcs/ssh/smb — or a preset: r2/b2/wasabi/…]: oracle
  Oracle OCI Object Storage — S3-compatible. Keys: …
  Namespace: your-namespace
  Region: your-region
  Endpoint: https://….compat.objectstorage.….oraclecloud.com
  Access key ID: ********
  Secret access key: ********
  Default bucket (blank = none): backups

Then copy

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

Use the S3-compat endpoint above — the native OCI endpoint speaks a different API.

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