{"id":9335,"date":"2021-12-01T08:06:18","date_gmt":"2021-12-01T08:06:18","guid":{"rendered":"https:\/\/blog.cloudthat.com\/?p=9335"},"modified":"2024-06-25T11:06:27","modified_gmt":"2024-06-25T11:06:27","slug":"understanding-the-amazon-route-53-application-recovery-controller","status":"publish","type":"blog","link":"https:\/\/www.cloudthat.com\/resources\/blog\/understanding-the-amazon-route-53-application-recovery-controller","title":{"rendered":"Understanding the Amazon Route 53 Application Recovery Controller"},"content":{"rendered":"

AWS has released a new feature under\u00a0<\/span>the\u00a0<\/span>Route 53 umbrella i.e., Route 53 Application Recovery<\/span>\u00a0<\/span>Controller. It is a new AWS service<\/strong>\u00a0<\/span>to help<\/span>\u00a0automatically recover from application and infrastructure failures.\u00a0<\/span>Also<\/span>, it provides true zero-data loss application protection for your cloud-native applications.<\/span>\u00a0<\/span>Today<\/span>, let’s dig a little deeper into\u00a0<\/span>the\u00a0<\/span>Route 53 Application Recovery Controller.<\/span><\/span>\u00a0<\/span><\/p>\n

Table of Contents<\/h2>\n

How does the Route 53 Application Recover controller work?<\/a><\/h1>\n

Capabilities of the Amazon Route 53 Application Recovery Controller<\/a><\/h1>\n

Use cases <\/a><\/h1>\n

Conclusion<\/a><\/h1>\n

About CloudThat<\/a><\/h1>\n

How does the Route 53 Application Recover controller work?<\/h1>\n

The\u00a0<\/span>Route 53 Application Recovery Controller provides a set of capabilities that make it easy for developers to continuously monitor\u00a0<\/span>an\u00a0<\/span>application<\/span>\u2019<\/span>s ability to recover from failures and control\u00a0<\/span>its<\/span>\u00a0recovery across AWS Regions, and AWS Availability Zones.<\/span>\u00a0<\/span>Applications that require high availability and minimal recovery time objectives can benefit from Amazon Route 53 Application Recovery Controller, such as those that use active-active architecture<\/span>.<\/span>\u00a0<\/span>However,<\/span>\u00a0applications that use other redundant architectures may also\u00a0<\/span>benefit<\/span>\u00a0from this<\/span>.<\/span><\/p>\n

Capabilities of the Amazon Route 53 Application<\/h1>\n

Recovery Controller<\/h1>\n

Application replicas are usually deployed redundantly across availability zones within an AWS Region using AWS’ global infrastructure, and traffic is routed to the correct replica using a Network Load Balancer.\u00a0<\/span>It has three different capabilities a Readiness check,\u00a0routing control, and safety rules.<\/span><\/p>\n

\"\"<\/a><\/p>\n

Source:<\/span>\u00a0https:\/\/aws.amazon.com\/route53\/application-recovery-controller\/<\/span><\/span>\u00a0<\/span><\/p>\n

Use cases<\/h1>\n

Readiness check continuously\u00a0monitors AWS resource capacity configurations, AWS quotas, and routing policies, and provides information that you can use to successfully recover from application failure.\u00a0By performing a readiness check, you can make sure that your recovery infrastructure is adequately scalable and configured to handle any eventuality.<\/span>\u00a0<\/span><\/p>\n

One\u00a0example\u00a0is\u00a0the\u00a0AWS service limits, where\u00a0the\u00a0Readiness\u00a0Check makes\u00a0sure that you have enough capacity to deploy in the region where you are falling off.\u00a0So,\u00a0if you don’t have enough capacity to scale\u00a0to lower\u00a0capacity, to\u00a0handle the traffic,\u00a0then your region is not ready.\u00a0In this case,\u00a0it\u00a0will let you know\u00a0that\u00a0the\u00a0region is not ready.<\/span><\/p>\n

    \n
  1. Readiness check\u00a0<\/span><\/span><\/strong><\/strong>continuously monitors AWS resource capacity configurations, AWS quotas, and routing policies, and provides information that you can use to successfully recover from application failure. By performing a readiness check, you can make sure that your recovery infrastructure is adequately scalable and configured to handle any eventuality.<\/li>\n
  2. Routing control<\/span><\/b>\u00a0<\/span>Routing\u00a0controls\u00a0give you\u00a0a\u00a0mechanism or single button switch to route traffic from\u00a0one\u00a0region to another\u00a0region.\u00a0Routing controls ensure that the system remains available during failures by balancing traffic between application replicas.\u00a0Traffic is redirected to application replicas with Amazon Route 53 health checks and DNS resolutions.<\/span>\u00a0<\/span>Amazon Route 53 traditional automated health-check\u00a0based failover can be improved in three ways by routing controls:<\/span>\u00a0<\/span>\n