Latency-based routing is configured at the record level in the Route 53 console. AWS calculates the delay, or latency, over the Internet from the requesting device to the endpoint in the AWS cloud. However, latency-based routing does not calculate the application’s delay such as the latency inherent in a database or backend application. Select the record you want to apply the policy to in the AWS Route 53 hosted zone console. The basic record detail parameters will appear on the right pane; click Edit Record to configure the policy. In the Routing Policy drop-down box, select Latency, fill out the fields for the region, and configure health checking if desired and the ID, which can be anything you choose to define, as shown in Figure 3.7.
FIGURE 3.7 Traffic latency-based routing
In the AWS Route 53 hosted zone console, select the record you want to apply the geo policy to and begin the configuration process. The basic record detail parameters will appear on the right pane; click Edit record to configure the policy. In the Routing Policy drop-down box, select geolocation and fill out the location you are allowing to access this record. The selections can be continent, country, or for the United States, the state, as shown in Figure 3.8. When you are done configuring the policy, it will take effect immediately.
FIGURE 3.8 Geolocation routing
Select the record you want to apply the weighted policy to in the AWS hosted zone console. The basic record detail parameters will appear on the right pane; click Edit Record to configure the policy. In the Routing Policy drop-down box, select Weighted and fill out the weight to assign this record. You will need to fill out multiple records and assign different weights to them since using a single weighted policy would still direct 100 percent of the traffic to that endpoint. Figure 3.9 shows the weighted-based routing configuration dialog box.
FIGURE 3.9 Weighted-based routing
As you learned in Chapter 2, failover routing policies will direct all traffic to the primary location by serving its IP address as long as it is passing health checks. Should the endpoint stop responding to health checking, a failover will be triggered, and the policy will then begin sending the backup device’s IP address in response to DNS queries.
Select the record you want to apply the failover policy to in the AWS hosted zone console. The basic record detail parameters will appear on the right pane; next click Edit Record to configure the policy. In the Routing Policy drop-down box, select Failover Type and the health check policy to be used; then select if you want this record to be the Primary or Secondary endpoint, as shown in Figure 3.10. If the primary should fail, then Route 53 will serve the failover endpoint’s IP address.
FIGURE 3.10 Failover-based routing
Multivalue records are similar to simple routing except that you fill out multiple IP addresses, as shown in Figure 3.11. Route 53 will then send out all of the IP addresses in response to a DNS query, and the requesting device will select one from the list to use to initiate the connection. This feature is often used to distribute connections across multiple endpoints without having to implement a load balancer.
Acedexam Training Policies
Learning resources
Other resources
Our Training Providers
