Route 53 is the domain name management service provided by AWS that provides us with further opportunities to make our environment highly available & fault tolerant.
Route 53 can be used to send traffic to Cloudfront, ELB, EC2, RDS or S3 instances and can be used both externally (i.e. domain name on the internet) and internally (custom hostnames within a VPC).
Route 53 has a number of different routing options:
|Simple||Route to a single endpoint like an EC2 instance|
|Weighted||Send a certain % of traffic to one end point and the rest to another. Very useful when migrating from on-premise to AWS as you can test on small amounts of traffic & gradually ramp up.|
|Latency||Will choose from a selection of endpoints, based on the users latency to each end point.|
|Failover||If an instance goes down, Route53 can route to a secondary (backup) endpoint, such as S3. To use S3 as an end point, the bucket name must be the same as the domain name. Remember: you must set ‘evaluate target health’ to yes on the primary record.|
|Geo||Will choose from a selection of endpoints, based on the users distance from each end point.|
Each domain has its own ‘hosted zone’ within AWS and will be prepopulated with nameserver records (NS) and Start Of Authority (SOA) records.
When setting up your routing, you can utilize service aliases (for ELB, Cloudfront, Elastic Beanstalk and S3 buckets) within AWS. For example, you can simply refer to your ELB’s alias, rather than specific IPs or hostnames. This is just a much simpler way to manage your domain name.