Please enable JavaScript.
Coggle requires JavaScript to display documents.
Route 53 Routing Policies for DNS Entries (Failover Policy (exactly two…
Route 53 Routing Policies for DNS Entries
Simple Routing Policy
one domain entry
multiple IPs possible
returns mapped ips in random order
is random
Weighted Routing Policy
multiple entries
more or one ip mapping
set a weight for the entry!
route 20% of traffic to ips in entry a
route 80% of traffic to ips in entry b
entries have the same name
weight value 0..255
calc Grundwert GW = sum(all weights). Calc for each Prozentsatz = (weight/GW)*100
Creation of Policies
Within Create Entry choose Policy Type
Health Check
when failed removes entry from Route 53
can be defined for every routing policy type except Simple Routing
when HC succeeds entry will be available to choose from
Can send SNS Notification alter if failed
Latency Based
automatically routes to the entry with lowest latency
can have health check
multiple entries with one IP
entries have the same name
Failover Policy
exactly two entries
one entry for primary
one entry for secondary
if health check for primary failed automatically switch to secondary
primary needs Health Check
entries have the same name
Geolocation Routing Policy
choose entry regarding geolocation of user that calls
really for differences of your product for geolocations
not for latency aspects
more entries with multiple ips per entry
entries have the same name
establish a default route for "everything else"
Geoproximity Routing Policy
Routes according geolocation and resources
very complex rules possible
have to use TrafficFlow
Like Workflow Tool for Routing Rules
very complex flows possible
e.g. used to route between two regions in the same geolocation for a location
you are nearer to us-west than us-east --> us-west
but can put a Bias in to enlarge the radius for us-east ==> us-east
MultiValue Answer Policy
Same as Simple Routing Policy
But can have Health Checks
But can have multiple entries (Health Checks)
Still is random
entries have the same name
same name with multiple IP Adresses
ALIAS
Mapping to another name (like CNAME)
Can have more than one mapping with same name (unlike CNAME)
Is AWS specific (NOT Standard DNS)
Allowed on zone apex (on domain itself, unlike CNAME)
CNAME
Just a mapping name to name
can not be used on top level domain