StorafleetStorafleet
Log inStart for free

/// CREATE A BUCKET / CLOUDFLARE R2

Create a Cloudflare R2 Bucket

Coming from S3 to cut your egress bill? R2 charges zero egress fees — you pay for storage and operations, not for data leaving the bucket. Stand up an R2 bucket here, then connect it to storafleet and migrate your objects across with Cloudflare's Sippy and Super Slurper.

R2 speaks the S3 API, so storafleet connects to it exactly like any S3-compatible provider — an Access Key ID, a Secret Access Key, and a custom endpoint. You will create all three below.
The full create-and-connect flow start to finish (~3 min) — enable R2 → create the bucket → mint the token → connect it to Storafleet.

Create a Cloudflare account / enable R2

R2 lives in your Cloudflare account. If you do not have one, sign up at dash.cloudflare.com, then enable R2:

  1. In the dashboard, go to Storage & databases → R2 → Overview.
  2. The first time you open R2 you complete a short checkout to add an R2 subscription to the account. R2 is free to get started with included monthly usage; you only pay for storage and operations above the free tier.
The R2 Overview page. First time in, Cloudflare walks you through a short (free) subscription checkout to turn R2 on.

See Cloudflare's Get started with R2 guide for the current signup flow.

Create an R2 bucket

From the R2 Overview page:

  1. Click Create bucket.
  2. Enter a bucket name. This is the name storafleet will use as the bucket for the Fleet.
  3. Under Location, leave it on automatic to let Cloudflare pick a region, or pick a location hint to bias placement near your users.
  4. Click Create bucket to finish.
The Create bucket dialog — give it a name and leave Location on automatic unless you need data residency.
Need data residency? Under Location you can choose Specify jurisdiction and pick European Union (EU) or FedRAMP (Enterprise only — contact Cloudflare Support for access). Jurisdiction-restricted buckets use their own endpoints and cannot be changed after creation. See Cloudflare's data location reference.

Create an R2 API token

R2's S3 credentials come from an API token. In the dashboard, open R2 → Overview, find API Tokens in the Account details panel, and click Manage API tokens:

  1. Click Create API token (choose an Account API token for a token tied to the account, or a User API token tied to your user).
  2. Set Permissions to Object Read & Write — storafleet reads, writes, lists, and deletes objects, but does not need to create or delete buckets.
  3. Optionally restrict the token to specific buckets (the one you just created), then create the token.

When you create the token in the dashboard, Cloudflare shows the two S3 credentials directly on the confirmation screen:

  • an Access Key ID, and
  • a Secret Access Key — paste this straight into Storafleet (no hashing needed).
The token confirmation screen. Copy the Access Key ID and Secret Access Key now — the secret is shown only once.
The Secret Access Key is shown only once. Copy both values now — you will not be able to view the secret again afterward.

(Only if you mint a token through the Cloudflare API instead of the dashboard is the Secret Access Key the SHA-256 hash of the token value — the dashboard hands you the ready-to-use secret.) See Cloudflare's R2 API tokens docs.

Find your endpoint & account ID

R2 exposes an S3-compatible endpoint scoped to your account:

  • https://<ACCOUNT_ID>.r2.cloudflarestorage.com
The S3 API endpoint and your account ID both live on the R2 Overview page — copy the endpoint exactly.

Your account ID is shown on the R2 Overview page and on the Create API token confirmation screen — it is the same value embedded in the endpoint above. For jurisdiction buckets, use the matching endpoint: https://<ACCOUNT_ID>.eu.r2.cloudflarestorage.com (EU) or https://<ACCOUNT_ID>.fedramp.r2.cloudflarestorage.com (FedRAMP).

R2 ignores the S3 region — S3 clients use auto. storafleet handles this for you when you pick R2 as the provider.

See Cloudflare's S3 API get started guide for the endpoint and credential details.

Connect it to storafleet

Screenshot: Storafleet's Create Fleet wizard with this provider selected and the endpoint + keys filled in — the step that unsticks a first-timer.

You now have everything storafleet needs: the bucket name, the S3 endpoint, the Access Key ID, and the Secret Access Key. Head to Connect R2 to storafleet to create the Fleet — storafleet encrypts your keys at rest exactly as it does for AWS access keys.

Storafleet's Create Fleet wizard with R2 selected — paste the endpoint and the two keys, name the Fleet, and connect. Storafleet verifies the credentials before saving.

Escaping an AWS bill? That is the whole point — see Migrate off AWS for the cost case, and the migration guide for moving your objects into R2 with Sippy and Super Slurper.

PreviousAmazon S3
NextBackblaze B2