You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
You can use AWS PrivateLink to connect different accounts in the same AWS region. The following diagram shows an overview of how AWS PrivateLink for Splunk Observability Cloud works:
35
32
36
33
.. image:: /_images/gdi/AWS_PL_region1.png
37
34
:width:80%
38
35
:alt:AWS Private Link schema.
39
36
40
-
Connect different accounts across different regions using AWS PrivateLink
You can also connect different accounts from different regions with AWS PrivateLink as displayed in the image:
44
-
45
-
.. image:: /_images/gdi/AWS_PL_region2.png
46
-
:width:80%
47
-
:alt:AWS Private Link schema.
48
-
49
-
The following regions are supported:
50
-
51
-
* US East (N. Virginia) ``us-east-1``
52
-
* US East (Ohio) ``us-east-2``
53
-
* US West (N. California) ``us-west-1``
54
-
* US West (Oregon) ``us-west-2``
55
-
* Africa (Cape Town) ``af-south-1``
56
-
* Asia Pacific (Hong Kong) ``ap-east-1``
57
-
* Asia Pacific (Hyderabad) ``ap-south-2``
58
-
* Asia Pacific (Jakarta) ``ap-southeast-3``
59
-
* Asia Pacific (Melbourne) ``ap-southeast-4``
60
-
* Asia Pacific (Mumbai) ``ap-south-1``
61
-
* Asia Pacific (Osaka) ``ap-northeast-3``
62
-
* Asia Pacific (Seoul) ``ap-northeast-2``
63
-
* Asia Pacific (Singapore) ``ap-southeast-1``
64
-
* Asia Pacific (Sydney) ``ap-southeast-2``
65
-
* Asia Pacific (Tokyo) ``ap-northeast-1``
66
-
* Canada (Central) ``ca-central-1``
67
-
* Canada West (Calgary) ``ca-west-1``
68
-
* Europe (Frankfurt) ``eu-central-1``
69
-
* Europe (Zurich) ``eu-central-2``
70
-
* Europe (Ireland) ``eu-west-1``
71
-
* Europe (London) ``eu-west-2``
72
-
* Europe (Paris) ``eu-west-3``
73
-
* Europe (Milan) ``eu-south-1``
74
-
* Europe (Stockholm) ``eu-north-1``
75
-
* Middle East (Bahrain) ``me-south-1``
76
-
* Middle East (UAE) ``me-central-1``
77
-
* South America (São Paulo) ``sa-east-1``
78
-
79
-
If your workloads or Splunk Observability Cloud accounts are in regions not listed above, cross-region PrivateLink is not supported. In such cases, you should either:
80
-
81
-
* Use PrivateLink within the same AWS region.
82
-
* Set up VPC peering.
83
-
84
37
.. _aws-privatelink-endpoint-types:
85
38
86
39
AWS PrivateLink types of endpoint
@@ -254,7 +207,39 @@ Reach out to Splunk Customer Support with the following information to include y
254
207
255
208
* AWS region
256
209
257
-
* If you're connecting between two regions you need to provide both the source region (where your workloads are hosted) and the target account region (where your Splunk Observability Cloud account is located).
210
+
* Same region connectivity: If you're connecting between two regions you need to provide both the source region (where your workloads are hosted) and the target account region (where your Splunk Observability Cloud account is located).
211
+
212
+
* Cross-region connectivity: If you're connecting between two regions you need to provide both the source (or customer) region and the target (or Observability Cloud account) region. The following regions are supported:
213
+
214
+
* US East (N. Virginia) ``us-east-1``
215
+
* US East (Ohio) ``us-east-2``
216
+
* US West (N. California) ``us-west-1``
217
+
* US West (Oregon) ``us-west-2``
218
+
* Africa (Cape Town) ``af-south-1``
219
+
* Asia Pacific (Hong Kong) ``ap-east-1``
220
+
* Asia Pacific (Hyderabad) ``ap-south-2``
221
+
* Asia Pacific (Jakarta) ``ap-southeast-3``
222
+
* Asia Pacific (Melbourne) ``ap-southeast-4``
223
+
* Asia Pacific (Mumbai) ``ap-south-1``
224
+
* Asia Pacific (Osaka) ``ap-northeast-3``
225
+
* Asia Pacific (Seoul) ``ap-northeast-2``
226
+
* Asia Pacific (Singapore) ``ap-southeast-1``
227
+
* Asia Pacific (Sydney) ``ap-southeast-2``
228
+
* Asia Pacific (Tokyo) ``ap-northeast-1``
229
+
* Canada (Central) ``ca-central-1``
230
+
* Canada West (Calgary) ``ca-west-1``
231
+
* Europe (Frankfurt) ``eu-central-1``
232
+
* Europe (Zurich) ``eu-central-2``
233
+
* Europe (Ireland) ``eu-west-1``
234
+
* Europe (London) ``eu-west-2``
235
+
* Europe (Paris) ``eu-west-3``
236
+
* Europe (Milan) ``eu-south-1``
237
+
* Europe (Stockholm) ``eu-north-1``
238
+
* Middle East (Bahrain) ``me-south-1``
239
+
* Middle East (UAE) ``me-central-1``
240
+
* South America (São Paulo) ``sa-east-1``
241
+
242
+
.. note:: If your workloads or Splunk Observability Cloud accounts are in regions not listed above, cross-region PrivateLink is not supported. In such cases, you should either use PrivateLink within the same AWS region or set up VPC peering.
258
243
259
244
* Endpoint type
260
245
@@ -275,13 +260,24 @@ To verify your AWS Account ID has been allowed, follow these steps:
275
260
276
261
1. Log in to the AWS Management Console, and open the :guilabel:`Amazon VPC service` in the specific region where you intend to set up AWS PrivateLink.
277
262
278
-
2. On the left navigation pane, select :guilabel:`PrivateLink and Lattice`.
263
+
2. On the left navigation pane, select :guilabel:`PrivateLink and Lattice > Endpoints`, and select endpoint services that use NLBs and GWLBs.
279
264
280
-
3. Select :guilabel:`PrivateLink and Lattice > Endpoints`, and select endpoint services that use NLBs and GWLBs.
265
+
3. Enable PrivateLink:
281
266
282
-
4. Enter and verify the service name based on the AWS region where you're configuring the VPC endpoint. Identify the appropriate service name using the :ref:`AWS PrivateLink service names table <aws-privatelink-service-names>`.
267
+
* Same region connectivity:
268
+
269
+
1. Enter and verify the service name based on the AWS region where you're configuring the VPC endpoint.
270
+
2. Identify the appropriate service name using the :ref:`AWS PrivateLink service names table <aws-privatelink-service-names>`.
271
+
272
+
* Cross-region connectivity:
273
+
274
+
1. Sepcify service name from the :ref:`AWS PrivateLink service names table <aws-privatelink-service-names>`.
275
+
2. Enable Cross Region endpoint checkbox and select the AWS region of the above selected service.
276
+
277
+
4. Ensure the service name is accurate by selecting :strong:`Verify Service`.
283
278
284
279
* If you see the "Service name verified" message, proceed with :ref:`aws-privatelink-step3`.
280
+
285
281
* If you see the "Service name could not be verified" error message, your account ID is not yet allowed for the given service name. Reach out to Splunk Customer Support to check the status of your request from :ref:`aws-privatelink-step1`.
286
282
287
283
.. _aws-privatelink-step3:
@@ -293,29 +289,41 @@ To create a VPC endpoint, follow these steps:
293
289
294
290
1. Log in to the AWS Management Console, and open :guilabel:`Amazon VPC service` within the specific region where you intend to set up AWS PrivateLink. If you have a VPC peering configuration, keep in mind the destination region of VPC peering.
295
291
296
-
2. On the left navigation pane, select :guilabel:`PrivateLink and Lattice`.
292
+
2. On the left navigation pane, select :guilabel:`PrivateLink and Lattice > Endpoints`, and select endpoint services that use NLBs and GWLBs.
297
293
298
-
3. Select :guilabel:`PrivateLink and Lattice > Endpoints`, and select endpoint services that use NLBs and GWLBs.
294
+
3. Enable PrivateLink:
299
295
300
-
4. Enter and verify the service name based on the AWS region where you're configuring the VPC endpoint. Identify the appropriate service name using the :ref:`AWS PrivateLink service names table <aws-privatelink-service-names>`.
296
+
* Same region connectivity:
297
+
298
+
1. Enter and verify the service name based on the AWS region where you're configuring the VPC endpoint.
299
+
2. Identify the appropriate service name using the :ref:`AWS PrivateLink service names table <aws-privatelink-service-names>`.
300
+
301
+
* Cross-region connectivity:
302
+
303
+
1. Sepcify service name from the :ref:`AWS PrivateLink service names table <aws-privatelink-service-names>`.
304
+
2. Enable Cross Region endpoint checkbox and select the AWS region of the above selected service.
301
305
302
-
5. Select the VPC in which you want to create the endpoint.
306
+
4. Ensure the service name is accurate by selecting :strong:`Verify Service`.
307
+
308
+
* If you see the "Service name verified" message, proceed with :ref:`aws-privatelink-step3`.
309
+
310
+
* If you see the "Service name could not be verified" error message, your account ID is not yet allowed for the given service name. Reach out to Splunk Customer Support to check the status of your request from :ref:`aws-privatelink-step1`.
303
311
304
-
6. Select the subnet or subnets within the VPC where the endpoint will reside. Make sure to select the subnets from the appropriate availability zones.
312
+
5. Select the subnet or subnets within the VPC where the endpoint will reside. Make sure to select the subnets from the appropriate availability zones.
305
313
306
-
7. Set the IP address type to ``IPv4``.
314
+
6. Set the IP address type to ``IPv4``.
307
315
308
-
8. Specify the security group controlling traffic for the endpoint. Set the outbound rule to HTTPS protocol and the ``443`` port.
316
+
7. Specify the security group controlling traffic for the endpoint. Set the outbound rule to HTTPS protocol and the ``443`` port.
309
317
310
318
The following image shows the security options for AWS PrivateLink:
:alt:Specify security groups that control traffic.
315
323
316
-
9. Review the configuration details and select :guilabel:`Create Endpoint`.
324
+
8. Review the configuration details and select :guilabel:`Create Endpoint`.
317
325
318
-
10. Before proceeding to :ref:`aws-privatelink-step4`, confirm with Splunk Customer Support that you created the endpoint, that the service name has been verified, and that Support has activated the endpoint urls.
326
+
9. Before proceeding to :ref:`aws-privatelink-step4`, confirm with Splunk Customer Support that you created the endpoint, that the service name has been verified, and that Support has activated the endpoint urls.
0 commit comments