AWS PrivateLink share


Hi Team - I recently came across below blog and have one query on "Scenario 3: Connecting with third-party vendors using AWS PrivateLink"

Scenario 3 says,

Use the PrivateLink Endpoint in VPC A and allow applications in other VPCs to talk to that endpoint through the Transit Gateway.

Wanted to understand, how VPC B and VPC C use the Private Link endpoint created in VPC A to communicate to third party service ? Do we have any other better documentation apart from ""

asked 10 months ago478 views
2 Answers

Hello, as I understood, the main idea is to resolve in your SpokeVPC DNS name of the PrivateLink endpoint created in the main VPC. It is done by sharing Route53 resolvers from the main VPC to your Spoke VPCs. (

Let's presume you have main VPC ( where SNS endpoint is created.

  1. It has DNS name and IP address You have Spoke VPCs:
  • Spoke VPC1 (
  • Spoke VPC2 (
  1. You share the DNS name across spoke VPCs, that means that DNS server in Spoke VPC1/VPC2 will resolve to
  2. TransitGateway will route your requests from spoke VPCs to to the main VPC where PrivateLink is deployed.

Can be multi-regional as well

answered 10 months ago
  • Thanks for the details

Accepted Answer

The following documents would be relevant.
This section describes the flow of communication from SpokeVPC to HubVPC's VPC endpoints using Transit Gateway.

profile picture
answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions