Granting Alooma access to your Redshift cluster can be done in a few simple steps, some of which are optional:
Step 1 - Authorizing Cluster Access
Are you planning to connect to Redshift via SSH? If so, skip ahead to Step 2.
For Alooma to be able to access your Redshift cluster directly, you'll need to create a security group where you've whitelisted the Alooma IP addresses from which we'll communicate with your cluster.
- From the Redshift Dashboard, click on Clusters.
- In the list of clusters, choose your cluster.
- In the Configuration tab of the clusters detail page, under the VPC Security Groups section, click the name of the security group.
- In the security group view, select the Inbound tab on the bottom half of the page, then in that tab click Edit.
- In the Edit inbound rules dialog you'll add the IP addresses that Alooma can use to access the cluster. To add a new rule, click Add Rule at the bottom of the list, and set the following:
- Type - Redshift.
- Protocol - TCP (the default).
- Port Range - The number of the open port (Redshift's default is 5439).
- Source - Custom IP (the default). In the field next to Source, paste the following IP address: 184.108.40.206/32
- Repeat the Add Rule steps above for each of these additional IPs: 220.127.116.11/32, 18.104.22.168/32, and 22.214.171.124/32.
Note that you can rename a security group by hovering over the group name and clicking the pencil icon.
While this step is optional, we recommend that you create a username and password for Alooma to use specifically for table creation and editing. If you don't create a username and password you can specify an existing user and schema for us to connect to.
To create, connect to your Redshift cluster from your SQL console of choice (e.g. SQL Workbench/J). From there, you'll run the following 2 commands:
- Create a user named alooma with a password of your choice.
CREATE USER alooma WITH PASSWORD '<>'
- Create a schema named alooma and grant us owner permissions.
CREATE SCHEMA alooma AUTHORIZATION alooma;