You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: D1 now supports jurisdictional restrictions.
3
-
description: D1 now has the capability to set jurisdictional restrictions on database creation. This restricts the location to run and store the d1 database.
3
+
description: D1 can now set jurisdictional restrictions on database creation. This restricts the location of where the D1 database is run and stored.
4
4
products:
5
5
- d1
6
6
- workers
7
7
date: 2025-09-11
8
8
---
9
9
10
-
You can now set a [jurisdiction](/d1/configuration/data-location/) when creating a D1 database. Note that if a jurisdiction restriction and a location hint are both provided, the jurisdiction takes precedence and the location hint is ignored.
10
+
You can now set a [jurisdiction](/d1/configuration/data-location/) when creating a D1 database.
11
+
12
+
Note that if a jurisdiction restriction and a location hint are both provided, the jurisdiction takes precedence, and the location hint is ignored.
Copy file name to clipboardExpand all lines: src/content/docs/d1/configuration/data-location.mdx
+8-18Lines changed: 8 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,12 +19,12 @@ Jurisdictions are used to create D1 databases that only run and store data withi
19
19
20
20
Workers may still access the database constrained to a jurisdiction from anywhere in the world. The jurisdiction constraint only controls where the database itself runs and persists data. Consider using [Regional Services](/data-localization/regional-services/) to control the regions from which Cloudflare responds to requests.
21
21
22
-
### Supported locations
22
+
### Available jurisdictions
23
23
24
-
|Parameter|Location |
25
-
| ---------|------------------------------ |
26
-
| eu | The European Union |
27
-
| fedramp | FedRAMP-compliant data centers|
24
+
|Jurisdiction|Jurisdiction description|
25
+
| ------------|------------------------ |
26
+
| eu | European Union|
27
+
| fedramp | FedRAMP|
28
28
29
29
### Set jurisdiction via the Cloudflare dashboard
30
30
@@ -37,15 +37,15 @@ Workers may still access the database constrained to a jurisdiction from anywher
37
37
4. Under **Data location**, select **Specify jurisdiction** and choose a jurisdiction from the list.
38
38
5. Select **Create** to complete the database creation process.
39
39
40
-
### Using jurisdictions from Workers
40
+
### Use jurisdictions from Wrangler
41
41
42
-
The example below shows how to create an R2 bucket in the `eu` jurisdiction using Wrangler
42
+
The example below shows how to create an R2 bucket in the `eu` jurisdiction using Wrangler:
43
43
44
44
```sh
45
45
npx wrangler@latest d1 create d1-with-jurisdiction --jurisdiction eu
46
46
```
47
47
48
-
### Using jurisdictions from the REST API
48
+
### Use jurisdictions from the REST API
49
49
50
50
```curl
51
51
curl -X POST "https://api.cloudflare.com/client/v4/accounts/<account_id>/d1/database" \
@@ -55,17 +55,7 @@ curl -X POST "https://api.cloudflare.com/client/v4/accounts/<account_id>/d1/data
55
55
56
56
```
57
57
58
-
### Available jurisdictions
59
-
60
-
The following jurisdictions are supported:
61
-
62
-
| Jurisdiction | Jurisdiction description |
63
-
| ------------ | ------------------------ |
64
-
| eu | European Union |
65
-
| fedramp | FedRAMP |
66
-
67
58
:::note
68
-
69
59
Note that jurisdiction restrictions can only be set on database creation. If a jurisdiction and a location hint are both provided, the jurisdiction takes precedence and the location hint is ignored.
0 commit comments