Content Delivery and DNS Services
Amazon Route 53
Route 53 is the AWS Domain Name Service.
Route 53 performs three main functions:
- Domain registration – Route 53 allows you to register domain names.
- Domain Name Service (DNS) – Route 53 translates name to IP addresses using a global network of authoritative DNS servers.
- Health checking – Route 53 sends automated requests to your application to verify that it’s reachable, available and functional.
You can use any combination of these functions.
Route 53 benefits:
- Domain registration.
- DNS service.
- Traffic Flow (send users to the best endpoint).
- Health checking.
- DNS failover (automatically change domain endpoint if system fails).
- Integrates with ELB, S3, and CloudFront as endpoints.
Routing policies determine how Route 53 DNS responds to queries.
The following table highlights the key function of each type of routing policy:
CloudFront is a content delivery network (CDN) that allows you to store (cache) your content at “edge locations” located around the world.
This allows customers to access content more quickly and provides security against DDoS attacks.
CloudFront can be used for data, videos, applications, and APIs.
- Cache content at Edge Location for fast distribution to customers.
- Built-in Distributed Denial of Service (DDoS) attack protection.
- Integrates with many AWS services (S3, EC2, ELB, Route 53, Lambda).
Origins and Distributions:
- An origin is the origin of the files that the CDN will distribute.
- Origins can be either an S3 bucket, an EC2 instance, an Elastic Load Balancer, or Route 53 – can also be external (non-AWS).
- To distribute content with CloudFront you need to create a distribution.
- There are two types of distribution: Web Distribution and RTMP Distribution.
CloudFront uses Edge Locations and Regional Edge Caches:
- An edge location is the location where content is cached (separate to AWS regions/AZs).
- Requests are automatically routed to the nearest edge location.
- Regional Edge Caches are located between origin web servers and global edge locations and have a larger cache.
- Regional Edge caches aim to get content closer to users.
The diagram below shows where Regional Edge Caches and Edge Locations are placed in relation to end users:
Also in AWS Certified Cloud Practitioner Training Notes:
- Cloud Computing Concepts
- AWS Global Infrastructure
- Identity and Access Management
- Elastic Load Balancing and Auto Scaling
- Monitoring and Logging Services
- Notification Services
- Billing and Pricing
- Cloud Security
- Shared Responsibility Model
- Architecting for the Cloud
- Additional Services and Tools