A company is releasing a new version of its web application. The SysOps administrator wants to perform a canary deployment by routing of user traffic to the current production Application Load Balancer (ALB) and of traffic to a new ALB. Which Route 53 configuration should the administrator implement to meet these requirements?
- Create two Alias A records for the subdomain, both configured with the Weighted routing policy, assigning a weight of to the production ALB record and to the new ALB record.Answer
- BCreate two CNAME records for the subdomain using the Simple routing policy, with one record pointing to each ALB.
- CCreate two Alias A records for the subdomain, both configured with the Failover routing policy, designating the production ALB as primary and the new ALB as secondary.
- DCreate a single CNAME record for the subdomain, and use weighted records within the ALB target groups to split the DNS traffic.
Answer
Create two Alias A records for the subdomain, both configured with the Weighted routing policy, assigning a weight of to the production ALB record and to the new ALB record.
The correct configuration uses the Weighted routing policy with two Alias A records. This allows the administrator to split DNS traffic in a proportion (by setting weights of and ). Using Alias records rather than CNAMEs is the recommended AWS best practice for mapping domains to load balancers, as they automatically update when the ALB IPs change and do not incur query charges.
Step-by-Step Solution
Key Concept
Weighted routing policy and Alias records in Route 53