Amazon Redshift Management Manual

Type
Management Manual
Amazon Redshift
Management Guide
API Version 2012-12-01
Amazon Web Services
Amazon Redshift Management Guide
Amazon Redshift: Management Guide
Amazon Web Services
Copyright © 2013 Amazon Web Services, Inc. and/or its affiliates. All rights reserved.
All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected
to, or sponsored by Amazon.
Amazon Redshift Management Guide
What Is Amazon Redshift? ..................................................................................................................... 1
Clusters ................................................................................................................................................... 4
Managing Clusters Using the Console .................................................................................................. 7
Managing Clusters Using AWS SDK for Java ...................................................................................... 21
Manage Clusters Using Amazon Redshift CLI and API ........................................................................ 23
Managing Clusters in VPC .................................................................................................................... 23
Creating a Cluster in a VPC ........................................................................................................ 24
Cluster Subnet Groups ................................................................................................................ 25
Managing Cluster Subnet Groups Using the Console ...................................................... 26
Managing Cluster Subnet Groups Using AWS SDK for Java ............................................ 29
Manage Cluster Subnet Groups Using Amazon Redshift CLI and API ............................. 31
Security Groups .................................................................................................................................... 32
Managing Security Groups Using the Console .................................................................................... 33
Managing Security Groups Using AWS SDK for Java ......................................................................... 37
Manage Security Group Using Amazon Redshift CLI and API ............................................................. 40
Parameter Groups ................................................................................................................................ 41
Managing Parameter Groups Using the Console ................................................................................. 43
Managing Parameter Groups Using AWS SDK for Java ..................................................................... 47
Manage Parameter Groups Using Amazon Redshift CLI and API ....................................................... 51
Snapshots ............................................................................................................................................. 52
Managing Snapshots Using the Console .............................................................................................. 54
Managing Snapshots Using AWS SDK for Java .................................................................................. 59
Managing Snapshots Using Amazon Redshift CLI and API ................................................................. 62
Events ................................................................................................................................................... 63
Viewing Events Using the Console ....................................................................................................... 63
Viewing Events Using AWS SDK for Java ........................................................................................... 65
View Events Using Amazon Redshift CLI and API ............................................................................... 66
Monitoring Cluster Performance ........................................................................................................... 67
Summary of Performance Data ............................................................................................................ 68
Working with Performance Data ........................................................................................................... 71
Viewing Cluster Performance Data ............................................................................................. 72
Viewing Cluster Metrics During Query Execution ........................................................................ 74
Viewing Cluster Metrics During Load Operations ........................................................................ 77
Creating an Alarm ....................................................................................................................... 78
Working with Performance Metrics in the Amazon CloudWatch Console ................................... 80
Purchasing Reserved Nodes ................................................................................................................ 82
Purchasing a Reserved Node Offering with the Console ..................................................................... 83
Purchasing a Reserved Node Offering Using Java .............................................................................. 86
Purchase a Reserved Node Offering Using Amazon Redshift CLI and API ......................................... 89
Controlling Access to Amazon Redshift Resources ............................................................................. 90
Connecting to a Cluster ........................................................................................................................ 95
Setting Up the SQL Workbench Client .................................................................................................. 96
Connect to Your Cluster by Using the psql Tool .................................................................................. 103
Connect to Your Cluster Using SSL .................................................................................................... 105
Connect to Your Cluster Programmatically ......................................................................................... 107
Connect from Outside of Amazon EC2 - Firewall Timeout Issue ........................................................ 112
Limits .................................................................................................................................................. 114
Using the AWS SDKs ......................................................................................................................... 117
Using the AWS SDK for Java .............................................................................................................. 117
Uploading Client-Side Encrypted Data ............................................................................................... 120
Signing an HTTP Request .................................................................................................................. 124
Document History ............................................................................................................................... 127
API Version 2012-12-01
4
Amazon Redshift Management Guide
What Is Amazon Redshift?
Welcome to the Amazon Redshift Cluster Management Guide. Amazon Redshift is a fully managed,
petabyte-scale data warehouse service in the cloud. Amazon Redshift offers you fast query performance
when analyzing virtually any size data set using the same SQL-based tools and business intelligence
applications you use today.With a few clicks in the AWS Management Console, you can launch a Redshift
cluster, starting with a few hundred gigabytes of data and scaling to a petabyte or more.
Your first step in creating a data warehouse is to launch a set of compute nodes, called an Amazon
Redshift cluster.The number and type of compute nodes that you need depends on the size of your data,
the number of queries you will execute, and the query execution performance you need. Each cluster
that you provision is a fully managed Amazon Redshift data warehouse.You can use the Amazon Redshift
Management console, API, or CLI to create and manage clusters.
By default, Amazon Redshift creates one database when you create a cluster.You can create additional
databases as needed. After your cluster has been provisioned, you can upload your dataset and then
perform data analysis queries by using the SQL-based tools and business intelligence applications that
you are already familiar with. Regardless of the size of the data set, Amazon Redshift offers high query
performance.
Amazon Redshift manages all the work of setting up, operating, and scaling a data warehouse: provisioning
capacity, monitoring and backing up the cluster, and applying patches and upgrades to the Amazon
Redshift engine.You can focus on using your data to acquire new insights for your business and customers.
Cluster Management Overview
Cluster management involves the following operations:
Create and manage clusters – Depending on your data warehousing needs, you can start with a small
cluster with just a single XL node and easily scale up to 100 8XL nodes as your requirements change.
You can monitor the performance of your data warehouse, and if needed, you can add or remove compute
nodes without any interruption to the service. For more information, see Amazon Redshift Clusters (p.4).
If you intend to keep your cluster running for a year or longer, you can save money by reserving compute
nodes for a one-year or three-year period. Reserving compute nodes offers significant savings compared
to the hourly rates that you pay when you provision compute nodes on demand. For more information,
see Purchasing Amazon Redshift Reserved Nodes (p. 82).
Create and manage cluster security groups – By default, any cluster that you create is closed to
everyone.To enable access to your cluster, you create a security group and associate it with your cluster.
API Version 2012-12-01
1
Amazon Redshift Management Guide
Cluster Management Overview
You add rules to the security group to grant explicit inbound access to a specific range of CIDR/IP
addresses or to an Amazon Elastic compute Cloud (EC2) security group if your SQL client is running on
an EC2 instance. For more information, see Amazon Redshift Cluster Security Groups (p.32).
Create and manage parameter groups – When you create an Amazon Redshift cluster, you associate
a parameter group with it.The parameters in this group, such as the date presentation style and floating
point precision, apply to all the databases that you create on the cluster.There is a default parameter
group for the Amazon Redshift engine that defines preset values for the parameters. If your application
requires different settings, you can create your own parameter group. For more information, see Amazon
Redshift Parameter Groups (p.41).
Manage snapshots – Amazon Redshift continuously backs up your data to an Amazon Simple Storage
Service (S3) bucket to help protect against data loss.You also have the option to create your own
point-in-time backups of your cluster.These automated and manual backups are called snapshots.You
can restore a cluster to its state when you took the snapshot. Amazon Redshift supports both automated
and manual snapshots. For more information, see Amazon Redshift Snapshots (p. 52)
Monitor cluster performance – Amazon Redshift collects metrics that you can use to track the health
and performance of your clusters and queries.You can set up alarms that notify you when one or more
metrics are outside an acceptable range.You can use the Amazon Redshift console to directly access
the most common cluster performance metrics and to look at the resource utilization of individual queries.
You can also view cluster performance metrics by using Amazon CloudWatch. For more information, see
Monitoring Amazon Redshift Cluster Performance (p.67).
Control access to your Amazon Redshift resources – The AWS account that creates the cluster has
full access to the cluster.Within your AWS account, you can use the AWS Identity and Access Management
(IAM) service to create user accounts and manage permissions for those accounts. By using IAM, you
can grant different users permission to perform only the cluster operations that are necessary for their
work. IAM controls only access to the Amazon Redshift API; it does not control access to the cluster via
JDBC and ODBC. For more information, see Controlling Access to Amazon Redshift Resources (p. 90).
Are You a First-Time Amazon Redshift User?
If you are a first-time user of Amazon Redshift, we recommend that you begin by reading the following
sections:
• Service Highlights and Pricing – The product detail page provides the Amazon Redshift value
proposition, service highlights, and pricing.
• Getting Started – The Getting Started Guide includes an example that walks you through the process
of creating a cluster, creating database tables, uploading data, and testing queries.
After you complete the Getting Started guide, we recommend that you explore one of the following guides:
• Amazon Redshift Cluster Management Guide (this document) – This guide shows you how to
create and manage Amazon Redshift clusters. For more information, see the following Cluster
Management Overview (p.1) section.
If you are an application developer, you can use the Amazon Redshift Query API to manage clusters
programmatically. Additionally, the AWS SDK libraries that wrap the underlying Amazon Redshift API
simplify your programming tasks. If you prefer a more interactive way of managing clusters, you can
use the Amazon Redshift console and the AWS command line interface (AWS CLI). For information
about the API and CLI, go to the following manuals :
• API Reference
• CLI Reference
API Version 2012-12-01
2
Amazon Redshift Management Guide
Are You a First-Time Amazon Redshift User?
• Amazon Redshift Database Developer Guide – If you are a database developer, the Amazon Redshift
Database Developer Guide explains how to design, build, query, and maintain the databases that make
up your data warehouse.
API Version 2012-12-01
3
Amazon Redshift Management Guide
Are You a First-Time Amazon Redshift User?
Amazon Redshift Clusters
Topics
• Overview (p.4)
• Managing Clusters Using the Console (p. 7)
• Managing Clusters Using AWS SDK for Java (p.21)
• Manage Clusters Using Amazon Redshift CLI and API (p.23)
• Managing Clusters in Virtual Private Cloud (VPC) (p.23)
Overview
An Amazon Redshift data warehouse is a collection of computing resources called nodes.This collection
of nodes is called a cluster.When you provision a cluster, you specify the type and the number of nodes
that will make up the cluster.The node type determines the storage size, memory, CPU, and price of
each node in the cluster. All the compute nodes in the cluster will be of the same type. For a list of
supported node types and related pricing, go to the Amazon Redshift Pricing page.
If your storage and performance needs change after you initially provision your cluster, you can always
scale the cluster in or out by adding or removing nodes, scale the cluster up or down by specifying a
different node type, or you can do both. Resizing the cluster in either way involves minimal downtime.
Resizing replaces old cluster at the end of the resize operation.When you submit a resize request, the
source cluster remains in read-only mode until the resize operation is complete.
Each cluster runs an Amazon Redshift engine.
When you create a cluster you also provide master user name and password.This master user will have
access to all the databases you create within the cluster.
There are other configuration options you can specify.When you provision an Amazon Redshift cluster,
it is locked down by default so that nobody has access to it.The security group is a mechanism that you
can use to grant inbound access to the cluster. Other configuration parameters, which govern the behavior
of the databases on your cluster, are stored in a parameter group.You can associate one or more security
groups and a parameter group with your cluster. If you don't provide a security group or a parameter
group, Amazon Redshift associates a default parameter group and security group with the cluster. For
more information, see (Amazon Redshift Cluster Security Groups (p.32)) and Amazon Redshift Parameter
Groups (p. 41).
API Version 2012-12-01
4
Amazon Redshift Management Guide
Overview
When creating a cluster you can optionally choose the cluster encryption option for additional security.
When you enable encryption in your cluster, Amazon Redshift stores all data in user-created tables in an
encrypted format. Note that enabling encryption in your cluster will impact performance, even though it
is hardware accelerated. On average, we expect you will see approximately a 20% degradation, with
peak overheads of 40%.You should take this into account when deciding whether you should enable
encryption when you create the cluster. Encryption is an immutable property of the cluster.The only way
to go from encrypted to non encrypted or vice versa is to unload the data and reload it to a new cluster.
Encryption also applies to backups.When restoring from an encrypted snapshot, the new cluster will be
encrypted as well.
If you are using the Amazon Redshift console to provision a cluster, it provides values for these options
for you to choose from. If you are provisioning a cluster programmatically, you can use the Amazon
Redshift API to find available options such as available node types Availability Zones (AZ) in which the
node types are available.
Note
At this time Amazon Redshift version 1.0 engine is available, however, as the engine is updated,
multiple Amazon Redshift engine versions might be available for selection.
For a list of supported AWS regions where you can provision a cluster, go to the Regions and Endpoints
section in the Amazon Web Services Glossary.
How Many Nodes Do I Need?
When you provision a cluster, you specify the type and the number of nodes that you need.You have a
choice of two node types when provisioning your own cluster, an extra large node (XL) with 2 TB of
compressed storage or an eight extra large node (8XL) with 16 TB of compressed storage. A cluster can
consist of a single XL node, or it can be as large as a 100 8XL nodes. XL clusters can contain from 1 to
32 nodes; 8XL clusters can contain 2 to 100 nodes. For pricing information and detailed information about
individual node types, go the Amazon Redshift product detail page.
The number of nodes you choose depends on the size of your dataset and your desired query performance.
For example, if you have 32 TB of data, you can choose 16 XL nodes or 2 8XL nodes. If your data grows
in small increments, choosing XL nodes will allow you to scale in increments of 2 TB. If you typically see
data growth in larger increments, an 8XL node based cluster may be a better choice.
Because Amazon Redshift distributes and executes queries in parallel across all Compute Nodes, you
can increase query performance by adding nodes to your data warehouse cluster. Amazon Redshift also
distributes your data across all compute nodes in a cluster.When you run a cluster with at least two
compute nodes, data on each node will always be mirrored on disks on another node and you reduce
the risk of incurring data loss.
Whichever choice you make, you can monitor query performance in the Amazon Redshift Console and
with Amazon Cloud Watch metrics.You can also add or remove nodes, as needed, to achieve the balance
between storage and performance that works best for you.When you request an additional node, Amazon
Redshift takes care of all the details of deployment, load balancing, and data maintenance.
For pricing information and detailed information about individual node types, go the Amazon Redshift
product detail page.
Availability Zone Considerations
By default, Amazon Redshift provisions your cluster in a randomly selected Availability Zone (AZ) within
the AWS region that you specify. All the cluster nodes are provisioned in the same AZ.
You can optionally request a specific Availability Zone, if Amazon Redshift is available in that Availability
Zone. For example, if you already have an Amazon Elastic Compute Cloud (EC2) instance running in
one Availability Zone, you might want to create your cluster in the same Availability Zone to reduce latency.
API Version 2012-12-01
5
Amazon Redshift Management Guide
How Many Nodes Do I Need?
On the other hand, you might choose another Availability Zone for higher availability. Amazon Redshift
may not be available in all Availability Zones within a region
Modifying a Cluster
From time to time after your cluster is running, you will probably want to make changes to it. For example,
you might associate a different parameter group with it, associate another list of security groups to include
additional security groups, or revoke existing security group associations.
When you associate a new parameter group, you must reboot the cluster for the change to take effect.
You can immediately reboot the cluster by using the Amazon API or the Amazon Redshift console. If
Amazon Redshift reboots the cluster during maintenance operations, the new parameter group will take
effect.
When you change the security group associations for a cluster, a reboot is not required.
Resizing a Cluster
If your storage and performance needs change after you initially provision your cluster, you can always
scale the cluster in or out by adding or removing nodes. Additionally, you can scale the cluster up or down
by specifying a different node type.When using the API you have to specify both even if you are only
changing one. Resizing the cluster in either way involves minimal downtime
When you resize a cluster, Amazon Redshift first puts your existing cluster in the read-only mode. Amazon
Redshift then provisions the nodes as requested, copies data to the new cluster, and switches your
connections to use the new cluster. At this time you lose any open connections to the old cluster. If you
have any queries in progress at the time of this switch, you will notice the connection loss.You must
restart the query on the new cluster.
In a modify operation, you can resize your cluster as necessary. For example, you can add more nodes,
change the node types, change single-node cluster to multinode or a multinode cluster to a single-node.
You must, however, ensure that the resulting cluster is large enough to hold the data that you currently
have; otherwise the resize will fail.
Cluster Maintenance
Amazon Redshift periodically performs maintenance to apply upgrades to your cluster. During these
updates, your Amazon Redshift cluster will not be available for normal operations.You can schedule a
thirty-minute weekly maintenance window during which these activities will take place.You can set the
maintenance window when you create the cluster, or you can modify the maintenance window whenever
you want.You can set the maintenance window either programmatically or by using the Amazon Redshift
console.While Amazon Redshift is performing maintenance, it will terminate any queries or other operations
that are in progress. If there are no maintenance tasks to perform during the scheduled maintenance
window, your cluster continues to operate normally until the next maintenance window.
Supported Platforms to Launch Your Cluster
Depending on your AWS account settings, you can launch an Amazon Redshift cluster on one of the
following Amazon Elastic Compute Cloud (EC2) platforms:
• EC2-Classic – Your cluster runs in a single, flat network that you share with other AWS customers.
If you deploy on EC2-Classic, you will control access to your cluster by associating one or more Amazon
Redshift cluster security groups with the cluster. For more information, see Amazon Redshift Cluster
Security Groups (p.32).
API Version 2012-12-01
6
Amazon Redshift Management Guide
Modifying a Cluster
• EC2-VPC – Your cluster runs in a virtual private cloud (VPC) that is logically isolated to your AWS
account.
If you deploy on EC2-VPC, you will control access to your cluster by associating one or more VPC
security groups with the cluster. For more information, go to Security Groups for Your VPC.
To create a cluster in a VPC, you must first create an Amazon Redshift cluster subnet group by providing
subnet information of your VPC, and then provide the subnet group when launching the cluster. For
more information, see Amazon Redshift Cluster Subnet Groups (p.25).
For more information about VPC, go to Amazon Virtual Private Cloud (Amazon VPC) product detail
page.
Your AWS account can launch a cluster either into both platforms or only into EC2-VPC, depending on
the AWS region.To determine which platform your account supports and then deploy a cluster, do the
following:
1. Decide on the AWS region in which you want to deploy a cluster. For a list of AWS regions in which
Amazon Redshift is available, go to Regions and Endpoints in the Amazon Web Services General
Reference.
2. Find out which EC2 platforms your account supports in the chosen AWS region.
You can find this information in the EC2 console. For step-by-step instructions, go to Supported
Platforms in the Amazon Elastic Compute Cloud User Guide.
3. If your account supports both EC2 platforms, choose the platform on which you want to deploy the
Amazon Redshift cluster. If your account supports only EC2-VPC, you deploy your cluster in VPC.
4. Deploy your Amazon Redshift cluster.
You can deploy a cluster by using Amazon Redshift console or programmatically using the Amazon
Redshift API or the SDK libraries. For more information, click one of the links provided at the beginning
of this topic.
Managing Clusters Using the Console
Topics
• Creating a Cluster (p. 8)
• Modifying a Cluster (p. 13)
• Deleting a Cluster (p. 15)
• Rebooting a Cluster (p. 16)
• Resizing a Cluster (p. 17)
• Getting Information About Cluster Configuration (p.18)
• Getting an Overview of Cluster Status (p.19)
• Taking a Snapshot of a Cluster (p.20)
• Working with Cluster Performance Data (p.21)
This section explains how to create, modify, get information about, delete, and reboot a cluster by using
the Amazon Redshift console. In general, you accomplish these tasks by viewing the cluster performance
dashboard.The dashboard is a list of clusters that shows at a glance the status of the cluster (e.g.
available), the DB Health of the cluster (e.g.healthy), whether the cluster is undergoing maintenance,
and count of recent events.
API Version 2012-12-01
7
Amazon Redshift Management Guide
Managing Clusters Using the Console
Creating a Cluster
Before you create a cluster, review the information in the Overview (p. 4) of this section.
To create a cluster
1. Sign into the AWS Management Console and open the Amazon Redshift console at
https://console.aws.amazon.com/redshift.
2. Do one of the following:
a. If no clusters are configured for your account, click Launch Cluster.
b. If one or more clusters are defined for your account, in the navigation pane, click Clusters.
Under Launch an Amazon Redshift Cluster, click Launch Cluster.
3. On the CLUSTER DETAILS page, do the following.When all the settings are as you want them,
click Continue.
a. In the Cluster Identifier box, type a unique name for your cluster.
API Version 2012-12-01
8
Amazon Redshift Management Guide
Creating a Cluster
Cluster identifiers must meet the following conditions:
• Must contain from 1 to 63 alphanumeric characters or hyphens.
• Alphabetic characters must be lowercase.
• First character must be a letter.
• Cannot end with a hyphen or contain two consecutive hyphens.
• Must be unique for all clusters within an AWS account.
b. (Optional) In the Database Name box, type a name for the first database that will be created
for the cluster. If you leave this box empty, the database will be named dev. If you choose a
name it must meet the following conditions:
• Must contain 1 to 64 alphanumeric characters.
• Must contain only lowercase letters.
• Cannot be a reserved word. A list of reserved words can be found in Reserved Words in
the Amazon Redshift Developer Guide.
c. In the Database Port box, type a database port through which you will connect to the database
instance.
d. In the Master User Name box, specify an account name for the master user of the database.
Master user names must meet the following conditions:
• Must contain from 1 to 128 alphanumeric characters.
• First character must be a letter.
• Cannot be a reserved word. For a list of reserved words, go to Reserved Words in the Amazon
Redshift Developer Guide.
e. In the Master User Password and Confirm Password boxes, type a password for the master
user account and confirm the password.
Passwords must meet the following conditions:
• Must be between 8 and 64 characters in length.
• Must contain at least one uppercase letter.
• Must contain at least one lowercase letter.
• Must contain one number.
• Can be any printable ASCII character (ASCII code 33 to 126) except ' (single quote), " (double
quote), \, /, @, or space.
In the following example, examplecluster is the cluster identifier, no database name is
specified, 5439 is the port and masteruser is the master user name.
API Version 2012-12-01
9
Amazon Redshift Management Guide
Creating a Cluster
4. On the NODE CONFIGURATION page, do the following.When all the settings are as you want them,
click Continue.
a. In the Node Type box, click a node type.
The CPU, Memory, Storage, and I/O Performance information will display the corresponding
information for the node that you select.
b. In the Cluster Type box, click a cluster type.
c. In the Number of Compute Nodes box, specify the number of nodes that the cluster will contain.
If you select Cluster Type as Single Node, the number of compute nodes is set to one.
In the following example, the node type dw.hs1.xlarge is selected, No Preference for availability
zone is selected, Cluster Type as Multi Node is selected and two nodes are specified.
API Version 2012-12-01
10
Amazon Redshift Management Guide
Creating a Cluster
5. On the ADDITIONAL CONFIGURATION page, do the following.When all the settings are as you
want them, click Continue.
a. (Optional) In the Cluster Parameter Group box, click a cluster parameter group to be associated
with the cluster. If you don't select a parameter group, the default parameter group will be
associated with the cluster.
b. Under Encrypt Database, choose whether to encrypt all data within the cluster and in backups.
The default is no encryption.
c. Configure the networking options and security groups of the cluster.
• Take one of the following actions.
Do this...To...
a. In the Choose a VPC box, click Not in VPC.
b. (Optional) In the Availability Zone box, click the
availability zone where you want to provision your cluster.
c. In the Cluster Security Groups box, click a security
group to associate with the cluster.
Provision the cluster outside
of a VPC
a. In the Choose a VPC box, choose a VPC.
Note
The Choose a VPC box is not enabled if you
don't have at least one cluster subnet group
defined.
b. In the Cluster Subnet Group box choose a subnet
group.
c. Under Publicly Accessible, choose whether you want
the cluster to be accessible from the public.
d. (Optional) In the Availability Zone box, click the
availability zone where you want to provision your cluster.
e. In the VPC Security Groups box, select one or more
security groups to associate with the cluster.
Provision the cluster in a
VPC.
d. Click Continue.
API Version 2012-12-01
11
Amazon Redshift Management Guide
Creating a Cluster
In the following example, a VPC, a VPC security group, and cluster subnet group are specified.
The cluster is marked as not publicly accessible, and no preference is selected for the availability
zone.
6. On the REVIEW page, review the details of the cluster. If everything is satisfactory, click Launch
Cluster to start the creation process. Otherwise, click Back to make any necessary modification,
and then click Continue to return to the Review page.
Note
Some cluster properties such as Database Port and Master User Name cannot be modified
later. If you need to change them, use the Back link to change them now.
API Version 2012-12-01
12
Amazon Redshift Management Guide
Creating a Cluster
7. After you initiate the creation process, click Close.The cluster may take several minutes to be ready
to use.
You can monitor the status of the operation in the performance dashboard.
Modifying a Cluster
After you have created a cluster, you can modify some of its configuration options. For example, you can
associate a different parameter group or security groups.You can also change the cluster maintenance
window, the master user credentials, and the automated snapshot retention period. All of these changes
take effect only after the cluster is restarted.
If you decrease the automated snapshot retention period, existing automated snapshots that fall outside
of the new retention period are deleted. For information about working with snapshots, see Amazon
Redshift Snapshots (p. 52).
To modify a cluster
1. Sign into the AWS Management Console and open the Amazon Redshift console at
https://console.aws.amazon.com/redshift.
2. In the navigation pane, click Clusters.
3. Under Performance Status, click the magnifying glass icon beside the cluster that you want to
modify.
API Version 2012-12-01
13
Amazon Redshift Management Guide
Modifying a Cluster
4. In the cluster summary page, click Modify.
5. In the Modify Cluster dialog box, make the changes to the cluster, and then click Modify.
In the following example, a cluster not provisioned in a VCP is modified so that two security groups
are associated with the cluster.To associate multiple security groups with a cluster, you can select
multiple items from the Cluster Security Groups list.
In the following example, a cluster provisioned in a VPC is modified so that two VPC security groups
are selected to be associated with the cluster.To associate multiple VPC security groups with a
cluster, you can select multiple items from the VPC Security Groups list.
API Version 2012-12-01
14
Amazon Redshift Management Guide
Modifying a Cluster
Deleting a Cluster
When you delete a cluster, you can optionally create a final cluster manual snapshot. If you plan to
provision a new cluster with the same data and configuration as the one you are deleting, you will need
this snapshot. Furthermore, when you delete a cluster, automated snapshots of the cluster are removed.
For more information about cluster snapshots, see Amazon Redshift Snapshots (p. 52).
To delete a cluster
1. Sign into the AWS Management Console and open the Amazon Redshift console at
https://console.aws.amazon.com/redshift.
2. In the navigation pane, click Clusters.
3. Under Performance Status, click the magnifying glass icon beside the cluster that you want to
delete.
In the example below, examplecluster is the cluster we want to delete.
4. On the cluster summary page, click Delete.
API Version 2012-12-01
15
Amazon Redshift Management Guide
Deleting a Cluster
5. In the Delete Clusters dialog box, in the Create final snapshot box, click Yes or No.To confirm
deletion, click Delete.
If you chose to create a final snapshot enter a snapshot name in the Final snapshot name box.
After you initiate the deletion of the cluster, it can take several minutes for the cluster to be deleted.
You can monitor the status of the deletion in the cluster list as shown in the example below. If you
requested a final snapshot, the Status will show final-snapshot before deleting.
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 into the AWS Management Console and open the Amazon Redshift console at
https://console.aws.amazon.com/redshift.
2. In the navigation pane, click Clusters.
3. Under Performance Status, click the magnifying glass icon beside the cluster that you want to
reboot.
4. On the cluster summary page, click Reboot.
5. In the Reboot Clusters dialog, confirm you have selected the cluster you intended, and click Reboot.
API Version 2012-12-01
16
Amazon Redshift Management Guide
Rebooting a Cluster
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70
  • Page 71 71
  • Page 72 72
  • Page 73 73
  • Page 74 74
  • Page 75 75
  • Page 76 76
  • Page 77 77
  • Page 78 78
  • Page 79 79
  • Page 80 80
  • Page 81 81
  • Page 82 82
  • Page 83 83
  • Page 84 84
  • Page 85 85
  • Page 86 86
  • Page 87 87
  • Page 88 88
  • Page 89 89
  • Page 90 90
  • Page 91 91
  • Page 92 92
  • Page 93 93
  • Page 94 94
  • Page 95 95
  • Page 96 96
  • Page 97 97
  • Page 98 98
  • Page 99 99
  • Page 100 100
  • Page 101 101
  • Page 102 102
  • Page 103 103
  • Page 104 104
  • Page 105 105
  • Page 106 106
  • Page 107 107
  • Page 108 108
  • Page 109 109
  • Page 110 110
  • Page 111 111
  • Page 112 112
  • Page 113 113
  • Page 114 114
  • Page 115 115
  • Page 116 116
  • Page 117 117
  • Page 118 118
  • Page 119 119
  • Page 120 120
  • Page 121 121
  • Page 122 122
  • Page 123 123
  • Page 124 124
  • Page 125 125
  • Page 126 126
  • Page 127 127
  • Page 128 128
  • Page 129 129
  • Page 130 130
  • Page 131 131

Amazon Redshift Management Manual

Type
Management Manual

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI