Core Functionality and Limitations
Amazon Route 53's primary role is DNS-based routing, enabling traffic management for domains, but it has specific limitations regarding content delivery.
Amazon Route 53 primarily provides DNS-based routing. This service is fundamental for directing internet traffic to various AWS resources.
Route 53 offers Geoproximity routing, which provides DNS routing based on the geographic location of users and resources.
Route 53 does not reduce latency or deliver cached content for streaming. Its role is solely DNS resolution and routing, not content delivery network (CDN) functionality.
While Route 53 Geoproximity provides DNS routing capabilities, it explicitly does not cache or accelerate content delivery.
Configuring a Custom Domain
procedure
Route 53 is utilized to configure custom domains, connecting them to AWS resources like Elastic Beanstalk environments.
The process to set up a custom domain involves registering a domain, creating a hosted zone, and configuring CNAME records.
Prerequisites
- An existing domain or a domain to be registered.
- An AWS resource (e.g., Elastic Beanstalk environment) to point the custom domain to.
1
Register a new domain or use an existing one (e.g., quiz.yourdomain.com).
A domain name is a prerequisite for using Route 53 to manage traffic.
2
Create a hosted zone in Route 53 for the specified domain.
A hosted zone serves as a container for all the DNS records that define how traffic should be routed for your domain.
3
Add a CNAME record within the hosted zone.
The CNAME record maps an alias (like 'quiz') to the canonical domain name of your AWS resource (e.g., an Elastic Beanstalk environment URL).
Name: quiz
Type: CNAME
Value: saa-quiz-production.us-east-1.elasticbeanstalk.com