Skip to content

Commit a32a1b4

Browse files
committed
DLS updates
1 parent fa17031 commit a32a1b4

File tree

3 files changed

+28
-12
lines changed

3 files changed

+28
-12
lines changed

src/content/docs/data-localization/compatibility.mdx

Lines changed: 19 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -42,14 +42,14 @@ The table below provides a summary of the Data Localization Suite product's beha
4242
| ---------------------------- | --------------- | ----------------- | -------------------------- |
4343
| Advanced Certificate Manager | ⚫️ | ⚫️ | ⚫️ |
4444
| Advanced DDoS Protection ||| 🚧 [^3] |
45-
| API Shield ||| [^4] |
45+
| API Shield ||| 🚧 [^4] |
4646
| Bot Management ||| 🚧 [^5] |
47-
| DNS Firewall | ⚫️ | ⚫️ | 🚧 [^1] |
47+
| DNS Firewall | ⚫️ | ⚫️ | 🚧 [^22] |
4848
| Page Shield ||||
49-
| Rate Limiting ||| 🚧 [^1] |
49+
| Rate Limiting ||| [^37] |
5050
| SSL ||||
5151
| Cloudflare for SaaS ||||
52-
| Turnstile | ⚫️ |||
52+
| Turnstile | ⚫️ ||[^38] |
5353
| WAF/L7 Firewall ||||
5454
| DMARC Management | ⚫️ | ⚫️ ||
5555

@@ -60,17 +60,19 @@ The table below provides a summary of the Data Localization Suite product's beha
6060
| Product | Geo Key Manager | Regional Services | Customer Metadata Boundary |
6161
| ---------------------------- | --------------- | ----------------- | -------------------------- |
6262
| Cloudflare Images | ⚫️ |[^36] | 🚧 [^35] |
63-
| Cloudflare Pages ||[^11] | 🚧 [^1] |
63+
| AI Gateway ||| 🚧 [^39] |
64+
| Cloudflare Pages |[^11] |[^11] | 🚧 [^1] |
65+
| Cloudflare D1 | ⚫️ | ⚫️ | 🚧 [^40] |
6466
| Durable Objects | ⚫️ |[^7] | 🚧 [^1] |
6567
| Email Routing | ⚫️ | ⚫️ ||
6668
| R2 |[^27] |[^8] |[^28] |
6769
| Smart Placement | ⚫️ |||
6870
| Stream | ⚫️ || 🚧 [^1] |
69-
| Workers (deployed on a Zone) ||| 🚧 [^1] |
71+
| Workers (deployed on a Zone) ||| 🚧 [^41] |
7072
| Workers AI | ⚫️ |||
7173
| Workers KV | ⚫️ ||[^34] |
7274
| Workers.dev ||||
73-
75+
| Workers Analytics Engine (WAE) | ⚫️ | ⚫️ | 🚧 [^1] |
7476

7577
***
7678

@@ -81,9 +83,10 @@ The table below provides a summary of the Data Localization Suite product's beha
8183
| Argo Smart Routing ||[^9] |[^10] |
8284
| Static IP/BYOIP | ⚫️ |[^26] | ⚫️ |
8385
| Magic Firewall | ⚫️ | ⚫️ ||
86+
| Magic Network Monitoring | ⚫️ | ⚫️ | 🚧 [^1] |
8487
| Magic Transit | ⚫️ | ⚫️ | 🚧 [^1] |
8588
| Magic WAN | ⚫️ | ⚫️ ||
86-
| Spectrum || ||
89+
| Spectrum ||[^42] ||
8790

8891
***
8992

@@ -112,7 +115,7 @@ The table below provides a summary of the Data Localization Suite product's beha
112115
[^1]: Logs / Analytics not available outside US region when using Customer Metadata Boundary.
113116
[^2]: Regular and Custom Tiered Cache works; Smart Tiered Caching not available with Regional Services.
114117
[^3]: Adaptive DDoS Protection is only supported for US CMB.
115-
[^4]: API shield will not yet work with Customer Metadata Boundary enabled outside of US region.
118+
[^4]: Features such as API Discovery and Volumetric Abuse Detection will not work with CMB set to EU only.
116119
[^5]: Some advanced Enterprise features, including the [Anomaly Detection engine](/bots/concepts/bot-score/#anomaly-detection), are not available.
117120
[^6]: Only when using a Custom Domain set to a region, either through Workers or [Transform Rules](/images/transform-images/serve-images-custom-paths/) within the same zone.
118121
[^7]: [Jurisdiction restrictions for Durable Objects](/durable-objects/reference/data-location/#restrict-durable-objects-to-a-jurisdiction).
@@ -126,7 +129,7 @@ The table below provides a summary of the Data Localization Suite product's beha
126129
[^15]: Can be localized to US FedRAMP region only. More regions coming in 2024.
127130
[^16]: Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region.
128131
[^17]: Currently may only be used with US FedRAMP region.
129-
[^18]: Only US FedRAMP region.
132+
[^18]: The only connectivity option is [US FedRAMP region](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters/#region). Regional Services only applies when using [Public Hostnames](/cloudflare-one/connections/connect-networks/routing-to-tunnel/) set to a region.
130133
[^19]: Uses Gateway HTTP and CASB.
131134
[^20]: You can [bring your own certificate](https://blog.cloudflare.com/bring-your-certificates-cloudflare-gateway/) to Gateway but these cannot yet be restricted to a specific region.
132135
[^21]: Gateway HTTP supports Regional Services. Gateway DNS does not yet support regionalization. <br/> ICMP proxy and WARP-to-WARP proxy are not available to Regional Services users.
@@ -142,3 +145,9 @@ The table below provides a summary of the Data Localization Suite product's beha
142145
[^34]: Jurisdictional Restrictions (storage) for Workers KV pairs is not supported today.
143146
[^35]: Logs / Analytics not available outside US region when using Customer Metadata Boundary. Jurisdictional Restrictions (storage) options are not supported today.
144147
[^36]: Only when using a [Custom Domain](/images/manage-images/serve-images/serve-from-custom-domains/) set to a region.
148+
[^37]: Legacy Zone Analytics & Logs section not available outside US region when using CMB. Use [Security Analytics](/waf/analytics/security-analytics/) instead.
149+
[^38]: [Turnstile Analytics](/turnstile/turnstile-analytics/) are available. However, there are no regionalization guarantees for the Siteverify API yet.
150+
[^39]: Jurisdictional Restrictions (storage) options for [Logs](/ai-gateway/observability/logging/) are not supported today.
151+
[^40]: Jurisdictional Restrictions ([data location](/d1/configuration/data-location/) / storage) options are not supported today.
152+
[^41]: Logs / Analytics not available outside US region when using Customer Metadata Boundary. Use Logpush instead.
153+
[^42]: Only applies to HTTP/S Spectrum applications.

src/content/docs/data-localization/metadata-boundary/get-started.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,11 @@ To configure Customer Metadata Boundary in the dashboard:
2222

2323
## Configure Customer Metadata Boundary via API
2424

25-
You can also configure Customer Metadata Boundary via API. These are some examples of API requests.
25+
You can also configure Customer Metadata Boundary via API.
26+
27+
Currently, only SuperAdmins and Admin roles can edit DLS configurations. Use the **Account-level Logs:Read/Write** API permissions for the `/logs/control/cmb` endpoint to read/write Customer Metadata Boundary configurations.
28+
29+
These are some examples of API requests.
2630

2731

2832
<Details header="Get current regions">

src/content/docs/data-localization/regional-services/get-started.mdx

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,8 +75,11 @@ Refer to the table below for the complete list of available regions and their de
7575

7676
## Configure Regional Services via API
7777

78-
You can also use Regional Services via API. These are some examples of API requests.
78+
You can also use Regional Services via API.
7979

80+
Currently, only SuperAdmins and Admin roles can edit DLS configurations. Use the Zone-level **DNS: Read/Write** API permission for the `/addressing/` endpoint to read or write Regional Services configurations.
81+
82+
These are some examples of API requests.
8083

8184
<Details header="List all the available regions">
8285

0 commit comments

Comments
 (0)