AWS PrivateLink has introduced tunnel endpoints, which you can use to privately access a network segment in another AWS account. You might be a vendor or service provider whose software must reach applications and resources in a customer’s network. A tunnel endpoint connects you to them. Your customer can share with you the segment of their network where those resources reside, and you can tunnel into that network segment to access any resource located within it. The network segment is defined by the customer in the form of Classless Inter-Domain Routing (CIDR) ranges and serves as a perimeter for what the vendor can access. Resources located outside the perimeter can’t be reached by the vendor.
Tunnel endpoints also expand the resource configuration capability. Previously, to share resources with a vendor, the customer had to enumerate them individually by creating a resource configuration for each using IP address or DNS name. This was limiting for use cases…
