Construct a resilient Amazon Redshift structure with computerized restoration enabled

Amazon Redshift offers resiliency within the occasion of a single level of failure in a cluster, together with mechanically detecting and recovering from drive and node failures. The Amazon Redshift relocation characteristic provides a further stage of availability, and this put up is concentrated on explaining this computerized restoration characteristic.

When the cluster relocation characteristic is enabled on an RA3 cluster, Amazon Redshift mechanically relocates the cluster in conditions the place points on the Availability Zone stage stop optimum cluster operation, or in case of large-scale failures impacting cluster sources in an information middle inside an Availability Zone. Relocation is completed by creating the cluster’s compute sources in one other Availability Zone. After a cluster is relocated to a different Availability Zone, there isn’t any lack of information and no software modifications are required as a result of the cluster endpoint doesn’t change. This offers a resilient structure to take care of software availability. When a failover is initiated, the precise time to get well depends on the dimensions of a cluster, with the typical time beneath quarter-hour. Observe that the flexibility to relocate is topic to capability availability. Cluster relocation is obtainable at no cost.

The cluster relocation characteristic additionally helps you construct a demonstratable Availability Zone restoration plan in addition to handle capability shortages whereas increasing sources in a given Availability Zone. You may manually transfer the cluster to a different Availability Zone to check your catastrophe restoration plan. In instances the place a cluster can’t be resized or resumed as a consequence of capability shortages in an Availability Zone, you possibly can relocate the cluster to an Availability Zone with extra capability. If the relocation isn’t profitable, the present cluster is left unchanged. The present cluster isn’t eliminated till the brand new cluster is efficiently created as a part of this course of.

Answer overview

Amazon Redshift prospects with operationally delicate purposes require software resiliency within the occasion of an outage in an Availability Zone. The Amazon Redshift relocation characteristic offers software resiliency via an easy-to-use structure with zero lack of information and no software modifications.

The next diagram illustrates the structure earlier than failover

After failover, we now have the next structure

On this put up, we display the right way to allow cluster relocation utilizing both the AWS Administration Console or AWS Command Line Interface (AWS CLI). We stroll via examples of computerized and handbook relocation, additionally present the right way to create a customized relocation resolution utilizing extra AWS companies.


Ensure you have the next conditions:

  • An AWS account.
  • Amazon Redshift clusters created in a VPC with a minimal of two subnets every in several Availability Zone.
  • An Amazon Redshift cluster with a number of Availability Zones configured within the cluster subnet group. You may set one up utilizing the next AWS CloudFormation template.
  • The relocation characteristic is feasible solely with the RA3 Amazon Redshift node kind.
  • Within the Community and safety settings part, select Disable for the Publicly accessible possibility.
See also  How AI/ML Based mostly Functions Powered by Knowledge Annotation Elevate Buyer Experiences

Allow cluster relocation

Step one is to allow cluster relocation, both through the console or AWS CLI. For extra info, see Managing cluster relocation in Amazon Redshift. When utilizing cluster relocation, pay attention to the limitations.

Allow cluster relocation utilizing the console

To allow cluster relocation on the console, full the next steps:

  1. On the Amazon Redshift console, select Clusters.
  2. Edit your cluster.
  3. Below Backup, for Cluster relocation, choose Allow.

Allow cluster relocation utilizing the AWS CLI

The relocation characteristic requires port 5439. In case your present cluster is utilizing a unique port, you need to modify it to make use of 5439 earlier than modifying it to allow relocation. The next command modifies the port in case your cluster doesn’t use 5439:

aws redshift modify-cluster --cluster-identifier mycluster --port 5439

The next command permits the availability-zone-relocation parameter on the Amazon Redshift cluster:

aws redshift modify-cluster --cluster-identifier mycluster --availability-zone-relocation

The next command disables the availability-zone-relocation parameter on the Amazon Redshift cluster:

aws redshift modify-cluster --cluster-identifier mycluster --no-availability-zone-relocation

Computerized Availability Zone relocation

When utilizing relocation in Amazon Redshift, you allow Amazon Redshift to maneuver a cluster to a different Availability Zone with none lack of information or modifications to your purposes. With relocation, you possibly can resume operations when there’s an interruption of service in your cluster with minimal impression. The brand new cluster can have the identical endpoint in order that purposes can proceed operations with out modification.

This characteristic doesn’t require any motion from the consumer apart from the one-time configuration to allow the relocation characteristic. When the restoration characteristic is activated, the vacation spot Availability Zone used is outlined within the cluster subnet group.

Guide Availability Zone relocation

You may set off the relocation manually, relocating a cluster to a different Availability Zone. Full the next steps:

  1. On the Amazon Redshift console, select Clusters within the navigation pane.The clusters in your account within the present Area are listed. A subset of properties of every cluster is displayed in columns within the record.
  2. Select the cluster you need to relocate.
  3. On the Actions menu, select Relocate.If the Relocate possibility is greyed out, that signifies the cluster isn’t configured to make use of the Availability Zone relocation characteristic, or the cluster doesn’t meet the necessities for the relocation characteristic. For extra particulars, consult with Limitations.
  4. Within the Relocate cluster part, for Subnet group, select an Availability Zone.The Availability Zone record is derived from the cluster subnet group. For those who don’t select an Availability Zone, Amazon Redshift chooses one for you.
  5. Select Relocate.
See also  Web3 should be taught from the previous: Individuals with disabilities are the most important untapped demographic

After relocation is initiated, Amazon Redshift begins the relocation and shows the cluster standing as Relocating. When the relocation full, the cluster standing modifications to Out there.

The next screenshot confirms the cluster has relocated to the right Availability Zone.

Customized Availability Zone relocation resolution

On this part, we simulate an computerized cluster failover to a different Availability Zone with a reboot. Our event-based relocation resolution entails organising an alarm with an Amazon Easy Notification Service (Amazon SNS) matter, and creating an AWS Lambda perform to set off the relocation.

Create an alarm

To arrange the alarm, full the next steps:

  1. On the Amazon Redshift console, select Clusters within the navigation pane.
  2. Select your cluster.
  3. On the Cluster efficiency tab, broaden the Alarms part and select Create alarm.
  4. Configure the alarm for the HealthStatus metric and supply an alarm title and outline.
  5. Within the Alarm actions part, for Notifications¸ choose Enabled.
  6. For Notify SNS matter, select an current SNS matter or create a brand new one.This matter receives a notification if the chief node isn’t wholesome or is unavailable.
  7. Select Create alarm.

Create a Lambda perform

To arrange a Lambda perform to set off Availability Zone relocation in case of cluster failure, full the next steps:

  1. On the Lambda console, within the navigation pane, select Features.
  2. Open the Lambda perform created by the CloudFormation stack.
  3. Edit the perform code and modify the next snippet, updating the cluster ID and the vacation spot Availability Zone:
    run_command('/decide/aws redshift modify-cluster --cluster-identifier redshift-cluster-az-relocation --availability-zone us-east-1d')

  4. Select Add set off.
  5. Below Set off configuration, select SNS.
  6. For SNS matter, select the subject you specified in your alarm.
  7. Select Add.

Check the Availability Zone relocation characteristic

Now we are able to take a look at our customized Availability Zone relocation resolution.

  1. On the Amazon Redshift console, select Clusters within the navigation pane.
  2. Select the cluster that you just need to relocate.
  3. On the cluster element web page, observe the cluster identifier.
  4. Use AWS CloudShell to run the next AWS CLI command to search out the present Availability Zone of the Amazon Redshift cluster:
    aws redshift describe-clusters --cluster-identifier redshift-cluster-az-relocation

  5. From the JSON output, search for the attribute AvailabilityZone.
  6. On the cluster element web page, on the Actions menu, select Reboot.
  7. Select Reboot cluster.
    This triggers the alarm, and modifications the alarm state to ALARM.
    Amazon SNS receives a message and triggers the Lambda perform to carry out the cluster relocation to the Availability Zone configured within the code. The cluster relocation takes a number of minutes.
  8. In CloudShell, run the next AWS CLI command to search out the modified Availability Zone of the cluster:
    aws redshift describe-clusters --cluster-identifier redshift-cluster-az-relocation


The cluster relocation characteristic offers the next advantages:

  • You may get well your cluster to a different Availability Zone the place failover could be performed in minutes to make sure enterprise continuity and excessive availability (HA). As well as, Availability Zones are bodily separated sources that let you create a configuration for HA.
  • Amazon Redshift cluster restoration is a one-step course of that will even be automated, versus the handbook course of required to revive a cluster from a snapshot.
  • As a result of Amazon Redshift managed storage already contains the flexibility to copy to 2 different Availability Zones utilizing Amazon Easy Storage Service (Amazon S3), the price of the extra copies is roofed. There are not any extra expenses to make use of this characteristic.
  • The cluster relocation functionality means that you can assist business-critical use instances in your information warehouse requiring HA capabilities. This reduces the possibility of an outage impacting your corporation operations.
  • You may profit from computerized restoration to a failover Availability Zone when there are points in optimum efficiency.
  • Relocation is supplied freed from cost and is topic to capability availability.
See also  Ransomware: Why It’s Time to Consider it as a Knowledge Administration Downside


On this put up, we walked you thru how the automated Availability Zone restoration characteristic in Amazon Redshift helps you construct a resilient trendy information structure. The put up additionally described the right way to carry out a handbook relocation via the AWS administration console. Lastly, we mentioned the right way to implement an event-based relocation utilizing Amazon SNS and Lambda. These numerous strategies might help you intend your failover methods based mostly on your corporation wants.

Concerning the authors

Kevin Burandt is a Senior Supervisor, Options Structure at AWS. He’s enthusiastic about constructing and main technical groups that  assist prospects and companions use know-how to attain enterprise outcomes and ship worth to their prospects. Exterior of labor, he enjoys residence renovation tasks and dealing on traditional automobiles.

Indira Balakrishnan is a Principal Options Architect within the AWS Analytics Specialist SA Group. She is enthusiastic about serving to prospects construct cloud-based analytics options to resolve their enterprise issues utilizing data-driven choices. Exterior of labor, she volunteers at her youngsters’ actions and spends time along with her household.

Ramkumar Nottath is a Sr. Options Architect at AWS specializing in Analytics companies. He enjoys working with numerous prospects to assist them construct scalable, dependable massive information and analytics options. His pursuits lengthen to varied applied sciences resembling analytics, information warehousing, streaming, and machine studying. He loves spending time along with his household and mates.

Tahir Aziz is an Analytics Answer Architect at AWS. He has labored with constructing information warehouses and massive information options for over 13 years. He loves to assist prospects design end-to-end analytics options on AWS. Exterior of labor, he enjoys touring and cooking.

Leave a Reply