JA EN
shiichan

Restrict Cloudflare Workflows to the eu, us, or fedramp jurisdiction

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

Hi everyone, it's Shii-chan!

Cloudflare Changelog developers.cloudflare.com

Good news for anyone who cares where their data lives!

What was announced?

According to the Cloudflare Changelog, you can now restrict a Workflow to a jurisdiction.

Its instances only run and store data within that jurisdiction, which helps you comply with data localization regulations such as GDPR or FedRAMP.

What changes

Workflows become easier to adopt in regulated industries and regions, because you can constrain where they run and store data through configuration alone.

Dive Deep

You set it in your Wrangler config: put jurisdiction on a workflows binding, or on a Workflow declared in exports.

[[ workflows ]]
name = "my-workflow"
binding = "MY_WORKFLOW"
class_name = "MyWorkflow"
jurisdiction = "eu"

Supported jurisdictions:

  • eu: the European Union
  • us: the United States
  • fedramp: FedRAMP-Moderate data centers

Things to keep in mind:

  • A Workflow's jurisdiction is set when it is created and cannot be changed afterwards
  • If an existing Workflow has a different jurisdiction, wrangler deploy and wrangler versions upload stop before uploading your Worker
  • Wrangler 4.152.0 or above is required

See Data location in the docs for more.

Wrap-up

  • Restrict a Workflow to eu, us, or fedramp
  • Both execution and data storage stay within the jurisdiction
  • Can't be changed after creation; needs Wrangler 4.152.0 or above

This is for anyone who needs Workflows under data residency requirements!

Related posts