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

Commit 0ecb7c0

Browse files
Feedback
1 parent 541e575 commit 0ecb7c0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

gdi/private-connectivity/aws-privatelink.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -240,8 +240,8 @@ To create a VPC endpoint, follow these steps:
240240

241241
7. Set the IP address type to ``IPv4``.
242242

243-
8. Specify the security group or groups controlling inbound and outbound traffic for the endpoint, and set the outbound rule for the selected security groups open for port ``443``.
244-
243+
8. Specify the security group or groups controlling inbound and outbound traffic for the endpoint, and set the outbound rule for the selected security groups open for port ``443``. If you're using HTTPS, you need to configure inbound rules only.
244+
245245
The following image shows the security options for AWS PrivateLink:
246246

247247
.. image:: /_images/gdi/aws-privatelink-secgroups2.png
@@ -250,7 +250,7 @@ To create a VPC endpoint, follow these steps:
250250

251251
9. Review the configuration details and select :guilabel:`Create Endpoint`.
252252

253-
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.
253+
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.
254254

255255
.. _aws-privatelink-step4:
256256

0 commit comments

Comments
 (0)