Tag: simple route

Route53 – Overview

admin

AWS Route53 service is used to manage the DNS records for your infrastructure.

  • SOA record stores information about
    • The name of the server that supplied the data of the zone.
    • The administrator of the zone
    • The current version of the data file.
    • The default number of seconds for the time-to-live file on the resource record
  • Alias Records
    • Alias records are used to map resource record sets in your hosted zone to ELB, CloudFront Distribution, or S3 buckets that are configured as websites.
    • Alias record works like CNAME record in that you map one DNS name (www.example.com) to another target DNS name (elbtest.elb.amazonaws.com).
    • Key Differences – A CNAME can’t be used for naked domain names (Zone apex record). You can’t have a CNAME pointing to the naked domain name i.e. http://example.com. It must be either an A record or an alias.
  • Route 53 is a global service and is not restricted to regions.
  • Routing policy in AWS
    • Simple Routing
    • Weighted Routing
    • Latency – Based routing
    • Failover Routing
    • Geolocation Routing
    • MultiValue Routing
  • Simple Routing policy
    • This is the default routing policy when we create a new record set.
    • It is good when we have only one record set.
    • It basically works around robin policy, for two instances each of them will appear one after the another.
  • Weighted routing policy
    • As we can see from the example, with weighted routing we can route the traffic based on the weight to certain instances.
  • Latency Based Routing
    • Latency-based routing allows you to route your traffic based on the lowest network latency for your end-users. (fastest response time).
    • To use latency-based routing, you create a latency resource record set for the amazon EC2 or (ELB) resource in each region that hosts your website. When AWS route 53 receives a query for your website. It selects the latency resource record set for the region that gives the user the lowest latency. Route 53 then responds with the value associated with that record set.
  • Failover Routing Policy
    • Failover routing policies are used when you have to create an Active/Passive setup.
    • Route 53 will monitor the health of your primary site using the health check page.
    • The Heath check page is the endpoint of your instances.
    • We need to create health checks and configure the endpoints to be monitored.
  • Geo-Location Routing Policy
    • Geo Location Routing lets you choose where your traffic will be sent based on the geographical location of the users.
  • Multivalue Answer Routing
    • You can have health check endpoints for each EC2 instance and if anyone fails you can remove it.