AWS Releases Amazon Route 53 Application Recovery Controller into General Availability

 Recently, AWS announced the overall availability (GA) of Amazon Route 53 Application Recovery Controller, a further new set of capabilities in Amazon Route 53. With the capabilities, it'll be easier for patrons to continuously monitor their applications’ ability to get over failures and control their recovery across AWS Regions, Availability Zones, and on-premises infrastructure.

Typically, with their global infrastructure AWS provides the power for patrons to deploy application replicas redundantly across AWS Availability Zones inside an AWS Region – and leverage a Network or Application Load Balancer to route traffic to the acceptable replica. However, some customers have even more demanding requirements for top availability for his or her workloads and wish an availability rate of 99.99% or above with recovery time objectives (RTO) measured in seconds or minutes. to satisfy such requirements, deploying multiple replicas across various AWS Availability Zones, AWS Regions, and on-premise environments combined with Amazon Route 53 is an option. The latter will route end-users to the acceptable replica reliably.

In an AWS News blog post on the GA release of Amazon Route 53 Application Recovery Controller, Sébastien Stormacq, a principal developer advocate at AWS, explains:

    Amazon Route 53 Application Recovery Controller helps you to create these applications requiring very high availability and low RTO, typically those using active-active architectures, but other sorts of redundant architectures may additionally  enjoy Amazon Route 53 Application Recovery Controller. it's made from two parts: readiness check and routing control.

The readiness checks continuously monitor AWS resource configurations, capacity, and network routing policies and permit users to watch any changes that might affect the power to execute a recovery operation. Moreover, the checks will make sure that the recovery environment is scaled and configured to require over when needed. Secondly, the routing controls help to rebalance traffic across application replicas during failures to make sure that the appliance stays available. Finally, these controls work with Amazon Route 53 health checks to redirect traffic to an application replica, using DNS resolution.

Other public cloud vendors also provide similar capabilities as Amazon Route 53 and therefore the new Application Recovery Controller. Microsoft, as an example, has two services:

•    Azure DNS, including domain and DNS management, and
•    Traffic Manager that gives DNS level traffic routing, load balancing, and failover capabilities