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
@@ -81,9 +83,10 @@ The table below provides a summary of the Data Localization Suite product's beha
81
83
| Argo Smart Routing | ✅ | ✘ [^9]| ✘ [^10]|
82
84
| Static IP/BYOIP | ⚫️ | ✅ [^26]| ⚫️ |
83
85
| Magic Firewall | ⚫️ | ⚫️ | ✅ |
86
+
| Magic Network Monitoring | ⚫️ | ⚫️ | 🚧 [^1]|
84
87
| Magic Transit | ⚫️ | ⚫️ | 🚧 [^1]|
85
88
| Magic WAN | ⚫️ | ⚫️ | ✅ |
86
-
| Spectrum | ✅ | ✅ | ✅ |
89
+
| Spectrum | ✅ | ✅ [^42]| ✅ |
87
90
88
91
***
89
92
@@ -112,7 +115,7 @@ The table below provides a summary of the Data Localization Suite product's beha
112
115
[^1]: Logs / Analytics not available outside US region when using Customer Metadata Boundary.
113
116
[^2]: Regular and Custom Tiered Cache works; Smart Tiered Caching not available with Regional Services.
114
117
[^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.
116
119
[^5]: Some advanced Enterprise features, including the [Anomaly Detection engine](/bots/concepts/bot-score/#anomaly-detection), are not available.
117
120
[^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.
118
121
[^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
126
129
[^15]: Can be localized to US FedRAMP region only. More regions coming in 2024.
127
130
[^16]: Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region.
128
131
[^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.
130
133
[^19]: Uses Gateway HTTP and CASB.
131
134
[^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.
132
135
[^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
142
145
[^34]: Jurisdictional Restrictions (storage) for Workers KV pairs is not supported today.
143
146
[^35]: Logs / Analytics not available outside US region when using Customer Metadata Boundary. Jurisdictional Restrictions (storage) options are not supported today.
144
147
[^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.
Copy file name to clipboardExpand all lines: src/content/docs/data-localization/metadata-boundary/get-started.mdx
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,11 @@ To configure Customer Metadata Boundary in the dashboard:
22
22
23
23
## Configure Customer Metadata Boundary via API
24
24
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.
Copy file name to clipboardExpand all lines: src/content/docs/data-localization/regional-services/get-started.mdx
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,8 +75,11 @@ Refer to the table below for the complete list of available regions and their de
75
75
76
76
## Configure Regional Services via API
77
77
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.
79
79
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.
0 commit comments