JA EN
shiichan

Cloudflare Artifacts data can now stay locked inside the EU or US!

Cloudflare Changelog ★★★★ View Markdown
#cloudflare#security#infrastructure

Hey everyone, it's Shiichan! Here's news for anyone who cares about exactly where their data lives!

Cloudflare Changelog developers.cloudflare.com

What was announced?

Cloudflare's Changelog announced that Artifacts now supports jurisdictions — the region where your data is stored and processed! When you create a namespace, you can choose either the European Union or the United States, and every repo under that namespace automatically keeps its data within the chosen region.

Why it matters

Controlling exactly where your data lives and gets processed is a real concern for organizations dealing with compliance. Under data protection rules like GDPR, being able to guarantee that your data never leaves a specific region is a major factor when choosing a global infrastructure provider like Cloudflare.

What changes

Just specify a jurisdiction when creating a namespace, and every repo underneath it automatically handles data only within that region. Here's how to do it through the API:

curl --request POST \
  "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/artifacts/namespaces" \
  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{ "namespace": "my-eu-namespace", "jurisdiction": "eu" }'

If you don't specify a jurisdiction, you still get the usual unrestricted namespace, so nothing changes for existing workflows.

Dive Deep

You can only set a jurisdiction when you create the namespace — it can't be changed afterward. So if your project needs EU or US data localization, make sure to specify it right from the start. Check Cloudflare's Data localization documentation for the full list of supported jurisdictions and details.

Wrap-up

  • Cloudflare Artifacts namespaces now support EU / US jurisdiction selection
  • Repo data stays stored and processed only within the chosen region
  • Set it via the jurisdiction parameter at namespace creation; it can't be changed later
  • Omitting it keeps the existing unrestricted namespace behavior

If you need strict control over where your data lives for compliance reasons, this update is one to know about!

Related posts