Menu
Amazon Redshift
Management Guide (API Version 2012-12-01)

Managing Clusters Using the Console

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

When you don't have any clusters in a region and you navigate to the Clusters page, you see an option to launch a cluster. In the following screenshot, the region is the US East (N. Virginia) Region and there are no clusters for this account.

When you have at least one cluster in the region that you have selected, the Clusters section displays a subset of information about all the clusters for the account in that region. In the following screenshot, there is one cluster created for this account in the selected region.

You can expand the cluster to view more information about the cluster, such as the endpoint details, cluster and database properties, tags, and so on. In the following screenshot, examplecluster is expanded to show a summary of information about the cluster.

Creating a Cluster

Before you create a cluster, review the information in the Overview of this section.

To create a cluster

  1. Sign in to the AWS Management Console and open the Amazon Redshift console at https://console.aws.amazon.com/redshift/.

  2. Choose Launch Cluster.

  3. On the Cluster Details page, specify values for the following options, and then choose Continue.

    Cluster Identifier

    Type a unique name for your cluster.

    Cluster identifiers must meet the following conditions:

    • They must contain from 1 to 63 alphanumeric characters or hyphens.

    • Alphabetic characters must be lowercase.

    • The first character must be a letter.

    • They cannot end with a hyphen or contain two consecutive hyphens.

    • They must be unique for all clusters within an AWS account.

    Database Name

    Type a name if you want to create a database with a custom name (for example, mydb). This field is optional. A default database named dev is created for the cluster whether or not you specify a custom database name.

    Database names must meet the following conditions:

    • They must contain 1 to 64 alphanumeric characters.

    • They must contain only lowercase letters.

    • A database name cannot be a reserved word. For more information, go to Reserved Words in the Amazon Redshift Database Developer Guide.

    Database Port

    Type a port number through which you will connect from client applications to the database. The port number must be included in the connection string when opening JDBC or ODBC connections to the databases in the cluster.

    The port number must meet the following conditions:

    • It must contain only numeric characters.

    • It must fall in the range of 1150 to 65535. The default port is 5439.

    • It must specify an open port that accepts inbound connections, if you are behind a firewall.

    Master User Name

    Type an account name for the master user of the database.

    Master user names must meet the following conditions:

    • They must contain from 1 to 128 alphanumeric characters.

    • The first character must be a letter.

    • A master user name cannot be a reserved word. For more information, go to Reserved Words in the Amazon Redshift Database Developer Guide.

    Master User Password and Confirm Password

    Type a password for the master user account, and then retype it to confirm the password.

    The password must meet the following conditions:

    • It must be from 8 to 64 characters in length.

    • It must contain at least one uppercase letter.

    • It must contain at least one lowercase letter.

    • It must contain at least one number.

    • It can be any printable ASCII character (ASCII code 33 to 126) except single quotation mark, double quotation mark, \, /, @, or space.

    In the following screenshot, examplecluster is the cluster identifier, no custom database name is specified, 5439 is the port, and masteruser is the master user name.

  4. On the Node Configuration page, specify values for the following options, and then choose Continue.

    Node Type

    Select a node type. When you select a node type, the page displays information that corresponds to the selected node type, such as CPU, Memory, Storage, and I/O Performance.

    Cluster Type

    Select a cluster type. When you do, the maximum number of compute nodes for the selected node and cluster type appears in the Maximum box, and the minimum number appears in the Minimum box.

    If you choose Single Node, you will have one node that shares leader and compute functionality.

    If you choose Multi Node, specify the number of compute nodes that you want for the cluster in Number of Compute Nodes.

    In the following screenshot, the dc1.large node type is selected for a Multi Node cluster with two compute nodes.

  5. On the Additional Configuration page, specify values for the following options, and then choose Continue.

    1. For Provide the optional additional configuration details below, configure the following options:

      Cluster Parameter Group

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

      Encrypt Database

      Select 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, select whether you want to use AWS Key Management Service (AWS 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 KMS if you want to enable encryption and use AWS KMS to manage your encryption key. In Master Key, choose (default) aws/redshift to use a default customer master key (CMK) or choose another key from your AWS account.

        Note

        If you want to use a key from another AWS account, choose Enter a key ARN from Master Key. Then type the ARN for the key to use. You must have permission to use the key. For more information about access to keys in AWS KMS, go to Controlling Access to Your Keys in the AWS Key Management Service Developer Guide.

        For more information about using AWS KMS encryption keys in Amazon Redshift, see About Database Encryption for Amazon Redshift Using AWS 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, select 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 About Encryption for Amazon Redshift Using Hardware Security Modules.

    2. For Configure Networking Options, you configure whether to launch your cluster in a virtual private cloud (VPC) or outside a VPC. The option you choose affects the additional options available in this section. Amazon Redshift uses the EC2-Classic and EC2-VPC platforms to launch clusters. Your AWS account determines which platform or platforms are available to you for your cluster. For more information, see Supported Platforms in the Amazon EC2 User Guide for Linux Instances.

      Choose a VPC

      To launch your cluster in a virtual private cloud (VPC), select the VPC you want to use. You must have at least one Amazon Redshift subnet group set up to use VPCs. For more information, see Amazon Redshift Cluster Subnet Groups.

      To launch your cluster outside a VPC, choose Not in VPC. This option is available only to AWS accounts that support the EC2-Classic platform. Otherwise, you must launch your cluster in a VPC.

      Cluster Subnet Group

      Select the Amazon Redshift subnet group in which to launch the cluster.

      Note

      This option is available only for clusters in a VPC.

      Publicly Accessible

      Choose Yes to enable connections to the cluster from outside of the VPC in which you launch the cluster. Choose No if you want to limit connections to the cluster from only within the VPC.

      Note

      This option is available only for clusters in a VPC.

      Choose a Public IP Address

      If you set Publicly Accessible to Yes, choose No here to have Amazon Redshift to provide an Elastic IP (EIP) for the cluster, or choose Yes if you want to use an EIP that you have created and manage. If you have Amazon Redshift create the EIP, it is managed by Amazon Redshift.

      Note

      This option is available only for clusters in a VPC where Publicly Accessible is Yes.

      Elastic IP

      Select the EIP that you want to use to connect to the cluster from outside of the VPC.

      Note

      This option is available only for clusters in a VPC where Publicly Accessible and Choose a Public IP Address are Yes.

      Availability Zone

      Choose No Preference to have Amazon Redshift select the Availability Zone that the cluster will be created in. Otherwise, select a specific Availability Zone.

      Enhanced VPC Routing

      Choose Yes to enable Enhanced VPC Routing. Enhanced VPC Routing might require additional configuration. For more information, see Amazon Redshift Enhanced VPC Routing

    3. For Optionally, associate your cluster with one or more security groups, specify values for the following options:

      Cluster Security Groups

      Select an Amazon Redshift security group or groups for the cluster. By default, the selected security group is the default security group. For more information about cluster security groups, see Amazon Redshift Cluster Security Groups.

      Note

      This option is only available if you launch your cluster in the EC2-Classic platform.

      VPC Security Groups

      Select a VPC security group or groups for the cluster. By default, the selected security group is the default VPC security group. For more information about VPC security groups, go to Security Groups for Your VPC in the Amazon VPC User Guide.

      Note

      This option is only available if you launch your cluster in the EC2-VPC platform.

    4. For Optionally create a basic alarm for this cluster, configure the following options, and then choose Continue:

      Create CloudWatch Alarm

      Choose Yes if you want to create an alarm that monitors the disk usage of your cluster, and then specify values for the corresponding options. Choose No if you don't want to create an alarm.

      Disk Usage Threshold

      Select a percentage of average disk usage that has been reached or exceeded at which the alarm should trigger.

      Use Existing Topic

      Choose No if you want to create a new Amazon Simple Notification Service (Amazon SNS) topic for this alarm. In the Topic box, edit the default name if necessary. For Recipients, type the email addresses for any recipients who should receive the notification when the alarm triggers.

      Choose Yes if you want to select an existing Amazon SNS topic for this alarm, and then in the Topic list, select the topic that you want to use.

  6. On the Review page, review the details of the cluster. If everything is satisfactory, choose Launch Cluster to start the creation process. Otherwise, choose Back to make any necessary changes, and then choose Continue to return to the Review page.

    Note

    Some cluster properties, such as the values for Database Port and Master User Name, cannot be modified later. If you need to change them, choose Back to change them now.

    The following screenshot shows a summary of various options selected during the cluster launch process.

  7. After you initiate the creation process, choose Close. The cluster might take several minutes to be ready to use.

    You can monitor the status of the operation in the performance dashboard.

Modifying a Cluster

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

  • VPC Security Groups

  • Publicly Accessible

  • Master User Password

  • Automated Snapshot Retention Period

  • HSM Connection

  • HSM Client Certificate

  • Maintenance Window Start

  • Maintenance Window End

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.

  • 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.

To modify a cluster

  1. Sign in to the AWS Management Console and open the Amazon Redshift console at https://console.aws.amazon.com/redshift/.

  2. In the navigation pane, choose Clusters, and then choose the cluster that you want to modify.

  3. On the Configuration tab of the cluster details page, choose Cluster, and then choose Modify.

  4. In the Modify Cluster window, make the changes to the cluster, and then choose Modify.

    The following screenshot shows the Modify Cluster options for a cluster in a VPC.

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 will need a manual snapshot so that you can restore the snapshot at a later time and resume using the cluster. If you delete your cluster but you don't create a final manual snapshot, the cluster data will be 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 AWS Management Console and open the Amazon Redshift console at https://console.aws.amazon.com/redshift/.

  2. In the navigation pane, choose Clusters, and then choose the cluster that you want to delete.

  3. On the Configuration tab of the cluster details page, choose Cluster, and then choose Delete.

  4. In the Delete Cluster dialog box, do one of the following:

    • In Create snapshot, choose Yes to delete the cluster and take a final snapshot. In Snapshot name, type a name for the final snapshot, and then choose Delete.

    • In Create snapshot, choose No to delete the cluster without taking a final snapshot, and then choose Delete.

    After you initiate the delete of the cluster, it can take several minutes for the cluster to be deleted. You can monitor the status in the cluster list as shown in the following screenshots. If you requested a final snapshot, Cluster Status will show final-snapshot before deleting.

    The following screenshot shows the cluster with a status of final-snapshot before it is deleted.

    The following screenshot shows the cluster with a status of deleting.

    When the process has finished, you can verify that the cluster has been deleted because it will no longer appear in the list of clusters on the Clusters page.

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 AWS Management Console and open the Amazon Redshift console at https://console.aws.amazon.com/redshift/.

  2. In the navigation pane, choose Clusters, and then choose the cluster that you want to reboot.

  3. On the Configuration tab of the cluster details page, choose Cluster and then choose Reboot.

  4. In the Reboot Clusters window, confirm that you want to reboot this cluster, and then choose Reboot.

    It can take several minutes for the cluster to be available. You can monitor the status of the reboot in the cluster list as shown in the following screenshot.

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 Tutorial: Resizing Clusters in Amazon Redshift.

To resize a cluster

  1. Sign in to the AWS Management Console and open the Amazon Redshift console at https://console.aws.amazon.com/redshift/.

  2. In the navigation pane, choose Clusters, and then choose the cluster that you want to resize.

  3. On the Configuration tab of the cluster details page, choose Cluster, and then choose Resize.

  4. In the Resize Clusters window, configure the resize parameters including the Node Type, Cluster Type, and Number of Nodes, and then choose Resize.

    You can monitor the progress of the resize on the Status tab.

Getting Information About Cluster Configuration

To get cluster configuration details

  1. Sign in to the AWS Management Console and open the Amazon Redshift console at https://console.aws.amazon.com/redshift/.

  2. In the navigation pane, choose Clusters, and then choose the cluster for which you want to view configuration information.

  3. On the Configuration tab of the cluster details page, review the configuration information. You can view information about the cluster properties, status, database, capacity, backup, audit logging, maintenance, and SSH ingestion settings.

Getting an Overview of Cluster Status

The cluster Status tab provides a high level overview of the status of a cluster, a summary of events related to the cluster, and a list of Amazon CloudWatch alarms associated with the cluster.

To get an overview of cluster status

  1. Sign in to the AWS Management Console and open the Amazon Redshift console at https://console.aws.amazon.com/redshift/.

  2. In the navigation pane, choose Clusters, and then choose the cluster for which you want to view status information.

  3. Choose the Status tab.

    The status summary page is displayed as shown in the following screenshot.

Taking a Snapshot of a Cluster

You can take a snapshot of your cluster from the Configuration tab of your cluster as shown following. You can also take a snapshot of your cluster from the snapshots part of the Amazon Redshift console. For more information, go to Managing Snapshots Using the Console.

To take a snapshot of a cluster

  1. Sign in to the AWS Management Console and open the Amazon Redshift console at https://console.aws.amazon.com/redshift/.

  2. In the navigation pane, choose Clusters, and then choose the cluster for which you want to take a snapshot.

  3. On the Configuration tab of the cluster details page, choose Backup, and then choose Take Snapshot.

  4. In the Create Snapshot dialog box, do the following:

    1. In the Cluster Identifier box, choose the cluster that you want to take a snapshot of.

    2. In the Snapshot Identifier box, type a name for the snapshot.

  5. Choose Create.

    To view details about the snapshot taken and all other snapshots for your AWS account, go to the snapshots part of the Amazon Redshift console (see Managing Snapshots Using the Console).

Editing the Default Disk Space Alarm

If you opted to create a default disk space alarm when you created your Amazon Redshift cluster, you can edit the alarm. For example, you might want to change the percentage at which the alarm triggers, or you might want to change the duration settings.

To edit the default disk space alarm

  1. Sign in to the AWS Management Console and open the Amazon Redshift console at https://console.aws.amazon.com/redshift/.

  2. In the navigation pane, choose Clusters, and then choose the cluster associated with the alarm that you want to edit.

  3. Choose the Status tab.

  4. In the CloudWatch Alarms section, choose the alarm that you want to edit.

    The default disk space alarm that was created when you launched your cluster is named percentage-disk-space-used-default-<string>. The string is randomly generated by Amazon Redshift.

  5. In the Edit Alarm window, edit any values that you want to change, such as the percentage or minutes.

  6. To change the Amazon SNS topic that the alarm is associated with, do one of the following:

    • If you want to select another existing topic, select a topic from the Send a notification to list.

    • If you want to create a new topic, choose create topic and specify a new topic name and the email addresses for recipients.

  7. Choose Save.

Working with Cluster Performance Data

You can work with cluster performance data using the Performance, Queries, and Loads tabs. For more information about working with cluster performance, see Working with Performance Data in the Amazon Redshift Console.