AWS PrivateLink now supports access over Inter-Region VPC Peering
Applications in an AWS VPC can now securely access AWS PrivateLink endpoints across AWS Regions using Inter-Region VPC Peering. AWS PrivateLink allows you to privately access services hosted on AWS in a highly available and scalable manner, without using public IPs, and without requiring the traffic to traverse the Internet. This release makes it possible for customers to privately connect to a service even if the service endpoint resides in a different AWS Region. Traffic using Inter-Region VPC Peering stays on the global AWS backbone and never traverses the public Internet.
AWS PrivateLink is available in US East (N. Virginia), US East (Ohio), US West (Oregon), 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) and South America (São Paulo) AWS Regions. To learn more, visit the AWS PrivateLink documentation.
Applications in an AWS VPC can now securely access AWS PrivateLink endpoints across AWS Regions using Inter-Region VPC Peering. AWS PrivateLink allows you to privately access services hosted on AWS in a highly available and scalable manner, without using public IPs, and without requiring the traffic to traverse the Internet. This release makes it possible for customers to privately connect to a service even if the service endpoint resides in a different AWS Region. Traffic using Inter-Region VPC Peering stays on the global AWS backbone and never traverses the public Internet.
AWS PrivateLink is available in US East (N. Virginia), US East (Ohio), US West (Oregon), 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) and South America (São Paulo) AWS Regions. To learn more, visit the AWS PrivateLink documentation.