Skip to content

Commit 661d373

Browse files
committed
DOC-192 Vinod comments
1 parent 73c7e0b commit 661d373

File tree

2 files changed

+16
-8
lines changed

2 files changed

+16
-8
lines changed

src/_data/products.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,3 +114,11 @@ items:
114114
team: false
115115
business: true
116116
add-on: true
117+
- product_display_name: Data Residency
118+
slug: data-residency
119+
plan-note: "Data residency is available to customers on the Business Tier plan"
120+
plans:
121+
free: false
122+
team: false
123+
business: true
124+
add-on: false

src/connections/data-residency.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,31 @@
11
---
22
title: Data Residency
3-
beta: true
43
---
4+
{% include content/plan-grid.md name="data-residency" %}
55

66

77

88

99
Segment offers customers the option to lead on data residency 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.
1010

11-
## Enable Regional Data Ingest and Storage
11+
## Enable Regional Data Ingestion and Storage
1212

13-
You can enable Regional Data Ingest and Storage from the Regional Settings tab within your Workspace settings. Enabling the feature here makes the feature available to both client-side and server-side sources.
13+
You can enable Regional Data Ingestion and Storage from the Regional Settings tab within your Workspace settings. Enabling the feature here makes the feature available to both client-side and server-side sources.
1414

1515
![enable](images/enable-regional-ingest.png)
1616

1717
> info ""
18-
> **Note**: Regional Data Storage a Beta feature, and its use is governed by the [(1) Segment First Access and Beta Terms and Conditions](https://segment.com/legal/first-access-beta-preview/) and [(2) Segment Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/).
18+
> **Note**: Regional Data Storage is a Beta feature, and its use is governed by the [(1) Segment First Access and Beta Terms and Conditions](https://segment.com/legal/first-access-beta-preview/) and [(2) Segment Acceptable Use Policy](https://segment.com/legal/acceptable-use-policy/).
1919
20-
## Regional Data Ingest
20+
## Regional Data Ingestion
2121

22-
Regional Data Ingest enables you to send data to Segment from both Client-side and Server-side sources through locally hosted API ingest points. The regional infrastructure can fail-over across locations within a region, but never across regions.
22+
Regional Data Ingestion enables you to send data to Segment from both Client-side and Server-side sources through regionally hosted API ingest points. The regional infrastructure can fail-over across locations within a region, but never across regions.
2323

2424
### Client-side sources
2525

26-
You can configure Segment's client-side SDKs for Javascript, iOS, Android, and React Native sources to send data to a regional host after you've updated the Ingest Region in that source's settings.
26+
You can configure Segment's client-side SDKs for Javascript, iOS, Android, and React Native sources to send data to a regional host after you've updated the Data Ingestion Region in that source's settings.
2727

28-
![ingest region](images/regional-ingest.png)
28+
![ingestion region](images/regional-ingest.png)
2929

3030
All regions are configured on a **per-source** basis. You'll need to configure the region for each source separately if you do not want to use the default region (Oregon). All Segment client-side SDKs read this setting and update themselves automatically to send data to new endpoints when the app is reloaded. You do not need to change code when you switch regions.
3131

0 commit comments

Comments
 (0)