What could be happening?
(Choose two.)
Latency resource record sets cannot be used in combination with weighted resource record sets.
You did not setup an HTTP health check to one or more of the weighted resource record sets associated with me disabled web servers.
The value of the weight associated with the latency alias resource record set in the region with the disabled servers is higher than the weight for the other region.
One of the two working web servers in the other region did not pass its HTTP health check.
You did not set “Evaluate Target Health” to “Yes” on the latency alias resource record set associated with example com in the region where you disabled the servers.
Explanations:
Latency-based routing can be combined with weighted records, and Route 53 will choose based on latency first, then apply weights.
Without an HTTP health check on weighted records, Route 53 cannot determine server health, so it may still route traffic to them.
Latency-based routing prioritizes latency, not weights; weights apply only among records within a latency set for a specific region.
Even if one server fails a health check, other healthy servers in the region should still be available to receive traffic.
Setting “Evaluate Target Health” to “Yes” enables Route 53 to route traffic to other regions if no healthy resources are available.
If memory serves me right, the answer is:
You did not setup an HTTP health check to one or more of the weighted resource record sets associated with me disabled web servers.