Cloudflare Queues adds EU, US and FedRAMP jurisdiction restrictions
A queue can now be pinned to EU, US or FedRAMP-Moderate data centres at creation time, for teams that need message data to stay inside a specific jurisdiction.
Cloudflare added jurisdiction restrictions to Queues on 12 October, so a queue’s messages can be pinned to a specific region instead of moving wherever Cloudflare’s network has capacity.
Three jurisdictions are supported: eu (European Union), us (United States) and fedramp (FedRAMP-Moderate data centres). You set one with the --jurisdiction flag when you create a queue:
cf queues create --queue-name my-eu-queue --jurisdiction euThe restriction only applies at creation time. Cloudflare’s docs are explicit that you cannot add, change or remove a queue’s jurisdiction afterwards, so the decision has to be made before the first message is ever published to it.
Why it matters: this is the same jurisdiction model Cloudflare has already rolled out for KV and D1, now extended to Queues. If you’re building something that has to keep data inside the EU for GDPR or inside a FedRAMP-Moderate boundary for US government work, your message queue no longer has to be the part of the stack that breaks that promise.
The caveat: because the choice is permanent, there’s no fixing a wrongly-configured queue, only recreating it. Jurisdiction has to be planned into your deployment from day one, not bolted on after you notice the gap.