Skip to content

Commit 957806f

Browse files
committed
docs: move 'copy endpoint service name' step to after authorizing principals
1 parent 23da2c0 commit 957806f

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

docs/private-networking/aws-console-setup.mdx

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -152,8 +152,8 @@ This is the resource that PrivateLink consumers connect to.
152152

153153
</Step>
154154
<Step title="Create the endpoint service">
155-
Click **Create**. Note the **Service name** — it looks like `com.amazonaws.vpce.us-east-1.vpce-svc-0123abcd...`.
156-
You'll paste this into the Trigger.dev dashboard.
155+
Click **Create**. The service is created immediately — you'll come back to copy its **Service
156+
name** once you've authorized Trigger.dev in the next step.
157157
</Step>
158158
</Steps>
159159

@@ -185,6 +185,11 @@ By default, no one can connect to your endpoint service. You need to explicitly
185185
<Step title="Click Allow principals">
186186
The principal is now authorized to create a VPC Endpoint targeting your service.
187187
</Step>
188+
<Step title="Copy the endpoint service name">
189+
On the endpoint service detail page, copy the **Service name** value — it looks like
190+
`com.amazonaws.vpce.us-east-1.vpce-svc-0123abcd...`. You'll paste this into the Trigger.dev
191+
dashboard in the next step.
192+
</Step>
188193
</Steps>
189194

190195
## Step 5: Add the connection in Trigger.dev

0 commit comments

Comments
 (0)