Amazon Web Service- Route 53
Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. It is designed for developers and corporate to route the end users to Internet applications by translating human readable names like www.mydomain.com, into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other.
Ø Features of Route 53:
1. Easy to register your domain − We can purchase all level of domains like .com, .net, .org, etc. directly from Route 53.
2. Highly reliable − Route 53 is built using AWS infrastructure. Its distributed nature towards DNS servers help to ensure a consistent ability to route applications of end users.
3. Scalable– Route 53 is designed in such a way that it automatically handles large volume queries without the user’s interaction.
4. Can be used with other AWS Services − Route 53 also works with other AWS services. It can be used to map domain names to our Amazon EC2 instances, Amazon S3 buckets, Amazon and other AWS resources.
5. Easy to use − It is easy to sign-up, easy to configure DNS settings, and provides quick response to DNS queries.
6. Health Check- Route 53 monitors the health of the application. If an outage is detected, then it automatically redirects the users to a healthy resource.
7. Cost-Effective − Pay only for the domain service and the number of queries that the service answers for each domain.
8. Secure −By integrating Route 53 with AWS (IAM), there is complete control over every user within the AWS account, such as deciding which user can access which part of Route 53.
Buy the best book for AWS- AWS Certified Solutions Architect Study Guide- by Ben Piper and David Clinton, Google Cloud Certified – Professional Cloud Architect” by Dan Sullivan
v DNS Records:
DNS, or the Domain Name System, translates human readable domain names (for example, www.amazon.com) to machine readable IP addresses (for example, 192.0.2.44).
v Routing Policy:
1. Simple Routing: It allows to configure DNS with no special Route 53 Routing. IT is mainly used when you have a single resource that performs a given function for your domain.
2. Failover Routing: It routes traffic to another or alternate resource when the previous resource is unhealthy. It makes one Elastic Load Balancer on active mode and the other on standby mode. It switches automatically when there is a failover.
3. Geolocation Routing: It routes the resources based on the geographic location of the users. It localizes the content or website in the language of the user. There are by specified by continent, or by country.
4. Geoproximity Routing (traffic flow only): Use when you want to route traffic based on the location of your resources and, optionally, shift traffic from resources in one location to another.
Greetings! This is my 1st comment here so I just wanted to give a quick shout out and tell you I truly enjoy reading your blog posts. Can you suggest any other blogs/websites/forums that cover the same subjects? Thank you!