Managing clusters using the console - Amazon Redshift
Creating a clusterModifying a clusterDeleting a clusterRebooting a clusterResizing a clusterUpgrading the release version of a clusterGetting information about cluster configurationGetting an overview of cluster statusCreating a snapshot of a clusterCreating or editing a disk space alarmWorking with cluster performance data
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Managing clusters using the console

To create, modify, resize, delete, reboot, and back up clusters, use the Clusters section in the Amazon Redshift console.

To view clusters

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Clusters. The clusters for your account in the current Amazon Region are listed. A subset of properties of each cluster is displayed in columns in the list. If you don't have any clusters, choose Create cluster to create one.

  3. Choose the cluster name in the list to view more details about a cluster.

Creating a cluster

Before you create a cluster, read Overview of Amazon Redshift clusters and Clusters and nodes in Amazon Redshift.

To create a cluster

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Clusters. The clusters for your account in the current Amazon Region are listed. A subset of properties of each cluster is displayed in columns in the list.

  3. Choose Create cluster to create a cluster.

  4. Follow the instructions on the console page to enter the properties for Cluster configuration.

    Choose one of the following methods to size your cluster:

    Note

    The following step describes an Amazon Redshift console that is running in an Amazon Region that supports RA3 node types. For a list of Amazon Regions that support RA3 node types, see Overview of RA3 node types in the Amazon Redshift Management Guide.

    • If your Amazon Region supports RA3 node types, choose either Production or Free trial to answer the question What are you planning to use this cluster for?

      If your organization is eligible, you might be able to create a cluster under the Amazon Redshift free trial program. To do this, choose Free trial to create a configuration with the dc2.large node type. For more information about choosing a free trial, see Amazon Redshift free trial.

    • If you don't know how large to size your cluster, choose Help me choose. Doing this starts a sizing calculator that asks you questions about the size and query characteristics of the data that you plan to store in your data warehouse.

      If you know the required size of your cluster (that is, the node type and number of nodes), choose I'll choose. Then choose the Node type and number of Nodes to size your cluster for the proof of concept.

  5. Follow the instructions on the console page to enter the properties for Cluster details.

    Note

    If you are behind a firewall, the database port must be an open port that accepts inbound connections.

  6. (Optional) Follow the instructions on the console page to enter properties for Cluster permissions. Provide cluster permissions if your cluster needs to access other Amazon services for you, for example to load data from Amazon S3.

  7. Choose Create cluster to create the cluster. The cluster might take several minutes to be ready to use.

Additional configurations

When you create a cluster, you can specify additional properties to customize it. You can find more details about some of these properties in the following list.

Virtual private cloud (VPC)

Choose a VPC that has a subnet group. After the cluster is created, the subnet group can't be changed.

Parameter groups

Choose a cluster parameter group to associate with the cluster. If you don't choose one, the cluster uses the default parameter group.

Encryption

Choose whether you want to encrypt all data within the cluster and its snapshots. If you leave the default setting, None, encryption is not enabled. If you want to enable encryption, choose whether you want to use Amazon Key Management Service (Amazon KMS) or a hardware security module (HSM), and then configure the related settings. For more information about encryption in Amazon Redshift, see Amazon Redshift database encryption.

  • KMS

    Choose Use Amazon Key Management Service (Amazon KMS) if you want to enable encryption and use Amazon KMS to manage your encryption key. Also, choose the key to use. You can choose a default key, a key from the current account, or a key from a different account.

    Note

    If you want to use a key from another Amazon account, then enter the Amazon Resource Name (ARN) for the key to use. You must have permission to use the key. For more information about access to keys in Amazon KMS, see Controlling access to your keys in the Amazon Key Management Service Developer Guide.

    For more information about using Amazon KMS encryption keys in Amazon Redshift, see Database encryption for Amazon Redshift using Amazon KMS.

  • HSM

    Choose HSM if you want to enable encryption and use a hardware security module (HSM) to manage your encryption key.

    If you choose HSM, choose values from HSM Connection and HSM Client Certificate. These values are required for Amazon Redshift and the HSM to form a trusted connection over which the cluster key can be passed. The HSM connection and client certificate must be set up in Amazon Redshift before you launch a cluster. For more information about setting up HSM connections and client certificates, see Encryption for Amazon Redshift using hardware security modules.

Maintenance track

You can choose whether the cluster version used is the Current, Trailing, or sometimes Preview track.

Monitoring

You can choose whether to create CloudWatch alarms.

Configure cross-region snapshot

You can choose whether to enable cross-Region snapshots.

Automated snapshot retention period

You can choose the number of days to retain these snapshots within 35 days. If the node type is DC2 or DS2, you can choose zero (0) days to not create automated snapshots.

Manual snapshot retention period

You can choose the number of days or Indefinitely to retain these snapshots.

Modifying a cluster

When you modify a cluster, changes to the following options are applied immediately:

  • VPC security groups

  • Publicly accessible

  • Admin user password

  • HSM Connection

  • HSM Client Certificate

  • Maintenance detail

  • Snapshot preferences

Changes to the following options take effect only after the cluster is restarted:

  • Cluster identifier

    Amazon Redshift restarts the cluster automatically when you change Cluster identifier.

  • Enhanced VPC routing

    Amazon Redshift restarts the cluster automatically when you change Enhanced VPC routing.

  • Cluster parameter group

If you decrease the automated snapshot retention period, existing automated snapshots whose settings fall outside of the new retention period are deleted. For more information, see Amazon Redshift snapshots.

For more information about cluster properties, see Additional configurations.

To modify a cluster

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Clusters.

  3. Choose the cluster to modify.

  4. Choose Edit. The Edit cluster page appears.

  5. Update the cluster properties. Some of the properties you can modify are:

    • Cluster identifier

    • Snapshot retention

    • Cluster relocation

    To edit settings for Network and security, Maintenance, and Database configurations, the console provides links to the the appropriate cluster details tab.

  6. Choose Save changes.

Deleting a cluster

If you no longer need your cluster, you can delete it. If you plan to provision a new cluster with the same data and configuration as the one you are deleting, you need a manual snapshot. By using a manual snapshot, you can restore the snapshot later and resume using the cluster. If you delete your cluster but you don't create a final manual snapshot, the cluster data is deleted. In either case, automated snapshots are deleted after the cluster is deleted, but any manual snapshots are retained until you delete them. You might be charged Amazon Simple Storage Service storage rates for manual snapshots, depending on the amount of storage you have available for Amazon Redshift snapshots for your clusters. For more information, see Shutting down and deleting clusters.

To delete a cluster

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Clusters.

  3. Choose the cluster to delete.

  4. For Actions, choose Delete. The Delete cluster page appears.

  5. Choose Delete cluster.

Rebooting a cluster

When you reboot a cluster, the cluster status is set to rebooting and a cluster event is created when the reboot is completed. Any pending cluster modifications are applied at this reboot.

To reboot a cluster

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Clusters.

  3. Choose the cluster to reboot.

  4. For Actions, choose Reboot cluster. The Reboot cluster page appears.

  5. Choose Reboot cluster.

Resizing a cluster

When you resize a cluster, you specify a number of nodes or node type that is different from the current configuration of the cluster. While the cluster is in the process of resizing, you cannot run any write or read/write queries on the cluster; you can run only read queries.

For more information about resizing clusters, including walking through the process of resizing clusters using different approaches, see Resizing clusters in Amazon Redshift.

To resize a cluster

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Clusters.

  3. Choose the cluster to resize.

  4. For Actions, choose Resize. The Resize cluster page appears.

  5. Follow the instructions on the page. You can resize the cluster now, once at a specific time, or increase and decrease the size of your cluster on a schedule.

  6. Depending on your choices, choose Resize now or Schedule resize.

If you have reserved nodes, for example DS2 reserved nodes, you can upgrade to RA3 reserved nodes. You can do this when you use the console to restore from a snapshot or to perform an elastic resize. You can use the console to guide you through this process. For more information about upgrading to RA3 nodes, see Upgrading to RA3 node types.

Upgrading the release version of a cluster

You can upgrade the release maintenance version of a cluster that has a Release Status value of New release available. When you upgrade the maintenance version, you can choose to upgrade immediately or upgrade in the next maintenance window.

Important

If you upgrade immediately, your cluster is offline until the upgrade completes.

To upgrade a cluster to a new release version

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Clusters.

  3. Choose the cluster to upgrade.

  4. For Actions, choose Upgrade cluster version. The Upgrade cluster version page appears.

  5. Follow the instructions on the page.

  6. Choose Upgrade cluster version.

Getting information about cluster configuration

To display information about a cluster

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Clusters, then choose the cluster name from the list to open its details. The details of the cluster are displayed, which can include Cluster performance, Query monitoring, Databases, Datashares, Schedules, Maintenance, and Properties tabs.

  3. Choose each tab to view more details.

Getting an overview of cluster status

To view the status of a cluster

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Clusters.

  3. View the status of the cluster in the Status column.

Creating a snapshot of a cluster

To create a snapshot of a cluster

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Clusters.

  3. Choose the cluster for which to create a snapshot.

  4. For Actions, choose Create snapshot. The Create snapshot page appears.

  5. Follow the instructions on the page.

  6. Choose Create snapshot.

Creating or editing a disk space alarm

To create a disk space usage alarm for a cluster

  1. Sign in to the Amazon Web Services Management Console and open the Amazon Redshift console at https://console.amazonaws.cn/redshift/.

  2. On the navigation menu, choose Alarms.

  3. For Actions, choose Create alarm. The Create alarm page appears.

  4. Follow the instructions on the page.

  5. Choose Create alarm.

Working with cluster performance data

In the console, you can work with cluster performance on the Cluster performance tab of the cluster details page.