R2 gets a new `us` jurisdiction, so you can now keep your data locked inside the United States!

Hello, it's Shii! Today I found some good storage-related news on the Cloudflare Changelog, so let me share it with you!

Cloudflare Changelog developers.cloudflare.com

What was announced?

On the Cloudflare Changelog, R2 announced support for a new us jurisdiction. With it, you can guarantee that a bucket's data is stored and processed only within the United States, an option for when you're explicitly required to keep data resident in the US.

The story so far

By default, R2 buckets are created with "Automatic" placement, landing in whichever region is closest to the caller if you don't specify one. If you wanted to explicitly restrict where data lives, there was already an eu jurisdiction, plus a fedramp jurisdiction for Cloudflare Enterprise customers, but there wasn't yet an option to keep things inside the US alone. Now us fills that gap.

What changes

For teams that need to satisfy US data residency requirements, whether from regulations like GDPR-style rules or from contracts with partners, you can now just specify the us jurisdiction when creating a bucket to lock its data inside the United States. Cases that used to require building your own region-control logic can now be satisfied with an R2 setting alone.

Dive Deep

Buckets in the us jurisdiction are accessed through a dedicated S3 endpoint.

https://{ACCOUNT_ID}.us.r2.cloudflarestorage.com

From Workers, just set jurisdiction on your R2 binding. In JSON format, it looks like this.

{
  "r2_buckets": [
    {
      "binding": "MY_BUCKET",
      "bucket_name": "{YOUR_BUCKET_NAME}",
      "jurisdiction": "us"
    }
  ]
}

In TOML format, you can write it like this.

[[r2_buckets]]
binding = "MY_BUCKET"
bucket_name = "{YOUR_BUCKET_NAME}"
jurisdiction = "us"

One thing worth noting: once a bucket is created, its jurisdiction can't be changed. If your project needs US data residency, make sure to specify us right when you first create the bucket. For full setup details and the list of supported jurisdictions, check the R2 data location docs against your own compliance requirements.

Wrap-up

• R2 now supports a new us jurisdiction, letting data be stored and processed only within the United States
• It joins the existing eu jurisdiction and the Enterprise-only fedramp jurisdiction as a new option
• Set it via the dedicated S3 endpoint or the jurisdiction parameter on a Workers binding
• The jurisdiction can't be changed after bucket creation, so specify it up front

This is an update worth knowing about if you're on a compliance team or using R2 and need to keep data resident in the US!