EU endpoint changes requested from team #6266
Conversation
src/guides/regional-segment.md
Outdated
| @@ -30,7 +30,7 @@ Regional Data Ingestion enables you to send data to Segment from both Device-mod | |||
| {% include content/eu-cloud-event-sources.html %} | |||
|
|
|||
| ### 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. Segment's EU instance only supports data ingestion from Dublin, Ireland with the `events.eu1.segmentapis.com/` endpoint. If you are using the Segment EU endpoint with an Analytics-C# source, you must manually append `v1` to the URL. For instance, `events.eu1.segmentapis.com/v1`. | |||
| 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. Segment's EU instance only supports data ingestion from Dublin, Ireland with the `in.eu2.segmentapis.com` endpoint. If you are using the Segment EU endpoint with an Analytics-C# source, you must manually append `v1` to the URL. For instance, `in.eu2.segmentapis.com`. | |||
There was a problem hiding this comment.
@vbatanov & @vinodkone : I'm getting more confused now. 😬
Can you please confirm that we do still run the edge proxies in EU that forward all traffic to US?
There was a problem hiding this comment.
@erikdw: Yes, we still running edge proxy in EU that forward traffic to US.
Regarding this PR changes
We could have two scenarios :
- Client have
EUworkspace they must use the regional endpoint, which isevents.eu1.segmentapis.com - Client have
USworkspace and but desires to use the EU endpoint, they must use the edge proxy endpoint, which isin.eu2.segmentapis.com
The documentation need to be updated to include both cases
There was a problem hiding this comment.
ohhh I seeee. will need to make some changes to my changes.
There was a problem hiding this comment.
Do you know if we still have the APAC edge proxies? I remember we set those up before, but not sure if they ever got used for reals.
There was a problem hiding this comment.
Yes, we still have them and base on this metrics somebody still use them: https://segment.datadoghq.com/s/A9ih7c/df9-jqx-zpn
And would be better to mention them in this documentation as well:
- Client have
USworkspace and but desires to use theap-southeast-1 (Singapore)endpoint, they must use the edge proxy endpoint, which isin.ap1.segmentapis.com - Client have
USworkspace and but desires to use theap-southeast-2 (Sydney)endpoint, they must use the edge proxy endpoint, which isin.au1.segmentapis.com
There was a problem hiding this comment.
take a look at changes please and let me know what else might need done.
There was a problem hiding this comment.
Also, does this apply to server side end points or just client side?
forstisabella
added
the
fixed-content
| > For workspaces that use the EU West Data Processing region, the Dublin Ingestion region is preselected for all sources. | ||
| - If you have a US workspace and but want to use the ap-southeast-1 (Singapore) endpoint, use the edge proxy endpoint: in.ap1.segmentapis.com | ||
| - If you have a US workspace and but want to use the ap-southeast-2 (Sydney) endpoint, use the edge proxy endpoint: in.au1.segmentapis.com | ||
| - If you are using the Segment EU endpoint with an Analytics-C# source, you must manually append `v1` to the URL. For instance, `in.eu2.segmentapis.com/v1`. |
There was a problem hiding this comment.
I don't think this is only for Segment EU endpoint , I think this for any endpoint if we using Analytics-C#
| - If you have a US workspace and but want to use the ap-southeast-2 (Sydney) endpoint, use the edge proxy endpoint: in.au1.segmentapis.com | ||
| - If you are using the Segment EU endpoint with an Analytics-C# source, you must manually append `v1` to the URL. For instance, `in.eu2.segmentapis.com/v1`. | ||
| - If you're in the *US West* data processing region, you can select from: Dublin, Singapore, Oregon, and Sydney. | ||
| - If you're in the *EU West* data processing region, Segment's EU instance only supports data ingestion from Dublin with the `in.eu2.segmentapis.com` endpoint. |
There was a problem hiding this comment.
The in.eu2.segmentapis.com is EU proxy for US workspaces.
I think we should rephrase , so it will be easy to read and to cover all the case, something like this:
EU workspaces - supports data ingestion from Dublin with default endpoint events.eu1.segmentapis.com
US workspaces - supports data ingestion from Oregon (Default), Dublin, Singapore and Sydney.
- if you want to use the eu-west-1 (Dublin) endpoint, use the edge proxy endpoint:
in.eu2.segmentapis.com - if you want to use the ap-southeast-1 (Singapore) endpoint, use the edge proxy endpoint:
in.ap1.segmentapis.com - if you want to use the ap-southeast-2 (Sydney) endpoint, use the edge proxy endpoint:
in.au1.segmentapis.com
| @@ -51,15 +53,15 @@ All Segment client-side SDKs read this setting and update themselves automatical | |||
| ### 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: | |||
| 1. Oregon (Default) — `https://events.segmentapis.com/v1` | |||
| 2. Dublin — `https://events.eu1.segmentapis.com/` | |||
| 2. Dublin — `https://in.eu2.segmentapis.com` | |||
There was a problem hiding this comment.
I think those examples only for us or eu data processing region not for proxy
These changes were requested in this slack thread. There may be more changes coming.
https://twilio.slack.com/archives/C01E619RP1U/p1710871228879359
Helpful resources - https://segment.com/docs/guides/regional-segment/#destination-support-and-regional-endpoint-availability