In this segment, you will learn how to set up a Redshift cluster.
The following steps will guide you through the process of setting up your Redshift cluster.
Before you start with configuring a Redshift cluster, you first need to create your own S3 bucket and upload the objects to it by following the steps mentioned in the document attached below.
Note:
Make sure that the S3 bucket and the Redshit cluster are created in the same region – US East (N.Virginia) (us-east-1).
The next step is to create an IAM role to allow the Redshift servicce to access the S3 bucket by creating a full access policy which will then be attached to your Redshift cluster. The following video will show you the steps to do this.
NOTE:
Please note that in AWS Academy, since IAM service cannot be used to create new roles, you can skip this and move on to the next step. But, in actual practice, IAM roles need to be used while you’re working with Redshift in a production environment.
NOTE:
The documentation below contain the steps to create an S3full access role. In AWS Academy, a role ‘myRedshiftRole’ has already created for read-only access of S3 buckets through Redshift.
With the IAM role and S3 bucket ready, you can now proceed with creating a Redshift cluster.
Important Note:
- The cluster subnet creation step, followed in the cluster creation video, is one-time only and you only need to do it once for your AWS account. You can then use this subnet for all future Redshift clusters that you create as well.
- During the cluster creation process, you will need to use the VPC that you would have created during the Introduction to Cloud and AWS module for your EC2instance. If you haven’t already created a VPC, please follow this document to setup a VPC on your AWS account.
The steps followed in the video above are detailed in the document attached below.
The following document has the steps that were followed in the video above to set up IAM policy for accessing S3 bucket on your Redshift cluster.
Please do a walkthrough of the Redshift cluster console to get a better understanding of each option available in the Redshift Cluster.
In this segment, you learnt how to create a Redshift cluster and maintain it in an optimal manner. You also understood the usage of different types of nodes.
Now, as mentioned in the video above, it is important that after you have worked on your AWS Redshift cluster, you should pause it so that the running Redshift cluster does not consume your budget unnecessarily. Please note that even after pausing the cluster, it will still consume some budget so it is advised that if you are not going to be using the same cluster for a long time, then you straightaway delete the cluster instead. The following video will show you the steps to pause your Redshift cluster.
The following document contains the steps discussed in the video above to pause a Redshift cluster.
Please note that clicking on the Stop button in AWS Academy dashboard page does not affect the Redshift cluster when you restart AWS Academy. The cluster has to be terminated from within the AWS management console page in the Redshift service.
The steps to create a Redshift cluster are straightforward, hence we would highly recommend you to create a new cluster every time you want to practice Redshift and delete the cluster once you are done. Please plan your practice accordingly so that you are able to sit in long stretch for the practice.
In the next segment, you will learn about cluster maintenance.
Important Note:
Amazon Redshift is a costly service of AWS. Hence, to avoid burning up your monthly AWS budget, please make sure to Pause your Redshift cluster during the module week(when you’re learning/practicing Redshift. However, you can also choose to terminate it if there is any kind of break while you are going through the module).
Please follow the steps below to delete the Redshift cluster. This must be done to avoid burning your AWS budgets.
It’s alway recommended that you either pause or terminate your Redshift cluster before you stop the AWS Academy Lab.
When you click on Stop Lab button on AWS Academy, any running Redshift cluster will not be visible when you refresh the page. The next time you start the lab, any unpaused/unterminated cluster will start automatically. This may lead to unnecessary chanrges to your AWS Academy Lab.
Therefore, make sure to pause or terminate your cluster after you’ve completed your work.