The Route 53 can configure your DNS based on the Weighted Routed policy for smoother migration from your on premise datacenter to the AWS. It can also be used to smoother migration from one region to other. Also you can avail it for any migrations by configuring it to work for your requirements.
Weighted Routing policy: To understand the concept , consider you are migrating from your on premise to the AWS hosted environment. Now if your application is business critical you don't really want the things to break no matter how much testing you have done in your non-prod environments. The weight based migrations can help you to reduce it.
For migration you would be having multiple LBs or servers configured. So you can add multiple DNS records for you application for the same domain and you attach a weight to your DNS record. For starting you can deploy the weight as 10% for AWS and 90% to your on premise data center and as you track the performance and availability you can keep on increasing the allotted weight in your DNS until it has fully migrated and become 100% for the AWS. It works on simple principle that rather than getting 100% customer to face dissatisfaction or down time its better to start with 10% or less depending on your needs. This can additionally make your transitions smoother from one enviornment to another environment.
Additionally you can customized your application in different regions and serve from both the environment though i would suggest there are much better way of achieving that. But for the migrations this is definately a plus.
Following are the steps to achieve the Weighted Routing in Route 53 AWS:-
1. Navigate to the Route 53 and go to the hosted zones.
2. Click on the "Create Record Set".
Name: www.unixcloudfusion.in
Type : A record
TTL: 60
Value: ip-of-the-aws-instance
Routing policy: Weighted
Weight:
Set id: optional
click create
3.Click on the "Create Record Set".
Name: www.unixcloudfusion.in
Type : A record
TTL: 60
Value: ip-of-on-premise-lbip
Routing policy: Weighted
Weight:
Set id: optional
click create
4. Thats it you are all set , rest all the things Route 53 will do for you.
Weighted Routing policy: To understand the concept , consider you are migrating from your on premise to the AWS hosted environment. Now if your application is business critical you don't really want the things to break no matter how much testing you have done in your non-prod environments. The weight based migrations can help you to reduce it.
For migration you would be having multiple LBs or servers configured. So you can add multiple DNS records for you application for the same domain and you attach a weight to your DNS record. For starting you can deploy the weight as 10% for AWS and 90% to your on premise data center and as you track the performance and availability you can keep on increasing the allotted weight in your DNS until it has fully migrated and become 100% for the AWS. It works on simple principle that rather than getting 100% customer to face dissatisfaction or down time its better to start with 10% or less depending on your needs. This can additionally make your transitions smoother from one enviornment to another environment.
Additionally you can customized your application in different regions and serve from both the environment though i would suggest there are much better way of achieving that. But for the migrations this is definately a plus.
Following are the steps to achieve the Weighted Routing in Route 53 AWS:-
1. Navigate to the Route 53 and go to the hosted zones.
2. Click on the "Create Record Set".
Name: www.unixcloudfusion.in
Type : A record
TTL: 60
Value: ip-of-the-aws-instance
Routing policy: Weighted
Weight:
Set id: optional
click create
3.Click on the "Create Record Set".
Name: www.unixcloudfusion.in
Type : A record
TTL: 60
Value: ip-of-on-premise-lbip
Routing policy: Weighted
Weight:
Set id: optional
click create
4. Thats it you are all set , rest all the things Route 53 will do for you.
0 comments:
Post a Comment