Amazon Route 53 DNS service now supports AWS PrivateLink

Amazon Route 53 now supports AWS PrivateLink for API requests to the route53.amazonaws.com service endpoint, allowing your AWS workloads to make changes to critical DNS infrastructure, including hosted zones, records, and health checks, without using the public internet. With this release, you can set up private connectivity between your virtual private clouds (VPCs) and the Route 53 API, from your VPC on the AWS backbone, in any AWS Region.

The Route 53 API is used by customers for domain name system (DNS) operations, which are a foundational layer of their cloud infrastructure automation, user-facing applications, and internal services. This integration simplifies cloud architecture by removing the need for customers to setup and manage complex networking services that connect resources in their virtual private clouds (VPCs) privately to the Route 53 API. Now, customers can use a VPC endpoint within their VPC to establish connectivity to the Route 53 API. Customers outside the US East (N. Virginia) Region can use cross-region Interface VPC endpoints to natively connect to Route53 from other Regions, without the need to send traffic over the public internet or set up inter-region connectivity like VPC peering.

Route 53 support for PrivateLink is available globally, except in AWS GovCloud (US) and Amazon Web Services in China. To learn more about this feature, or to get started, visit the AWS PrivateLink documentation. To learn about pricing, visit the PrivateLink pricing page.