{"id":169,"date":"2015-11-17T14:47:38","date_gmt":"2015-11-17T14:47:38","guid":{"rendered":"http:\/\/zappysys.com\/blog\/?p=169"},"modified":"2015-12-18T14:25:50","modified_gmt":"2015-12-18T14:25:50","slug":"how-to-setup-amazon-redshift-cluster-for-outside-data-access","status":"publish","type":"post","link":"https:\/\/zappysys.com\/blog\/how-to-setup-amazon-redshift-cluster-for-outside-data-access\/","title":{"rendered":"How to setup Amazon Redshift Cluster in few clicks"},"content":{"rendered":"

Introduction<\/h2>\n

In this article\u00a0you will learn how to Setup Amazon Redshift Cluster<\/em> in few clicks. You will also learn how to set Inbound and Outbound Firewall Rules so you can access Redshift Cluster from outside of AWS Network (e.g. from your corporate network or your home). By default Redshift Cluster cannot be access from outside of your AWS Virtual Network (referred as\u00a0VPC – Virtual Private Cloud)<\/p>\n

Once Redshift Cluster is setup you can follow these steps to Load data into Redshift<\/a>\u00a0(Using SSIS Redshift Data Transfer Task<\/a> or Command line for Redshift<\/a>)<\/p>\n

What is Amazon Redshift<\/h2>\n

Amazon Redshift<\/em> is a fully managed, petabyte-scale data warehouse<\/em> service in the cloud<\/em>. You can start with just a few hundred gigabytes of data and scale to a petabyte or more. This enables you to use your data to acquire new insights for your business and customers.<\/p>\n

The first step to create a data warehouse is to launch a set of nodes, called an Amazon Redshift cluster<\/em>. After you provision your cluster, you can upload your data set and then perform data analysis queries. Regardless of the size of the data set, Amazon Redshift offers fast query performance using the same SQL-based tools and business intelligence applications that you use today.<\/p>\n

Setup Amazon Redshift Cluster<\/span><\/h2>\n
\n

NOTE: Skip this step if you already setup you Redshift Cluster<\/em><\/p>\n

    \n
  1. Login to your AWS Console and Click on Redshift icon. Or click here<\/span><\/a> to land directly to redshift<\/li>\n
  2. Click on Launch Cluster<\/li>\n
  3. On Cluster Detail Page specify Cluster Identifier, Database Name, Port, Master User and Password. Click Continue to go to next page\n
    \n

    \"Configure<\/a><\/p>\n

    Configure Redshift Cluster Identifier, Database Name, Port , UserID and Password<\/p>\n<\/div>\n<\/li>\n

  4. On Node Configuration Page specify Node Type (This is VM Type), Cluster Type and Number of Node. If you are trying under Free Tire then select smallest Node possible (in this case it was dw2.large). Click Continue to go to next page\n
    \n

    \"Configure<\/a><\/p>\n

    Configure Redshift Node Type and Cluster Type<\/p>\n<\/div>\n<\/li>\n

  5. On Additional Configuration Page you can pick VPC (virtual private connection), Security group for Cluster and other options for Encryption. For demo purpose select as below screenshot . Click Continue to review your settings and click Create Cluster\n
    \n

    \"Configure<\/a><\/p>\n

    Configure Redshift Cluster Encryption, VPC and Additional Detail<\/p>\n<\/div>\n<\/li>\n

  6. Give it few mins while your cluster is being created. After few minutes (5-10 mins) you can go back to same page and review cluster Status and other properties as below. Copy Cluster Endpoint to somewhere because we will need it later.\n
    \n

    \"Check<\/a><\/p>\n

    Check Redshift Cluster Status , Endpoint and Other Properties<\/p>\n<\/div>\n<\/li>\n<\/ol>\n<\/div>\n

    Add inbound rule for Redshift Cluster<\/span><\/h2>\n
    NOTE: Skip this step if you have already added your IP to inbound exclusion rule.<\/em>
    \nBy default you cannot connect to Amazon Redshift cluster from outside AWS Network (e.g. from your On-Premises Machine). If you wish to connect then you must add inbound exception rule to allow your request to redshift cluster on specific port.<\/div>\n
    \n

    To add create new inbound rule perform following steps<\/p>\n

      \n
    1. Under Redshift home page click [Security] tab. You may see following Notice depending on which region you are. Click on [Go to the EC2 Console] link or you can direct go to EC2 by clicking Services -> EC2 menu at the top\n
      \n

      \"Configure<\/a><\/p>\n

      Configure Security Group and Inbound Filter Firewall Rule to allow Local Connection<\/p>\n<\/div>\n<\/li>\n

    2. On EC2 Security Groups Page select Security group attached with your Redshift Cluster and then in the bottom pane click on Inbound Tab\n
      \n

      \"Security<\/a><\/p>\n

      Security Group Screen \u2013 Add or Edit Inbound Firewall Rule to allow Local Connection<\/p>\n<\/div>\n<\/li>\n

    3. On Inbound Tab click Edit option to modify default entry or you can add new Rule. Notice how IP Range is specified.. 0.0.0.0\/0 means all IP. If you wish to add range then you have to set something like this… 50.34.234.10\/250\u00a0 .. this will cover 50.34.234.10 to 50.34.234.250 IP range. Make sure your port range covers Port you specified for Redshift cluster.<\/li>\n
    4. Click on Add rule if you wish to add new entry else edit as below and click save<\/li>\n<\/ol>\n<\/div>\n

      Automate Redshift Cluster Creation<\/h2>\n

      If you have need to automate Redshift Cluster Creation or any of the following things automatically then check Redshift Cluster management Task<\/a><\/p>\n