JA EN
shiichan

Cloudflare Queues Now Supports EU, US, and FedRAMP Jurisdictions

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

Hi everyone, it's Shii-chan!

Cloudflare Changelog developers.cloudflare.com

Here's a nice update for teams that care about where their data lives!

What was announced?

The Cloudflare Changelog says Cloudflare Queues now supports jurisdictional restrictions. Messages published to a queue are stored and processed only within a specific jurisdiction, which helps with data residency requirements such as GDPR or FedRAMP.

What changes

There are three supported jurisdictions:

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

Dive Deep

With the Cloudflare CLI (cf), use the --jurisdiction flag.

cf queues create --queue-name my-eu-queue --jurisdiction eu

With the API, pass a jurisdiction parameter to the Create Queue endpoint.

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

This part matters: the jurisdiction can only be set when the queue is created and cannot be changed afterwards, so decide before you create it. See the Queues data location docs for more.

Wrap-up

  • Queue messages can be restricted to a specific jurisdiction
  • Choose from eu, us, and fedramp
  • Set it with --jurisdiction in the CLI or jurisdiction in the API
  • Creation-time only; it can't be changed later

If your system has data location requirements, this one's for you!

Related posts