Create S3 Bucket: Sprinkle stores all intermediate data and report caches in this bucket
Step by Step Guide
STEP-1: Allow Redshift to accept connection from Sprinkle
Redshift cluster should be there with Publicly Accessible as Enabled. If not, enable it.
Create a security group to allow inbound connection on port 5439 from Sprinkle IPs (18.104.22.168, 22.214.171.124).
Add the security group to your Redshift cluster.
STEP-2: Configure Redshift Connection
Log into Sprinkle application
Navigate to Admin -> Drivers -> Create Warehouse
Provide all the mandatory details
Distinct Name: Name to identify this connection
JDBC URL : Redshift console -> Clusters -> Choose the cluster -> Copy the JDBC url from General Information. It will be of the following form jdbc:redshift://<xxxxx.xxxxxxxxxx>.redshift.amazonaws.com:5439/
SSH Tunnel in Redshift:
Connect via SSH Host: Click on "Yes" to configure SSH Tunnel.
SSH Host* : IP address or hostname of the SSH server
SSH Public Key* : Copy the SSH public key and paste it into the ~/.ssh/authorized_keys file of the SSH user on the ssh host machine
SSH Login Username* : Provide the SSH Login Username where you added the public key. Further, verify the provided details by testing the connection.
Networking rules from your end:
Make sure SSH Host has public IP
Whitelist Sprinkle IPs (126.96.36.199, 188.8.131.52) in your SSH Host. SSH host should be able to accept traffic from these Sprinkle IPs.
Make sure SSH port 22 is open.
Once this setting is completed you can try test-connection and if successful, you can update the changes.
Create S3 Bucket
Sprinkle requires S3 Bucket to store intermediate data and report caches. Follow the below steps to create and configure S3 bucket:
STEP-1: Create a S3 bucket
Create a S3 bucket, provide any name like “sprinkle” in the same location/region as the Redshift cluster.
STEP-2: Create an IAM user for S3 access
Create a new IAM user, provide any name like “sprinkle-s3-user”. Select credential type as Access key. Create an inline policy as below. Make sure to use the actual bucket name in place of BUCKET_NAME:
From the credentials tab, get the Access Key Id and Secret Key of the IAM user.