[netlify-build]

stayseesong · markzegarelli · commit f21f9ba2163b · 2021-11-02T16:49:09.000-07:00
diff --git a/src/_data/products.yml b/src/_data/products.yml
@@ -114,9 +114,9 @@ items:
     team: false
     business: true
     add-on: true
-- product_display_name: Data Residency
+- product_display_name: Regional Segment
   slug: data-residency
-  plan-note: "Data residency is available to customers on the Business Tier plan."
+  plan-note: "Regional Segment is available to customers on the Business Tier plan."
   plans:
     free: false
     team: false
diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml
@@ -227,8 +227,8 @@ sections:
     title: Integration Error Codes
   - path: /connections/rate-limits
     title: Rate Limits and SLA
-  - path: /connections/data-residency
-    title: Data Residency
+  - path: /connections/regional-segment
+    title: Regional Segment
 - section_title: Personas
   section:
   - path: /personas
diff --git a/src/connections/regional-segment-eu.md b/src/connections/regional-segment-eu.md
@@ -0,0 +1,58 @@
+---
+title: Regional Segment (Europe)
+---
+{% include content/plan-grid.md name="data-residency" %}
+
+
+
+
+Segment provides regional infrastructure across Europe, Middle East, Africa and Asia Pacific with [rate limits and SLA](/docs/connections/rate-limits/).
+
+As Schrems II restricts the transfer of personal data to any processors established in countries outside of Europe, all data in European workspaces ingest, store, process and deliver locally within the EU. You can set up workspaces in the EU where data is received via the Dublin, Ireland endpoint hosted in the EU for all sources, with the exception of [cloud object sources](/docs/connections/sources/#object-cloud-sources) and cloud event sources that aren't supported. Segment-hosted archives hosted in S3 AWS Dublin, Ireland, process, filter, validate, deduplicate, and archive data for EU workspaces.
+
+> info ""
+> Regional Segment for Europe is currently in beta. Segment’s [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature.
+
+## Create a new workspace with a different region
+To create a workspace with a different data processing region:
+1. Log in to your segment account.
+2. Click **New Workspace**.
+3. Select your **Data processing region**. This determines the location in which Segment collects, processes, and stores data that’s sent to and from your workspace. You can choose from *US West* or *EU Central*.  
+4. Click **Create workspace**.
+
+## Regional Data Ingestion
+Regional Data Ingestion enables you to send data to Segment from both Device-mode and Cloud-mode sources through regionally hosted API ingest points. The regional infrastructure can fail across locations within a region, but never across regions.
+
+Segment's EU instance only supports data ingestion from Dublin, Ireland through the `in.eu2.segmentapis.com/v1` endpoint.
+
+### Set your Data Ingestion Region
+To set your Data Ingestion Region:
+1. Go to your source.
+2. Select the **Settings** tab.
+3. Click **Regional Settings**.
+4. Choose your **Data Ingestion Region**.
+    * If you’re in the US region, you can select from: Dublin, Singapore, Oregon, and Sydney.
+    * Segment’s EU instance only supports data ingestion from Dublin with the `events.eu1.segmentapis.com` endpoint.
+
+### Client-side sources
+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.
+
+All regions are configured on a per-source basis. Configure the region for each source separately if you don't want to use the default region.
+
+> info ""
+> Dublin is the only region for EU instances and defaults automatically.
+
+All Segment client-side SDKs read this setting and update themselves automatically to send data to new endpoints when the app reloads. You don't need to change the code when you switch regions.
+
+### Server-side and project sources
+When you send data from a server-side or project source, you can use the `host` configuration parameter to send data to the desired region, which will be Dublin — `in.eu2.segmentapis.com/v1`
+
+## Regional Data Storage
+[Regional Data Storage](/docs/connections/data-residency/#regional-data-storage) isn't supported in EU workspaces.
+
+## EU Updates   
+### Data Lakes
+Regional Segment in the EU changes the way you [configure the Data Lakes AWS environment](/docs/connections/storage/data-lakes/data-lakes-manual-setup/#iam-role).
+
+### Warehouse Public IP Range
+Use Segment's custom CIDR `3.251.148.96/29` while authorizing Segment to write in to your Redshift or Postgres port. [BigQuery](/docs/connections/storage/catalog/bigquery/#getting-started) doesn't require you to allow a custom IP address.
diff --git a/src/connections/regional-segment.md b/src/connections/regional-segment.md
@@ -1,5 +1,5 @@
 ---
-title: Data Residency
+title: Regional Segment
 ---
 {% include content/plan-grid.md name="data-residency" %}
 
diff --git a/src/connections/storage/warehouses/faq.md b/src/connections/storage/warehouses/faq.md
@@ -81,7 +81,12 @@ We highly recommend scripting any sort of additions of data you might have to wa
 
 ## Which IPs should I whitelist?
 
-You can whitelist our custom IP 52.25.130.38/32 while authorizing Segment to write in to your Redshift or Postgres port.
+You can whitelist Segment's custom IP `52.25.130.38/32` while authorizing Segment to write in to your Redshift or Postgres port.
+
+If you're in the EU region, use CIDR `3.251.148.96/29`.
+
+> info ""
+> EU workspace regions are currently in beta. If you would like to learn more about the beta, please contact your account manager.
 
 BigQuery does not require whitelisting an IP address. To learn how to set up BigQuery, check out our [set up guide](https://segment.com/docs/connections/storage/catalog/bigquery/#getting-started)
 
