@@ -62,51 +62,59 @@ AWS PrivateLink endpoint URLs
6262.. list-table ::
6363  :header-rows:  1
6464  :width:  100
65-   :widths:  20 , 20, 20, 20, 20
65+   :widths:  10, 10 , 20, 20, 20, 20
6666
67-   * - AWS region
67+   * - Splunk Observability Cloud realm
68+     - AWS region
6869    - Ingest endpoint URL
6970    - API endpoint URL
7071    - Backfill endpoint URL
7172    - Stream endpoint URL
7273
73-   * - ap-northeast-1
74+   * - jp0
75+     - AWS AP Tokyo (ap-northeast-1)
7476    - :new-page: `private-ingest.jp0.signalfx.com <http://private-ingest.jp0.signalfx.com/> `
7577    - :new-page: `private-api.jp0.signalfx.com <http://private-api.jp0.signalfx.com/> `
7678    - Coming soon
7779    - :new-page: `private-stream.jp0.signalfx.com <http://private-stream.jp0.signalfx.com/> `
7880
79-   * - ap-southeast-2
81+   * - au0
82+     - AWS AP Sydney (ap-southeast-2)
8083    - :new-page: `private-ingest.au0.signalfx.com <http://private-ingest.au0.signalfx.com/> `
8184    - :new-page: `private-api.au0.signalfx.com <http://private-api.au0.signalfx.com/> `
8285    - Coming soon
8386    - :new-page: `private-stream.au0.signalfx.com <http://private-stream.au0.signalfx.com/> `
8487
85-   * - eu-central-1
88+   * - eu1
89+     - AWS EU Frankfurt (eu-central-1)
8690    - :new-page: `private-ingest.eu1.signalfx.com <http://private-ingest.eu1.signalfx.com/> `
8791    - :new-page: `private-api.eu1.signalfx.com <http://private-api.eu1.signalfx.com/> `
8892    - Coming soon
8993    - :new-page: `private-stream.eu1.signalfx.com <http://private-stream.eu1.signalfx.com/> `
9094
91-   * - eu-west-1
95+   * - eu0
96+     - AWS EU Dublin (eu-west-1)
9297    - :new-page: `private-ingest.eu0.signalfx.com <http://private-ingest.eu0.signalfx.com/> `
9398    - :new-page: `private-api.eu0.signalfx.com <http://private-api.eu0.signalfx.com/> `
9499    - Coming soon
95100    - :new-page: `private-stream.eu0.signalfx.com <http://private-stream.eu0.signalfx.com/> `
96101
97-   * - eu-west-2
102+   * - eu2
103+     - AWS EU London (eu-west-2)
98104    - :new-page: `private-ingest.eu2.signalfx.com <http://private-ingest.eu2.signalfx.com/> `
99105    - :new-page: `private-api.eu2.signalfx.com <http://private-api.eu2.signalfx.com/> `
100106    - Coming soon
101107    - :new-page: `private-stream.eu2.signalfx.com <http://private-stream.eu2.signalfx.com/> `
102108
103-   * - us-east-1
109+   * - us0
110+     - AWS US East Virginia (us-east-1)
104111    - :new-page: `private-ingest.us0.signalfx.com <http://private-ingest.us0.signalfx.com/> `
105112    - :new-page: `private-api.us0.signalfx.com <http://private-api.us0.signalfx.com/> `
106113    - Coming soon
107114    - :new-page: `private-stream.us0.signalfx.com <http://private-stream.us0.signalfx.com/> `
108115
109-   * - us-west-2
116+   * - us1
117+     - AWS US West Oregon (us-west-2)
110118    - :new-page: `private-ingest.us1.signalfx.com <http://private-ingest.us1.signalfx.com/> `
111119    - :new-page: `private-api.us1.signalfx.com <http://private-api.us1.signalfx.com/> `
112120    - Coming soon
@@ -120,51 +128,59 @@ AWS PrivateLink service names
120128.. list-table ::
121129  :header-rows:  1
122130  :width:  100
123-   :widths:  20 , 20, 20, 20, 20
131+   :widths:  10, 10 , 20, 20, 20, 20
124132
125-   * - AWS region
133+   * - Splunk Observability Cloud realm
134+     - AWS region
126135    - Ingest endpoint service name
127136    - API endpoint service name
128137    - Backfill endpoint service name
129138    - Stream endpoint service name
130139
131-   * - ap-northeast-1
140+   * - jp0
141+     - AWS AP Tokyo (ap-northeast-1)
132142    - com.amazonaws.vpce.ap-northeast-1.vpce-svc-086c8167a74323e5a
133143    - com.amazonaws.vpce.ap-northeast-1.vpce-svc-06e1951072fcabaaa
134144    - Coming soon
135145    - com.amazonaws.vpce.ap-northeast-1.vpce-svc-0aebd0dfe769cc20b
136146
137-   * - ap-southeast-2
147+   * - au0
148+     - AWS AP Sydney (ap-southeast-2)
138149    - com.amazonaws.vpce.ap-southeast-2.vpce-svc-01e4e31c294754b6e
139150    - com.amazonaws.vpce.ap-southeast-2.vpce-svc-0d1d69a0b1bf003cd
140151    - Coming soon
141152    - com.amazonaws.vpce.ap-southeast-2.vpce-svc-006a9808c3bf97fc1
142153
143-   * - eu-central-1
154+   * - eu1
155+     - AWS EU Frankfurt (eu-central-1)
144156    - com.amazonaws.vpce.eu-central-1.vpce-svc-0163ebbf011db95fa
145157    - com.amazonaws.vpce.eu-central-1.vpce-svc-063722bf4a2e858a3
146158    - Coming soon
147159    - com.amazonaws.vpce.eu-central-1.vpce-svc-022080c55adaeac78
148160
149-   * - eu-west-1
161+   * - eu0
162+     - AWS EU Dublin (eu-west-1)
150163    - com.amazonaws.vpce.eu-west-1.vpce-svc-01c194b2265ecb86e
151164    - com.amazonaws.vpce.eu-west-1.vpce-svc-07b08296ff84e17a0
152165    - Coming soon
153166    - com.amazonaws.vpce.eu-west-1.vpce-svc-0d036df6dbc6ddadb
154167
155-   * - eu-west-2
168+   * - eu2
169+     - AWS EU London (eu-west-2)
156170    - com.amazonaws.vpce.eu-west-2.vpce-svc-0f7427a7b9ef925b0
157171    - com.amazonaws.vpce.eu-west-2.vpce-svc-0719f35de75c08514
158172    - Coming soon
159173    - com.amazonaws.vpce.eu-west-2.vpce-svc-0bc5b13127f2916ce
160174
161-   * - us-east-1
175+   * - us0
176+     - AWS US East Virginia (us-east-1)
162177    - com.amazonaws.vpce.us-east-1.vpce-svc-0336437d577075951
163178    - com.amazonaws.vpce.us-east-1.vpce-svc-089b68950f5be1c22
164179    - Coming soon
165180    - com.amazonaws.vpce.us-east-1.vpce-svc-0c7d803ea7ebe3157
166181
167-   * - us-west-2
182+   * - us1
183+     - AWS US West Oregon (us-west-2)
168184    - com.amazonaws.vpce.us-west-2.vpce-svc-06376c4a9be288ee9
169185    - com.amazonaws.vpce.us-west-2.vpce-svc-0da2bbb45fa4c3a6b
170186    - Coming soon
@@ -281,9 +297,43 @@ To delete an endpoint, follow these steps:
281297#. Select the VPC endpoint you want to delete.
282298#. Confirm the deletion when prompted.
283299
284- Advanced configuration: AWS PrivateLink with VPC peering  
300+ Advanced configuration 
285301========================================================================== 
286302
303+ Use AWS PrivateLink with the Collector 
304+ -------------------------------------------------- 
305+ 
306+ To use AWS PrivateLink URLs in your Collector instance, update the necessary variables in your Collector configuration to point to the given endpoint type: 
307+ 
308+ .. list-table ::
309+   :header-rows:  1
310+   :width:  100
311+   :widths:  20, 40, 40
312+ 
313+   * - Endpoint type
314+     - Endpoint URL
315+     - Example
316+ 
317+   * - Metric ingest endpoint
318+     - ``private-ingest.<REGION>.signalfx.com ``
319+     - ``private-ingest.us0.signalfx.com ``
320+ 
321+   * - Traces ingest endpoint
322+     - ``private-ingest.<REGION>.signalfx.com/v2/trace ``
323+     - ``private-ingest.us0.signalfx.com/v2/trace ``
324+ 
325+   * - API endpoint URL
326+     - ``http://<REGION>.signalfx.com ``
327+     - ``http://private-api.us0.signalfx.com ``
328+ 
329+ 
330+ See all PrivateLink URLs at :ref: `aws-privatelink-endpoint-urls `.
331+ 
332+ For information about the Collector's environment variables see :ref: `collector-env-var `.
333+ 
334+ Use AWS PrivateLink with VPC peering 
335+ -------------------------------------------------- 
336+ 
287337Examine a scenario where the workloads that you're monitoring with Splunk Observability Cloud are in the AWS ``ap-south-1 `` region, and your Splunk Observability Cloud account is in ``us-east-1 ``. You want to use PrivateLink to ingest observability data, but PrivateLink only works within one AWS region.
288338
289339In this scenario, carry out the following steps:
0 commit comments