Amazon Redshift launches the ability to easily move clusters between AWS Availability Zones (AZs)
Amazon Redshift, the most widely used data warehouse, now offers the ability to move an Amazon Redshift cluster to another AWS Availability Zone (AZ). The cluster relocation feature moves a cluster to another AZ in one step without requiring application changes. You can invoke the relocation function in cases where resource constraints in a given AZ are disrupting cluster operations such as the ability to resume or resize a cluster. This feature is available for use on clusters leveraging the RA3 instance family and is offered at no additional cost.
Amazon Redshift, the most widely used data warehouse, now offers the ability to move an Amazon Redshift cluster to another AWS Availability Zone (AZ). The cluster relocation feature moves a cluster to another AZ in one step without requiring application changes. You can invoke the relocation function in cases where resource constraints in a given AZ are disrupting cluster operations such as the ability to resume or resize a cluster. This feature is available for use on clusters leveraging the RA3 instance family and is offered at no additional cost.
Amazon Redshift provides resiliency in the event of a single point of failure in a cluster including automatically detecting and recovering from drive and node failures. The relocation feature will add additional levels of availability in cases where AZ level issues are preventing optimal cluster operations. You can enable the ability to relocate your cluster by modifying your cluster configuration settings in the Amazon Redshift console, API or CLI. When a cluster is moved to another AZ, the new cluster will have the same endpoint so that applications can continue operations without modification. You can easily execute a relocation of your cluster using the Amazon Redshift console, API, or CLI. When the cluster relocation capability is enabled, Amazon Redshift will also relocate your cluster in situations where AZ level issues prevent optimal cluster operation.
This feature is available for use on clusters leveraging the RA3 instance family. The RA3 instance family supports separation of compute and storage resources that enables several key features including relocation since compute resources can now be relocated to a new AZ and leverage a consistent copy of the cluster’s data in Redshift Managed Storage (RMS).
Cluster relocation capability is available in all commercial regions where the RA3 instance type is supported.