Introduction:
Amazon Route 53 is a highly efficient and scalable cloud web service and is also
used for the health checking of resources.
It provides developers with an efficient and extremely reliable way to connect
users to internet applications without any downtime, it still has downtime in
servers or applications but users/customers may not be aware of it.
It effectively connects user requests to AWS such as Amazon EC2 instances,
Elastic Load Balancing, or Amazon S3 buckets.
AWS Route 53 mainly performs three functions
It registers the name for the website (Domain name) which needs a
name. Like if you want to buy a domain name, you that domain name
through Route 53.
It helps the user to connect the website or web application with the
browser in the server when he/she enters the website name.
It keeps checking the health of resources before the customer notices it
by sending an automated request over the internet to resources.
Benefits Of Using Route 53:
Highly efficient and reliable ensures a consistent ability to route
applications.
It can handle millions of millions of requests because it is highly scalable.
It can handle large queries without user interaction.
It’s very easy to use, to sign up for, and configure and provides fast
responses.
It’s very cost-effective like paying only for the services you used.
It’s very secure, because of Identity and Access Management (IAM)
1|Page
Sudhakara Rao Chillara/DevOps University
Types Of Routing Policies:
1. Simple Routing:
It allows configuring DNS with no unique 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 ELB (Elastic Load Balancing) on active
mode and the other on standby mode. It switches automatically when
there is a failover.
2|Page
Sudhakara Rao Chillara/DevOps University
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.
These are specified by continent, or by country.
4. Geo-proximity Routing:
It routes traffic to the resources based on the geographic location of
users and their resources based on the geographic location of users and
their resources. There is an option available to route less traffic or more
to a given resource
3|Page
Sudhakara Rao Chillara/DevOps University
5. Latency-based Routing:
It is mainly used when we have installed or hosted a website across
multiple AWS regions. It improves the performance by serving their
request from the lowest latency AWS region.
6. Weighted Routing:
It routes multiple resources with a single domain name and controls the
traffic to be routed to each resource. It is mainly useful for testing and
load-balancing new versions of the software.
Key Features of Route 53:
Traffic Volume:
According to your application’s geolocation, latency, health, and other factors,
you can direct end users to the optimal endpoint available.
Routing based on Latency:
End users can be directed to the AWS region with minimal latency.
A Geo DNS:
Your end users might be directed to an endpoint that is situated in their
particular area or the closest geographical place.
Failover DNS:
In order to prevent website crashes or outages, you might direct your end
customers to a different location.
Health Monitoring and Checks:
Amazon Route 53 keeps an eye on your website’s or application’s health and
performance. You may also keep an eye on your servers.
4|Page
Sudhakara Rao Chillara/DevOps University
Registering domains:
With the help of Amazon Route 53, you can search for and register available
domain names. Along with the current cost, a comprehensive list of the Top-
Level Domains (TLDs) that are currently accessible is also given.
Limitations of Amazon Route 53:
Even though it is a sophisticated DNS service with many useful capabilities,
Amazon Route 53 has a number of significant limitations.
The most crucial are as follows:
DNSSEC (Domain Name System Security Extensions) is not supported. It
is not possible to use DNSSEC on AWS Route 53. DNSSEC is able to
thwart man in the middle (MITM) attacks and other kinds of DNS attacks.
a single point of failure. When combined with other AWS services, AWS
Route 53 could form a single point of failure. AWS Route 53 disaster
recovery and associated problems are a result of this.
Price of Route 53. The service is pricey, especially for enterprises using
Route 53 with non-AWS endpoints/services. Particularly pricey are the
inquiries for each record type to which you apply a query, which is an
additional $50/month for the visual editor.
Optional forwarding. AWS Route 53 does not offer conditional
forwarding or forwarding for domains used on an on-premises network.
DNS load balancing for Route 53 only.
5|Page
Sudhakara Rao Chillara/DevOps University
Only minimal load balancing functions are offered by AWS Route 53 load
balancer features, which lack enterprise-class functionality and
comprehensive policy support.
6|Page
Sudhakara Rao Chillara/DevOps University
Steps To Configure Amazon Route 53:
In these steps, we are going to configure AWS Route 53. For creating an AWS
Free Tier Account click here:
Step 1: Now, search Route 53 in the search bar in the AWS Console.
7|Page
Sudhakara Rao Chillara/DevOps University
Step 2: Click on Create hosted zone on Route 53 Dashboard.
Step 3: On the new page fill in all the required details such as Domain name,
description, and select the public hosted zone and then click on create hosted
zone.
8|Page
Sudhakara Rao Chillara/DevOps University
Step 4: Now, a hosted zone for the domain name will be created.
Step 5: On the new page, there will be a list of record sets. By default, there will
be two records of type NS & SOA.
9|Page
Sudhakara Rao Chillara/DevOps University
Step 6: To create your record select the record name and click on the create
record option.
10 | P a g e
Sudhakara Rao Chillara/DevOps University
Step 7: Fill in all the required details such as Name, Type, Alias, TTL seconds,
Value, etc. Click the Create Record option. Create one more record for some
other region so that there will be two records with the same domain name
pointing to different IP addresses with your selected routing policy.
11 | P a g e
Sudhakara Rao Chillara/DevOps University
12 | P a g e
Sudhakara Rao Chillara/DevOps University
