Let us take a closer look and discuss, Active active failover vs Active Passive Failover AWS with the support of AWS support Services at Bobcares.

What is Amazon Route 53 health check?

Route 53 health checks are a feature that allows us to monitor the health of certain AWS resources or any endpoint that can react to requests.

The checks can offer notifications when the state of the health check changes and can assist Route 53 in recognizing when a record points to an unhealthy resource, allowing Route 53 to failover to another record.

Route 53 health checks can configure active-active and active-passive failover topologies. Any routing policy (or combination of routing policies) other than failover can configure active-active failover, and the failover routing policy can configure the active-passive failover.

Active-active failover

If we want all of the resources to be available most of the time, we can utilize this failover setup. When a resource becomes unavailable, Route 53 can detect this and stop using it to respond to queries.

All records with the same name, type (such as A or AAAA), and routing policy (such as weighted or latency) are active in active-active failover unless Route 53 considers them unhealthy. Any healthy record can respond to a DNS query via Route 53.

Active-passive failover

When we want a primary resource or set of resources to be available most of the time and a secondary resource or group of resources to be on standby in case all of the primary resources become unavailable, we use an active-passive failover arrangement.

Route 53 only responds to queries with healthy principal resources. If all of the primary resources are sick, Route 53 begins to respond to DNS queries with only the healthy secondary resources.

Route 53 active-passive vs active-active failover

The fundamental distinction between the two architectures is when the architecture is operational. During regular operation, we have access to all resources thanks to active-active failover.

In an active-passive failover, backup resources are normally in a standby state and only observe operations during the failover.

Active-active failover

When we want all app nodes in all regions to be available at the same time, we employ active-active failover. When we want all of the resources to be available most of the time, we use this failover setup.

Active-passive failover

When we want a primary resource or set of resources to be available most of the time and a secondary resource or group of resources to be on standby in case all of the primary resources become unavailable, we can utilize an active-passive failover arrangement.

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude we have now gone through the active active failover vs active passive failover AWS. With the support of our AWS support services at Bobcares, we have learned more about both and the differences between the two to get a clear picture of active active failover and Active passive failover.