Skip to content

Commit 11ab6c0

Browse files
DOCSP-20844 add troubleshoot info (#232)
* DOCSP-20844 add troubleshoot info * DOCSP-20844 updates for feedback * DOCSP-20844 updates for review feedback
1 parent d45dbd1 commit 11ab6c0

File tree

2 files changed

+58
-0
lines changed

2 files changed

+58
-0
lines changed

source/includes/steps-add-existing-privatelink.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,4 +55,5 @@ ref: click-confirm
5555
level: 4
5656
stepnum: 0
5757
title: "Click :guilabel:`Confirm` to add the existing private endpoint."
58+
5859
...

source/includes/steps-create-new-privatelink.yaml

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -123,5 +123,62 @@ ref: finish-private-endpoint-aws
123123
level: 5
124124
stepnum: 0
125125
title: "Click :guilabel:`Finish endpoint creation`."
126+
---
127+
ref: resource-aws-security-group
128+
level: 5
129+
stepnum: 0
130+
title: "Configure your resources' security groups to send traffic to
131+
and receive traffic from the :term:`interface endpoint`."
132+
content: |
133+
134+
For each resource that needs to connect to your {+dl+} using
135+
{+aws-pl+}, the resource's security group must allow outbound
136+
traffic to the :term:`interface endpoint's <interface endpoint>`
137+
private IP(s) on all ports.
138+
139+
See :aws:`Adding Rules to a Security Group </AWSEC2/latest/UserGuide/ec2-security-groups.html#adding-security-group-rule>`
140+
for more information.
141+
142+
---
143+
title: "Create a security group for your interface endpoint to allow
144+
resources to access it."
145+
ref: attach-aws-security-group
146+
level: 4
147+
stepnum: 0
148+
content: |
149+
150+
This security group must allow inbound traffic on all ports from each
151+
resource that needs to connect to your {+dl+} using {+aws-pl+}:
126152
153+
a. In the |aws| console, navigate to the :guilabel:`VPC Dashboard`.
154+
155+
#. Click :guilabel:`Security Groups`, then click
156+
:guilabel:`Create security group`.
157+
158+
#. Use the wizard to create a security group. Make sure you select
159+
your VPC from the :guilabel:`VPC` list.
160+
161+
#. Select the security group you just created, then click the
162+
:guilabel:`Inbound Rules` tab.
163+
164+
#. Click :guilabel:`Edit Rules`.
165+
166+
#. Add rules to allow all inbound traffic from each resource in your
167+
VPC that you want to connect to your {+dl+}.
168+
169+
#. Click :guilabel:`Save Rules`.
170+
171+
#. Click :guilabel:`Endpoints`, then click the endpoint for your
172+
VPC.
173+
174+
#. Click the :guilabel:`Security Groups` tab, then click
175+
:guilabel:`Edit Security Groups`.
176+
177+
#. Add the security group you just created, then click
178+
:guilabel:`Save`.
179+
180+
To learn more about :aws:`VPC security groups
181+
</vpc/latest/userguide/VPC_SecurityGroups.html>`, see the |aws|
182+
documentation.
183+
127184
...

0 commit comments

Comments
 (0)