Please enable JavaScript.
Coggle requires JavaScript to display documents.
DNS
Route 53 - Coggle Diagram
DNS
Route 53
Route Policies
Simple
- Simple resource
- It can have multiple values (for example 3 IPs)
- If it returns multiple value the client has to choose one to use
- it doesn't have health check
Weighted
- You control the request using % (70%, 20%, 10%)
- You can't pass 100%
- It has a health check
- The name has to be the same
- It's good for ELB between regions and testing new applications when deploying
- If you set all % to 0, it means that the request is going to send equality
Latency
- Redirect the request to the least latency
- Good for performance and use with clients in different regions on the world
Failover
- Active and Passive
- When you fail the policy is going to send to another way
Geo Location
- Different latency
- Based on user's location
- You can have HC
Geoproximity
- Shift more traffic to the resource based on define bias. Closest region
- divide the user between the region
-
IP Based
- Route based on client's IP address
- You need to provide CICR
Multi-Value
- Route traffic multiple resources
- Can associate with a HC
- 8 HC for each Multi-Value
- This multi-value not substitute ELB
TTL
It's the time that the client cache the DNS response in your own computer. After that time, the client will request the DNS again
High time
- Less traffic
- Outdated records
Low TTL
- more traffic ($$$)
- easy to change the records
Types of health check
Simple Health Check
- Only public resources
- DNS Failover
- Cloud Watch
- You can define threshold, interval, support HTTP/HTTPS/TCP, 18% > is health and only 2xx and 3xx
Calculate Health Check
- Combine many health checks
- Can monitor 256 HC
- You can use OR, AND, NOT
- Parent and Child
Health Check Private Zone
- A normal HC can't access the endpoint because the endpoint is inside the VPC
- So, to make this HC, you need to create some metrics on Cloud Watch and point this HC to the CW. This way you are going to have a HC
-
-
CNAME vs ALIAS
CNAME vs ALIAS
CNAME
- hostname to hostname
- only for non root domain. for example blah.domain.com
ALIAS
- hostname to AWS resources
- works only root domain
- free charge
- health check
- A / AAAA
- Common services used ELB, CF, API Gateway, BeanStalk, S3, VPC, Global Accelerator, route 53 (NOT EC2 DNS NAME)
-
-
-
You can route the traffic using
- Domain / Sub-domain
- Record type
- Value
- Routing Policy
- TTL
- A (IPv4) / AAAA (IPv6) / CNAME / NS / ALIAS
Domain Register
- It's where you can buy a domain on AWS
- You can use domain from another company on AWS