Amazon Route 53 now supports health checks for private endpoints

Amazon Route 53 now offers Private Endpoint Health Checks, enabling business-critical workloads that never touch the public internet, such as internal APIs, databases, and self-hosted nodes behind internal load balancers or in private subnets, to use native health monitoring and automatic DNS failover. Customers can health-check any reachable private target by IP address, domain, or port over HTTP, HTTPS, or TCP. Customers can associate these health checks with Route 53 DNS records across routing policies in private hosted zones, so Route 53 routes traffic only to healthy endpoints and manages failover automatically. 

Previously, teams built custom control loops using Amazon CloudWatch alarms, AWS Lambda functions, and the Route 53 API to achieve DNS failover for private resources. With this approach, failover took several minutes and added operational burden. Detection and DNS failover with Private Endpoint Health Checks are designed to complete in seconds rather than minutes, the service is fully managed, and nothing is exposed to the public internet. 

The feature supports on-premises and hybrid endpoints reachable from the VPC over AWS Direct Connect or AWS Site-to-Site VPN, enabling resilience patterns such as active-passive disaster recovery and cross-Region DR over AWS Transit Gateway or AWS Cloud WAN. Amazon Route 53 Private Endpoint Health Checks is available today in all AWS commercial regions. To learn more, visit the Amazon Route 53 Developer Guide and the Route 53 pricing page. 

 

Categories: general:products/amazon-route-53,marketing:marchitecture/networking-and-content-delivery,marketing:marchitecture/networking

Source: Amazon Web Services