Please enable JavaScript.
Coggle requires JavaScript to display documents.
Route 53 - Coggle Diagram
Route 53
Advanced features
-
Health Checks
Features:
- Unhealthy: X health checks failed (default 3)
- Heathy: X health checks passed (default 3)
- Health check interval: default 30s (can set to 10s but higher cost)
- About 15 health checkers will check the endpoint health
- Can have HTTP, TCP and HTTPS health checks (no SSL verification)
- Can integrate health check with CloudWatch
- Health checks can be linked to Route 53 DNS queries
Routing policy
Simple (image)
Features:
- Use when I need to redirect to a single resource
- A random DNS record is chosen by the client (i.e. web browser) if multiple DNS records are returned
-
-
Geolocation
Features:
- Different from Latency routing policy
- Routing based on user location
- Example: Traffic from UK should go to this specific IP
- Can create default policy when there is no match on the location
Latency (image)
Features:
- Redirect to the server that has the least latency close to us
- Latency is evaluated in terms of user to designated AWS Region
Weighted (image)
-
Pros:
- Helpful to split traffic between regions
- Can be associated with Health Checks
Use Cases:
- Helpful to test 1% of traffic on new application version
Multi value
Features:
- Use when routing traffic to multiple resources
- Associate Route 53 Health Checks with each DNS record
- Up to 8 healthy records are returned for each Multi-Value query
- Multi-Value is not a substitute for having an ELB
Geoproximity
Features:
- Route traffic to resources based on the geographic location of users and resources
- Use Bias to shift more traffic to resources
- To expand Bias values (1 to 99) - more traffic to the resource
- To shrink (-1 to -99) - less traffic to the resource
- Resources can be AWS resources (specify AWS region) or Non-AWS resources (e.g. data center)
- Must use Route 53 Traffic Flow (advanced feature) to use Geoproximity
TTL (image)
-
Low TTL
Cons:
- More traffic on DNS
- Higher cost
Pros:
- Records are outdated for less time
- Easy to change DNS records
-
Alias
Features:
- hostname to AWS resource (e.g. app.mydomain.com -> blabla.amazonaws.com)
- Works for ROOT domain (e.g. mydomain.com) and NON-ROOT domain
Pros:
- Free of charge
- Native health check
CNAME
Features:
- hostname to hostname (e.g. app.mydomain.com -> blabla.anything.com
- Only work for NON-ROOT domain (e.g. app.mydomain.com)
-
Most common records:
- A: hostname to IPv4
- AAAA: hostname to IPv6
- CNAME: hostname to hostname
- Alias: hostname to AWS resource
Features:
- Managed DNS
- DNS: Collection of rules and records which helps clients understand how to reach a server through its domain name
- Can use Public domain names (own/ buy)
- Can use Private domain names (can be resolved by my instances in VPCs)
- Global service
- Is also a domain name Registrar (organization that manages the reservation of Internet domain names)