|
1 | 1 | ---
|
2 | 2 | title: Data Residency
|
3 | 3 | ---
|
4 |
| -Segment offers customers the option to mitigate risk by providing regional infrastructure across Europe, Middle East, Africa and Asia Pacific. The default region for all customers is United States (Oregon). The regional infrastructure has the same [rate limits and SLA](/docs/connections/rate-limits/) as the default region. |
| 4 | +Segment offers customers the option to mitigate risk by providing regional infrastructure across Europe, Middle East, Africa and Asia Pacific. The default region for all customers is in Oregon, United States. The regional infrastructure has the same [rate limits and SLA](/docs/connections/rate-limits/) as the default region. |
5 | 5 |
|
6 |
| -If your workspace is enabled to support regional services, you can select on the region on a per-source basis in that Source's settings. |
| 6 | +## Agree to Terms |
7 | 7 |
|
8 |
| - |
| 8 | +> note "" |
| 9 | +> This feature is in Public Preview. |
9 | 10 |
|
10 |
| -All Segment client-side libraries dynamically read your preferred region when the SDK is loaded when your app starts or restarts. Changing regions does not require changes to your code when you change regions. |
| 11 | +Before you can enable Regional Data Ingest and Storage on your workspace, you must read and agree to the [First Access and Beta Terms and Conditions](https://segment.com/legal/first-access-beta-preview/) and [Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/). |
11 | 12 |
|
12 |
| -For server-side routing, you can view endpoint details in the source's settings, and use the [`host`](https://github.com/segmentio/analytics-python/blob/c9f5ba6b58813eba1c3e5c778b0fc8d86f937f55/analytics/__init__.py#L9) configuration parameter to send data to the desired region. |
| 13 | +Once agreed to, click **Accept Terms** to enable the feature on your active workspace. |
13 | 14 |
|
14 |
| -Regional infrastructure can failover across locations within the region, but does not failover across regions. |
| 15 | + |
15 | 16 |
|
16 |
| -## Local data storage |
| 17 | +## Enable Regional Data Ingest |
17 | 18 |
|
| 19 | +Regional Data Ingest enables you to send data to segment from either Client-side or Server-side sources, through locally hosted API ingest points. The regional infrastructure has the capability to fail-over across locations within the region, but will not cross regions. |
| 20 | + |
| 21 | +### Client-side Sources |
| 22 | + |
| 23 | +You can configure Segment's client-side SDKs for Javascript, iOS, Android, and React Native sources to send data to a regional host by selecting the ingest region on a per-source basis. |
| 24 | + |
| 25 | + |
18 | 26 |
|
19 |
| -<!-- we need to add a section on Local Data Storage which outlines how customers can setup regional buckets so that their events are archived within the region. This will also need to include SLA and process details around replays and deletions as well as some caveats like: we cannot guarantee a replay if the customer tweaks the data in their bucket --> |
|
0 commit comments