Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 3ca4c3d

Browse files
aurbiztondo-splunkaurbiztondo-splunk
committed
New table
1 parent 7dfeacd commit 3ca4c3d

File tree

1 file changed

+87
-6
lines changed

1 file changed

+87
-6
lines changed

‎gdi/private-connectivity/aws-privatelink.rst‎

Lines changed: 87 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,92 @@ You can use AWS PrivateLink to connect different accounts in the same AWS region
4040
Connect different accounts across different regions using AWS PrivateLink
4141
----------------------------------------------------------------------------------------------------
4242

43-
AWS PrivateLink also provides cross region private link connectivity for the following regions:
43+
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+
.. list-table::
52+
:header-rows: 1
53+
:width: 100
54+
:widths: 30, 10, 10, 10, 10, 10, 10, 10
55+
56+
* - Source AWS region / Splunk Observability Cloud realm
57+
- Target region: ap-southeast-2 (Sydney) / au0
58+
- Target region: ap-northeast-1 (Tokyo) / jp0
59+
- Target region: eu-west-1 (Dublin) / eu0
60+
- Target region: eu-central-1 (Frankfurt) / eu1
61+
- Target region: eu-west-2 (London) / eu2
62+
- Target region: us-east-1 (East Virginia) / us0
63+
- Target region: us-west-2 (West Oregon) / us1
64+
65+
* - ap-southeast-2 (Sydney)
66+
- Yes
67+
- Yes
68+
- Yes
69+
- No
70+
- No
71+
- Yes
72+
- Yes
73+
74+
* - ap-northeast-1 (Tokyo)
75+
- Yes
76+
- Yes
77+
- Yes
78+
- No
79+
- No
80+
- Yes
81+
- Yes
82+
83+
* - eu-west-1 (Dublin)
84+
- Yes
85+
- Yes
86+
- Yes
87+
- No
88+
- No
89+
- Yes
90+
- Yes
91+
92+
* - us-east-1 (East Virginia)
93+
- Yes
94+
- Yes
95+
- Yes
96+
- No
97+
- No
98+
- Yes
99+
- Yes
100+
101+
* - us-west-2 (West Oregon)
102+
- Yes
103+
- Yes
104+
- Yes
105+
- No
106+
- No
107+
- Yes
108+
- Yes
109+
110+
* - ap-southeast-1 (Singapore)
111+
- Yes
112+
- Yes
113+
- Yes
114+
- No
115+
- No
116+
- Yes
117+
- Yes
118+
119+
* - sa-east-1 (Sao Paolo)
120+
- Yes
121+
- Yes
122+
- Yes
123+
- No
124+
- No
125+
- Yes
126+
- Yes
127+
128+
OLD:
44129

45130
.. list-table::
46131
:header-rows: 1
@@ -63,7 +148,7 @@ AWS PrivateLink also provides cross region private link connectivity for the fol
63148
- Yes
64149
- Yes
65150

66-
* - ap-southeast-1 (Sydney) / au0
151+
* - ap-southeast-2 (Sydney) / au0
67152
- Yes
68153
- Yes
69154

@@ -79,10 +164,6 @@ AWS PrivateLink also provides cross region private link connectivity for the fol
79164
- Yes
80165
- No
81166

82-
.. image:: /_images/gdi/AWS_PL_region2.png
83-
:width: 80%
84-
:alt: AWS Private Link schema.
85-
86167
.. caution:: Cross-region connectivity is not supported if either the source or target account is in the ``eu-central-1`` (eu1) or ``eu-west-2`` (eu2) regions. For the latest list of supported AWS regions for cross-region PrivateLink connectivity refer to the :new-page:`official AWS announcement <https://aws.amazon.com/about-aws/whats-new/2024/11/aws-privatelink-across-region-connectivity/>`.
87168

88169
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:

0 commit comments

Comments
 (0)