Data location
Jurisdictions are used to create Durable Objects that only run and store data within a region to comply with local regulations such as the GDPR ↗ or FedRAMP ↗.
Workers may still access Durable Objects constrained to a jurisdiction from anywhere in the world. The jurisdiction constraint only controls where the Durable Object itself runs and persists data. Consider using Regional Services to control the regions from which Cloudflare responds to requests.
Durable Objects can be restricted to a specific jurisdiction either by creating a DurableObjectNamespace
restricted to a jurisdiction, or by creating an individual DurableObjectId
restricted to a jurisdiction:
Methods on a DurableObjectNamespace
that take a DurableObjectId
as a parameter will throw an exception if the parameter is associated with a different jurisdiction. To achieve this, a DurableObjectId
encodes its jurisdiction. As a consequence, it is possible to have the same name represent different IDs in different jurisdictions.
Methods on a DurableObjectNamespace
that take a DurableObjectId
as a parameter will throw an exception if the parameter is associated with a different jurisdiction. However, these methods will not throw an exception if the DurableObjectNamespace
is not associated with a jurisdiction. The common case is that any valid DurableObjectId
can be used in the top-level namespace's methods.
Parameter | Location |
---|---|
eu | The European Union |
fedramp | FedRAMP-compliant data centers |
Durable Objects, as with any stateful API, will often add response latency as requests must be forwarded to the data center where the Durable Object, or state, is located.
Durable Objects do not currently change locations after they are created1. By default, a Durable Object is instantiated in a data center close to where the initial get()
request is made. This may not be in the same data center that the get()
request is made from, but in most cases, it will be in close proximity.
Location hints are the mechanism provided to specify the location that a Durable Object should be located regardless of where the initial get()
request comes from.
To manually create Durable Objects in another location, provide an optional locationHint
parameter to get()
. Only the first call to get()
for a particular Object will respect the hint.
Parameter | Location |
---|---|
wnam | Western North America |
enam | Eastern North America |
sam | South America 2 |
weur | Western Europe |
eeur | Eastern Europe |
apac | Asia-Pacific |
oc | Oceania |
afr | Africa 2 |
me | Middle East 2 |
1 Dynamic relocation of existing Durable Objects is planned for the future.
2 Durable Objects currently do not spawn in this location. Instead, the Durable Object will spawn in a nearby location which does support Durable Objects. For example, Durable Objects hinted to South America spawn in Eastern North America instead.