R2 adds US jurisdiction for data residency
R2 now supports a US jurisdiction option that guarantees bucket data is stored and processed within the United States, available via a jurisdiction-specific S3 endpoint and configurable in Workers R2 bindings.
R2 now supports a us jurisdiction, which guarantees that bucket data is stored and processed within the United States. Use this jurisdiction when you need explicit US data residency guarantees.
Use the jurisdiction-specific S3 endpoint to create and access buckets in the us jurisdiction:
https://<ACCOUNT_ID>.us.r2.cloudflarestorage.com
To access a bucket in the us jurisdiction from Workers, set jurisdiction in your R2 binding:
{
"r2_buckets": [
{
"binding": "MY_BUCKET",
"bucket_name": "<YOUR_BUCKET_NAME>",
"jurisdiction": "us"
}
]
}[[r2_buckets]]
binding = "MY_BUCKET"
bucket_name = "<YOUR_BUCKET_NAME>"
jurisdiction = "us"
Once an R2 bucket is created, its jurisdiction cannot be changed.
For setup instructions and the full list of supported jurisdictions, refer to R2 data location.
Source: original entry ↗
More from Cloudflare
Follow Cloudflare to get its new changes in your feed and email digest.
Cloudflare API MCP server now serves Cloudflare skills
The Cloudflare API MCP server now integrates with the Skills over MCP extension, allowing MCP clients to discover and access Cloudflare skills. Users can add the MCP server endpoint to compatible MCP clients to access these skills.
WAF failed detections field now available in Rules
A new cf.appsec.request.failed_detections field lets you control how rules handle requests when security detections fail. This array of detection IDs covers content scanning, WAF attack scoring, attack signatures, leaked credentials, and AI-based PII/prompt injection/custom topic detection failures, and works across custom rules, rate limiting rules, and request header transform rules.
Markdown for Agents: More efficient in-process streaming conversion
Markdown for Agents now uses an in-process streaming engine at the edge to convert HTML, reducing overhead and memory use. The conversion limit increased from 2 MiB to 6 MiB, and token count headers are no longer generated.