Cloudflare R2 jurisdiction is permanent and needs its own endpoint

Not specified by the original author.

TL;DR

When you use a jurisdiction, point every client at the jurisdiction-specific endpoint, never the account-wide one, or you will chase a phantom missing bucket. Decide jurisdiction before you create the bucket, there is no edit path later, only create-new-and-migrate.

Steps

1. Decide jurisdiction before you create the bucket, there is no edit path later, only create-new-and-migrate. When you use a jurisdiction, point every client at the jurisdiction-specific endpoint, never the account-wide one, or you will chase a phantom missing bucket. In Workers, the binding needs the jurisdiction field too, wrangler.toml r2buckets entries take a jurisdiction key alongside bucketname.

When to use

You are seeing this: Decide jurisdiction before you create the bucket, there is no edit path later, only create-new-and-migrate. Use this skill when you run into "Cloudflare R2 jurisdiction is permanent and needs its own endpoint".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://YOUR-account-id.eu.r2.cloudflarestorage.com

Source: Official docs (Cloudflare R2, Data location): a bucket's jurisdiction is fixed at creation and cannot be changed afterward. Jurisdiction is also not the same as a location hint: hints are best-effort placement, jurisdictions (eu, fedramp, us) enforce data residency. A second trap sits next to it: buckets with a jurisdiction only answer on their jurisdiction endpoint, like https://YOUR-account-id.eu.r2.cloudflarestorage.com, and the account-wide endpoint reports the bucket as missing.

Verified resolution: Decide jurisdiction before you create the bucket, there is no edit path later, only create-new-and-migrate. When you use a jurisdiction, point every client at the jurisdiction-specific endpoint, never the account-wide one, or you will chase a phantom missing bucket. In Workers, the binding needs the jurisdiction field too, wrangler.toml r2buckets entries take a jurisdiction key alongside bucketname.

Source URL: https://developers.cloudflare.com/r2/reference/data-location/