User guide

Parameter Value for This ExerciseParameter Name
TopSecret1Master Password
dw1.xlarge or the node size that you want to use.
For more information, see About Clusters and
Nodes (p. 6)
Node Type
single-nodeCluster Type
To create your cluster, type the following command:
aws redshift create-cluster --cluster-identifier examplecluster --master-username
masteruser --master-user-password TopSecret1 --node-type dw1.xlarge --cluster-
type single-node
The cluster creation process will take several minutes to complete.To check the status, type the following
command:
aws redshift describe-clusters --cluster-identifier examplecluster
The output will look similar to this:
{
"Clusters": [
{
...output omitted...
"ClusterStatus": "creating",
"ClusterIdentifier": "examplecluster",
...output omitted...
}
When the ClusterStatus field changes from creating to available, your cluster is ready for use.
In the next step, you will authorize access so that you can connect to the cluster.
Step 3: Authorize Inbound Traffic for Cluster Access
You must explicitly grant inbound access to your client in order to connect to the cluster.Your client can
be an Amazon EC2 instance or an external computer.
When you created a cluster in the previous step, because you did not specify a security group, you
associated the default cluster security group with the cluster. The default cluster security group contains
no rules to authorize any inbound traffic to the cluster. To access the new cluster, you must add rules for
inbound traffic, which are called ingress rules, to the cluster security group.
Ingress Rules for Applications Running on the Internet
If you are accessing your cluster from the Internet, you will need to authorize a Classless Inter-Domain
Routing IP (CIDR/IP) address range. For this example, we will use a CIDR/IP rule of 192.0.2.0/24; you
will need to modify this range to reflect your actual IP address and netmask.
API Version 2012-12-01
136
Amazon Redshift Management Guide
Setting Up the Amazon Redshift CLI