Start preparing for your Next Exam | Use coupon – TOGETHER | Avail 30% discount

Overview of Amazon Route 53

  1. Home
  3. AWS Certified Solutions Architect Associate (SAA-C03)
  5. Overview of Amazon Route 53
  • It is an
    • Authoritative
    • highly available
    • scalable
    • cloud DNS service by AWS
  • Limit of 50 domain names on Route 53
  • compatible with IPv6
  • Allows management of mappings between domain names and IP addresses (records)
  • replies to “queries” for translating domain names to IP address
  • routing on port 53
  • can register and manage new domains
  • It monitors the health of applications using configuration
  • If health checks fail, it disables the endpoint for time as per TTL
  • Use ELB for load balancing
  • Traffic Flow application
    • is a visual editor
    • Can create complex routing policies spanning multiple regions and environments.
  •  
  • ELBs operate on domain names only, and not on fixed IPv4 or IPv6 addresses.
  • Not possible to use an A Record to resolve to an ELB, use an Alias record

Routing Policies

  • Simple
    • Default routing policy when you create a new record set
    • Most commonly used when you have a single resource that performs a given function for your domain
    • Example would be a single web server that serves content for a single domain name
  • Weighted
    • Use to route traffic to multiple resources in proportions that you specify
    • Split traffic based on different weights assigned within the record set
    • Example would be sending 10% of user traffic to US-East-1 and the other 90% to US-East-2
  • Latency
    • Use when you have resources in multiple locations and you want to route traffic to the resource that provides the least latency
    • Route traffic based on lowest network latency for your end users, such as sending requests to the region that will give the user the fasted response time
    • Create a resource record set for EC2 or ELB resources in each region that hosts your content. When Route53 receives a request for your content, it selects the latency resource record for the region that gives the user the lowest latency
  • Failover
    • Use when you want to configure active-passive failover
    • Example would be when you want your primary site to be in US-East-1, and a DR site in US-West-1
    • Route53 will monitor the health of our primary site using a health check
    • Health checks are not automatic and must be configured by the user
  • GeoLocation
    • Use when you want to route traffic based on the location of your users
    • Example would be ensuring that EU customers get routed to servers residing in the EU, and ensuring US customers get routed to servers residing in the US
  • Geoproximity
    •  Use to route traffic based on location of resources
    • shift traffic from resources in one location to resources in another.
  • Multivalue answer
    • If Route 53 should respond to DNS queries with up to eight healthy records selected at random.

 

Menu