Recipe: Route53 routing policies

Choose the right routing policy for latency, failover, geolocation, or weighted distribution across your Nimbus edge endpoints.

Simple routing

One record, one target. Use for single-region deployments where all traffic hits the same origin.

Assign weights to multiple records. Ideal for canary releases or gradual traffic shifting between Nimbus instances.

Route users to the lowest-latency region. Pair with Nimbus edge nodes in us-east-1, eu-west-1, and ap-southeast-1.

Active-passive configuration. Health checks flip traffic to a standby endpoint when the primary becomes unhealthy.

Serve localized content by continent or country. Enforce data residency constraints at the DNS layer.

Quick tip

Combine geolocation and latency policies with alias records pointing to Nimbus-managed CloudFront distributions for multi-region resilience.