Cloud Equivalents

DNS & DNS-based routing · AWS vs Google Cloud

Route 53 routing policies and health checks vs Cloud DNS routing policies

Route 53 routing policies and health checks map to Cloud DNS routing policies: weighted round robin, geolocation, and failover, with health checks.

Direct match Use it to: Send users to the nearest or healthiest endpoint, split traffic by weight, or fail over between regions using DNS answers.

Last verified: · Edit on GitHub · Report an error

Side-by-side comparison

DNS-based traffic routing and failover: AWS vs Google Cloud side by side
AspectAmazon Web ServicesGoogle Cloud
ServiceRoute 53 routing policies and health checksCloud DNS routing policies
LifecycleGenerally availableGenerally available
What it isDNS-based traffic routing (weighted, latency, failover, geolocation, geoproximity, IP-based, multivalue) with health checks.Weighted round robin, geolocation, and failover routing policies with health checks.
Pricing modelRouting policy queries are charged per million (higher for latency, geo, and IP-based), plus per health check per month.Charged per zone and per query; health checks may add cost.
DocsRoute 53 routing policies and health checks docsCloud DNS routing policies docs
Pricing pageRoute 53 routing policies and health checks pricingCloud DNS routing policies pricing

Key differences

  • Health-checked policies work with internal load balancers and, for public zones, external endpoints; check the current support list.

Pricing summary

Pricing models only. No prices are quoted because they change by region and over time.

AWS
Routing policy queries are charged per million (higher for latency, geo, and IP-based), plus per health check per month. Route 53 routing policies and health checks pricing →
GCP
Charged per zone and per query; health checks may add cost. Cloud DNS routing policies pricing →

And on Azure?

Direct match Azure's equivalent is Azure Traffic Manager. AWS vs Azure comparison →

FAQ

What is the Google Cloud equivalent of Route 53 routing policies and health checks?

Route 53 routing policies and health checks map to Cloud DNS routing policies: weighted round robin, geolocation, and failover, with health checks.

How does pricing compare between Route 53 routing policies and health checks and Cloud DNS routing policies?

AWS: Routing policy queries are charged per million (higher for latency, geo, and IP-based), plus per health check per month. Google Cloud: Charged per zone and per query; health checks may add cost. Check the official pricing pages for current rates.

What is the Azure equivalent?

Azure Traffic Manager (direct match). Route 53 routing policies and health checks map to Azure Traffic Manager.

Related AWS vs GCP comparisons

Official sources