Introduction Amazon Application Recovery Controller Region Switch: Renewal Service for Multiple Regions | Amazon Web Services

As an AWS developer, the way we produced with many corporate organizations that operate critical across several AWS regions. The key problem they often share is the lack of confidence in the strategy of taking services of services in the region – Ulick will work, whether all addictions have been identified and where their teams have sufficient procedures. Traditional approaches often leave them uncertain about their readiness for a regional switch.

Today I am enthusiastic that I can announce Amazon Application Recovery Controller (ArC) Switch, a fully managed, highly available ability that allows organizations to plan, practice and organize regions with confidence and eliminate uncertainty around the cross -country renewal operations. The Switch Region will help you orchestrate your applications for multiple AWS regions. It provides you with a centralized solution for coordination and automation of renewal renewal tasks and AWS accounts if you need to switch the application operations from one AWS area to another.

Many customers deploy business criticism across several AWS AWS regions to meet their available requirements. If an operation event affects the application in one region, switching operations to another record includes multiple steps across AWS, such as Compute, Databases and DNS. This coordination usually requires building and maintaining complex scripts that require regular testing and updates as the application evolves. In addition, it orchestrates and monitoring the procedure of regions switches across multiple applications and providing evidence of successful recovery for compliance purposes often includes manual data collection.

The region switch is built on the regional data plane architecture, where the regional switches are carried out from the area activation. This proposal eliminates the impact dependence during the switch, which provides a more resistant recovery process, as the implementation is independent of the region from which you switch.

Building a renewal plan using the Arc area switch
With the Arc Region switch, you can create renewal plans that define the specific steps needed to switch the application between regions. Each plan contains implementing blocks that take action on AWS sources. When starting, the Switch region supports nine types of implementing blocks:

• Arc Région Switch Plan Plan Plan Block – Let you organize an orchestra in which multiple applications move to the area you want to activate, link to plans to switch other regions.
• AMAZON EC2 Automatic scaling of block execution – AMAZON EC2 PC Sources in your target area by adapting a specific percentage of the capacity of your source area.
• Control elements Arc block execution – changes in routing controls for redirecting traffic by DNS health checks.
• Amazon Aurora Global Database Implementing Block – Acceptance of Services Services Services in Database Failure with Potential Loss of Data or Switching with zero data for global database Aurora.
• Manual approval block – adds checkpoints in your renewal workflow where team members can check and approve before the procedure.
• Own action AWS LAMBDA BLOCK – adds its own steps to restore Lambda functions in the field of activation or deactivation.
• Amazon Route 53 Health Check Block – you determine which regions will be redirected by the operation of your application during the receipt of services during failure. When carrying out the region switch plan, the Amazon Route 53 Health Check status is updated and the operation is redirected to your DNS configuration.
• Amazon Elastic Kubernetes Service (Amazon EKS) Scaling Resoning Scaling Block – Kubernetes under your destination during recovery comparing a specific percentage of the capacity of your source area.
• Amazon Elastic Container Service (AMAZON ECS) – ECS tasks in your target Région by comparing the specific percentage of the capacity of your source area.

The region switches your plans to control resource and AWS identity and access management (IAM) for 30 minutes. During the Switch region, it monitors the progress of every step and provides detailed protocols. You can view the condition of the execution via the control panel for switching the region and at the bottom of the details of the design.

To help you balance costs and boundability, the Switch region offers flexibility in how you prepare your emergency resources. During recovery, you can configure the required percentage of computing capacity for targeting in your target area using blocks of the region’s scale. For critical applications that expect overvoltage during recovery, you may decide to expand above 100 capacity, and lower percentage settings can help achieve faster overall execution. However, it is important to note that the use of one of the blocks of scaling does not guarantee capacity and the actual availability of resources depends on the capacity in the target area at the time of recovery. To make it easier to make the best possible results, we recommend testing your renewal and maintenance plans for appropriate service quotas in your standby regions.

The ARC Region switches included a global pad that you can use to monitor the status of the region switch across the company and regions. In addition, there is a regional executive control panel that only shows execution in the current console area. This control panel is designed to be highly available in each region so that an operational event can be used.

The Switch Region allows you to host resources on an account that is separated from an account that contains a regional switch plan. If the plan uses the sources from the birthday that differs from the account host, then the region switch executionRole assume crossAccountRole Access to these sources. In addition, the regional switch plans can be centralized and shared on multiple accounts using AWS Resource Access Manager (AWS RAM), allowing effective recovery management throughout your organization.

We’ll see that it works
Let me show you how to create and make a switch plan. There are these parts in this demo. First I create a region switch plan. Then I define the workflow. Finlly, I configure the triggers.

Step 1: Create a plan

I will go to the section of the AWS Management Console Recovery controller. I choose Switch In the left navigation offer. Then I choose Create a schedule of the region switches.

After I make the name of my plan, I am specific to Access to recover with multiple regions (Active/passive gold active/active). In active/passive mode, two replicas of applications are deployed to two regions, while the transport route only to the active area. The replica in the passive area can be activated by the execution plan of the region switch.

Then I select Primary area and Emergency area. Optionally I can enter a Required Time of Recovery (RTO). The service will use this value to provide a look at how long the region switch takes the RTO required in my desired RTO.

I will enter A plan to perform roles. This is a role that allows the AWS calling regions to call the AWS. I assure myself that the role we choose has permission to be induced by the service and contains a minimum set of permissions that allows the ARC circuit. Return to the IAM section of the documentation for details.

Step 2: Create a workflow

When the two Status Evaluation Plan The announcements are green, I create a workflow. I choose Create workflows Start.

Plans allow you to create specific workflows that will restore your applications using the region switch. You can build workflows with implementing blocks that run Sequementelly or in parallel with an orchestration of the order in which multiple applications or resources are recovering into the activation area. The plan consists of these workflows that allow you to activate or deactivate a specific area.

For this demo I use a graphic editor to create a workflow. But you can also define a workflow in JSON. This format is more suitable for automation or if you want to save the workflow definition to the source code management system (SCMS) and your infrastructure as code (IAC) tools such as Cloudformation AWS.

Can i alternate between Design and Code View by selecting the corresponding card next to The creator of the workflow Title. The view is read. I suggested a workflow with a graphic editor and copied the equivalent of JSON to save it together with my IAC project.

The Switch region launches the rating to verify the renewal strategy every 30 minutes. It regularly checks that all actions defined in your workflows will be successful after completion. This proactive evaluation of verification of different elements included IAM authorization and resource statistics across accounts and regions. By constantly monitoring these addictions, the Switch region helps to ensure that your recovery plans remain viable and identify potential problems before your real switching operations affect.

However, as well as an intact deposit is not a reliable backup, the recovery plan cannot be considered truly verified. While continuous evaluation provides a strong foundation, we strongly recommend that you regularly implement your plans in testing scenarios to verify their effectiveness, understand the real recovery time and ensure that your teams are familiar with the recovery process. This practical testing is essential for maintenance confidence in the restoration strategy after the disaster.

Step 3: Create a trigger

The trigger defines the conditions for activating the workflows just created. It is express as a set of cloudwatch alarm. Alarm triggers are optional. You can also use the region with manual triggers.

I will choose from the Region Switches Page in the console Triggers card and choose Add triggers.

I will choose for each area defined in my plan Add the trigger Define triggers that activate the area.Finally, I choose alarms and their condition (OK or alarm), which the region switch will use the area activation.

Now I should test the plan to switch regions using the region switch. It is important to make a plan from the area I activate (target area of workflow) and use the data plane in this particular area.

Here’s how to make a plan using the AWS command line (AWS CLI) interface:

aws arc-region-switch start-plan-execution \
--plan-arn arn:aws:arc-region-switch::111122223333:plan/resource-id \
--target-region us-west-2 \
--action activate

Prices and availability
The Switch region is available in all AWS commercial regions for $ 70 per month for a plan. Each plan can include up to 100 performances, or you can create maternity plans for organizing up to 25 children’s plans.

After I saw first -hand engineering epform, which goes into building and ongoing resumption solutions, I am excited to see how the Switch region will help automate this process for our customers. If you want to start with the Arc Region switch, visit the ARC console to create your first region switches. For more information about the Switch region, see Amazon Application Recovery Controller (ARC). You can also address your AWS native team with questions about using the Switch region for your applications for multiple regions.

I look forward to seeing how you use the region switch to strengthen the resistance of multiple regions.

– seb