/// CONNECT A PROVIDER / CLOUDFLARE R2

Cloudflare R2

R2 is S3-compatible, so storafleet connects to it with access keys and a custom endpoint. The keys come from an R2 API token, and you supply your account id so storafleet can build the right endpoint.

Don't have a Cloudflare R2 bucket yet? Create one first →

R2 is connected with access keys — there's no keyless IAM Role path on Cloudflare.

The whole R2 connect flow end to end, about two minutes — Cloudflare token → Storafleet Create Fleet.

Create an R2 API token

In the Cloudflare dashboard, create an R2 API token. On the confirmation screen Cloudflare shows an Access Key ID and a Secret Access Key directly — copy both (the secret is shown only once) and paste them into the Access Keys path of the Create Fleet wizard. No hashing needed.

Cloudflare's token confirmation screen shows the Access Key ID and Secret Access Key right there — copy both now; the secret is shown only once.

Creating the token via Cloudflare's API rather than the dashboard? Then the Secret Access Key is the SHA-256 hash of the token value. The dashboard gives you the ready-to-use secret.

Endpoint and account id

You also need your Cloudflare account id and the R2 endpoint, which is https://<ACCOUNT_ID>.r2.cloudflarestorage.com. Enter that as the custom endpoint when connecting the Fleet.

Your account ID sits on the R2 Overview page (right-hand Account details) — it's the same value inside the endpoint URL.

In Storafleet's Create Fleet wizard, pick Cloudflare R2, then paste the endpoint, Access Key ID, and Secret Access Key, and the bucket name — Storafleet sets the region to auto for you. This is the step to nail; everything above just gathers these four values.

No versioning

R2 has no S3 versioning. Features in storafleet that depend on object versions are not available on an R2 Fleet.

Data residency

You can pin an R2 bucket to an EU or FedRAMP jurisdiction at creation time. When you do, the endpoint changes to include the jurisdiction — for example https://<ACCOUNT_ID>.eu.r2.cloudflarestorage.com. Use that jurisdiction-specific endpoint in the wizard.

See Data residency for more.

Fast-path migrations

The R2 fast paths — Super Slurper (bulk import) and Sippy (live migration) — additionally need a Cloudflare account API token, on top of the R2 API token used for the connection itself.

See the migration guide for when to reach for Super Slurper versus Sippy.

PreviousAmazon S3

NextBackblaze B2