Route 53
Owner | |
---|---|
Verification | |
Tags | |
Last edited time |
Record Types
A | hostname to IPv4 |
AAAA | hostname to IPv6 |
CNAME | hostname to hostname (not root domain) - create Alice recored |
NS | Hosted Zone |
Alias | for AWS resources (ELB. CloudFront, API, S3 - not EC2 ) |
* TTL - mandatory
Routing Policies
Simple - for a single record , no health checks - can specify multiple (random will be chosen)
Weighted - control the % going to specific resource + health checks
Latency - lowest latency from us to the region + health checks - can set failover
Failover (Active - Passive) health checks mandatory
Geolocation - based on user location (location / country) - need to create default for no location
Geo proximity - location of users+resources - can set bias using traffic flow
Multi value - up to 8 records - not ELB
Hosted Zones
Container of records to define how to route traffic coming into you public / private records
Can share private zones using VPC peering
To associate an Amazon VPC and a private hosted zone that you created with different AWS accounts, perform the following procedure:
Health Checks
HTTP for public. for private - use CloudWatch
endpoint monitoring = AWS resource - based value returned
Calculated health check monitoring = other health checks - group health checks into parent
CloudWatch health check = full control (dynamo , RDS)
Resolvers & Hybrid DNS
For hybrid DNS resolving (peered VPC or On Premises) - use Resolver Endpoint :
Inbound Endpoint - to forward DNS queries from external networks to Route 53
Outbound Endpoint -to forward DNS queries to your on premises DNS
Created at the region level in two AZ for HA, up to 10k queries per IP per second
can set Forwarding rules to control forwarding based on rules
Route 53 Resolver
create private DNS resolution