Amazon Redshift provisioned clusters - Amazon Redshift

Amazon Redshift provisioned clusters

If you are a first-time user of Amazon Redshift, this tutorial gets you started using Amazon Redshift clusters. To get started using Redshift Serverless, see Amazon Redshift Serverless.

After you have created and signed in to the Amazon Redshift provisioned console, you can create and manage Amazon Redshift objects, including clusters, nodes, and databases. You can also run queries, view queries, and perform other SQL data definition language (DDL) and data manipulation language (DML) operations with a SQL client.

Important

The cluster that you provision for this exercise runs in a live environment. As long as it's running, it accrues charges to your AWS account. For pricing information, see the Amazon Redshift pricing page.

To avoid unnecessary charges, delete your cluster when you are done with it. The final step of the tutorial explains how to do so.

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

We recommend that you begin by going to the Provisioned clusters dashboard to get started using the Amazon Redshift console.

Depending on your configuration, the following items appear in the navigation pane of the Amazon Redshift provisioned console:

  • Redshift Serverless – Access and analyze data without the need to set up, tune, and manage Amazon Redshift provisioned clusters.

  • Provisioned clusters dashboard – View the list of clusters in your AWS Region, check Cluster metrics and Query overview for insights to metrics data (such as CPU utilization) and query information. Using these can help you determine if your performance data is abnormal over a specified time range.

  • Clusters – View your list of clusters in this AWS Region, choose a cluster to start querying, or perform cluster-related actions. You can also create a new cluster from this page.

  • Query editor – Run queries on databases hosted on your Amazon Redshift cluster. We recommend using the Query editor v2 instead.

  • Query editor v2 – Amazon Redshift query editor v2 is a separate web-based SQL client application to author and run queries on your Amazon Redshift data warehouse. You can visualize your results in charts and collaborate by sharing your queries with others on your team.

  • Queries and loads – Get information for reference or troubleshooting, such as a list of recent queries and the SQL text for each query.

  • Datashares – As a producer account administrator, either authorize consumer accounts to access datashares or choose not to authorize access. To use an authorized datashare, a consumer account administrator can associate the datashare with either an entire AWS account or specific cluster namespaces in an account. An administrator can also decline a datashare.

  • Zero-ETL integrations – Manage integrations that make transactional data available in Amazon Redshift after being written in supported sources.

  • IAM Identity Center connections – Configure the connection between Amazon Redshift and IAM Identity Center.

  • Configurations – Connect to Amazon Redshift clusters from SQL client tools over Java Database Connectivity (JDBC) and Open Database Connectivity (ODBC) connections. You can also set up an Amazon Redshift–managed virtual private cloud (VPC) endpoint. Doing so provides a private connection between a VPC based on the Amazon VPC service that contains a cluster and another VPC that is running a client tool.

  • AWS Partner Integration – Create integration with a supported AWS Partner.

  • Advisor – Get specific recommendations about changes you can make to your Amazon Redshift cluster to prioritize your optimizations.

  • AWS Marketplace – Get information on other tools or AWS services that work with Amazon Redshift.

  • Alarms – Create alarms on cluster metrics to view performance data and track metrics over a time period that you specify.

  • Events – Track events and get reports on information such as the date the event occurred, a description, or the event source.

  • What's new – View new Amazon Redshift features and product updates.

In this tutorial, you perform the following steps.


         The steps in this tutorial, outlined following

Signing up for AWS

If you don't already have an AWS account, sign up for one. If you already have an account, you can skip this prerequisite and use your existing account.

  1. Open https://portal.aws.amazon.com/billing/signup.

  2. Follow the online instructions.

    Part of the sign-up procedure involves receiving a phone call and entering a verification code on the phone keypad.

    When you sign up for an AWS account, an AWS account root user is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to an administrative user, and use only the root user to perform tasks that require root user access.

Determine firewall rules

Note

This tutorial assumes your cluster uses the default port 5439 and Amazon Redshift query editor v2 can be used to run SQL commands. It doesn't go into details about networking configurations or setting up a SQL client that might be necessary in your environment.

In some environments, you specify a port when you launch your Amazon Redshift cluster. You also create an inbound ingress rule in a security group to allow access through the port to your cluster.

If your client computer is behind a firewall, make sure that you know an open port that you can use. Using this open port, you can connect to the cluster from a SQL client tool and run queries. If you don't know an open port, work with someone who understands your network firewall rules to determine an open port in your firewall.

Though Amazon Redshift uses port 5439 by default, the connection doesn't work if that port isn't open in your firewall. You can't change the port number for your Amazon Redshift cluster after it's created. Thus, make sure that you specify an open port that works in your environment during the launch process.