Phased Deployment of New Application with Route53
Question
You currently have an application hosted on an ELB with EC2 Instances running in AWS.
Route53 is used as the DNS Service.
You are planning on deploying a new version of the application which will have a new ELB with EC2 Instances.
But you want this transition to be phased out so that a percentage of users get access to the new application.
Once the new application is confirmed as working that the entire user base can be switched over.
How would you configure Route53 in this case?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - A.
The AWS documentation mentions the following.
Weighted routing lets you associate multiple resources with a single domain name (example.com) or subdomain name (acme.example.com) and choose how much traffic is routed to each resource.
This can be useful for a variety of purposes, including load balancing and testing new versions of software.
For more information on the routing policy, please refer to the below URL:
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.htmlTo achieve a phased transition to a new application version hosted on a different ELB with EC2 instances, you need to use Route53 routing policies that support distributing traffic to multiple resources based on different criteria.
Option A: Weighted routing policy - This policy allows you to distribute traffic across multiple resources in proportions that you specify. For example, you can configure Route53 to send 50% of the traffic to the old ELB and 50% of the traffic to the new ELB. However, this approach may not be suitable for a phased transition where you want to gradually increase traffic to the new application version.
Option B: Failover routing policy - This policy is not appropriate for this scenario because it is designed to route traffic to a standby resource in case the primary resource fails.
Option C: Latency routing policy - This policy routes traffic to the resource that has the lowest latency to the user. It is not suitable for a phased transition scenario because it does not provide control over the percentage of traffic sent to each resource.
Option D: Simple routing policy - This policy sends all traffic to a single resource that you specify, which is not suitable for phased transition scenarios.
Therefore, the correct answer is A. Configure Route53 with the Weighted routing policy. To use this policy, you can initially route a small percentage of traffic to the new ELB and gradually increase it as you confirm the new application version is stable and working correctly. You can adjust the weighting percentage to control how much traffic is directed to each ELB. Once you are confident in the new version, you can switch all the traffic to the new ELB by setting the weighting to 100%.
