User guide

You might rename a cluster if you want to change the cluster to which your applications connect without

having to change the endpoint in those applications. In this case, you must first rename the original cluster

and then change the second cluster to reuse the name of the original cluster prior to the rename. Doing

this is necessary because the cluster identifier must be unique within your account and region, so the

original cluster and second cluster cannot have the same name .You might do this if you restore a cluster

from a snapshot and don’t want to change the connection properties of any dependent applications.

Note

If you delete the original cluster, you are responsible for deleting any unwanted cluster snapshots.

When you rename a cluster, the cluster status changes to renaming until the process finishes. The old

DNS name that was used by the cluster is immediately deleted, although it could remain cached for a

few minutes. The new DNS name for the renamed cluster becomes effective within about 10 minutes.

The renamed cluster is not available until the new name becomes effective. The cluster will be rebooted

and any existing connections to the cluster will be dropped. After this completes, the endpoint will change

to use the new name. For this reason, you should stop queries from running before you start the rename

and restart them after the rename finishes.

Cluster snapshots are retained, and all snapshots associated with a cluster remain associated with that

cluster after it is renamed. For example, suppose you have a cluster that serves your production database

and the cluster has several snapshots. If you rename the cluster and then replace it in the production

environment with a snapshot, the cluster that you renamed will still have those existing snapshots

associated with it.

Amazon CloudWatch alarms and Amazon Simple Notification Service (Amazon SNS) event notifications

are associated with the name of the cluster. If you rename the cluster, you need to update these

accordingly.You can update the CloudWatch alarms in the CloudWatch console, and you can update

the Amazon SNS event notifications in the Amazon Redshift console on the Events pane.The load and

query data for the cluster continues to display data from before the rename and after the rename. However,

performance data is reset after the rename process finishes.

For more information, see Modifying a Cluster (p. 20).

Shutting Down and Deleting Clusters

You can shut down your cluster if you want to stop it from running and incurring charges. When you shut

it down, you can optionally create a final snapshot. If you create a final snapshot, Amazon Redshift will

create a manual snapshot of your cluster before shutting it down.You can later restore that snapshot if

you want to resume running the cluster and querying data.

If you no longer need your cluster and its data, you can shut it down without creating a final snapshot. In

this case, the cluster and data are deleted permanently. For more information about shutting down and

deleting clusters, see Shutting Down or Deleting a Cluster (p. 22).

Regardless of whether you shut down your cluster with a final manual snapshot, all automated snapshots

associated with the cluster will be deleted after the cluster is shut down. Any manual snapshots associated

with the cluster are retained. Any manual snapshots that are retained, including the optional final snapshot,

are charged at the Amazon Simple Storage Service storage rate if you have no other clusters running

when you shut down the cluster, or if you exceed the available free storage that is provided for your

running Amazon Redshift clusters. For more information about snapshot storage charges, go to the

Amazon Redshift pricing page.

API Version 2012-12-01

Amazon Redshift Management Guide

Shutting Down and Deleting Clusters