AWS PrivateLink now Supports Access Over VPC Peering
Applications in an Amazon Virtual Private Cloud (Amazon VPC) can now securely access AWS PrivateLink endpoints across VPC peering connections. AWS PrivateLink allows you to privately access services hosted on the AWS network in a highly available and scalable manner, without using public IPs and without requiring the traffic to traverse the internet.
Applications in an Amazon Virtual Private Cloud (Amazon VPC) can now securely access AWS PrivateLink endpoints across VPC peering connections. AWS PrivateLink allows you to privately access services hosted on the AWS network in a highly available and scalable manner, without using public IPs and without requiring the traffic to traverse the internet.
The support of VPC peering by AWS PrivateLink makes it possible for customers to privately connect to a service even if that service's endpoint resides in a different Amazon VPC that is connected using VPC peering. AWS PrivateLink endpoints can now be accessed across both intra- and inter-region VPC peering connections. You can learn more about this in the Amazon VPC documentation.
AWS PrivateLink is available in these AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), GovCloud (US-West), US West (N. California), EU (London), EU (Ireland), EU (Frankfurt), EU (Paris), Canada (Central), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), South America (São Paulo), China (Beijing), operated by Sinnet, and China (Ningxia), operated by Ningxia Western Cloud Data Technology Co. Ltd. (NWCD). To learn more, visit the AWS PrivateLink documentation.