Amazon Redshift

​

Introduction

​

MoEngage × Redshift

​

Integration

​

Step 1: Make sure your Redshift cluster is publicly accessible

• When creating a new Redshift Cluster, under the “Network and Security” section, select the “Turn on Publicly accessible” option.
• If you already have a Redshift cluster, under the Properties tab, look for Network and Security section. Click on the “Edit” button.

In the properties, turn on publicly accessible and then save

​

Step 2: Create a new database user for MoEngage

-- create a new user with a strong password
CREATE USER <username> PASSWORD <password>;
-- create a new schema where MoEngage will dump data
-- you can skip this if you want to use existing schema
CREATE SCHEMA IF NOT EXISTS <schema_name>;
-- grant create access on the above schema or existing schema
GRANT CREATE, USAGE ON SCHEMA <schema_name> TO <username>;

​

Step 3: Allow MoEngage IPs to access your cluster

​

Create a new Security Group

1. Give your Security Group a name, and an optional description.
2. Select the VPC (by default, it is already selected).
3. Add a new inbound rule with the following details:

4. Leave the outbound rules empty.
5. Click on “Create security group” when done.

​

Edit an existing Security Group

1. Click on the “Actions” button on the security group page and select “Edit inbound rules”.
2. Add a new inbound rule according to the table provided above.
3. Click “Save rules” when done.

​

Attach the Security Group to your Redshift Cluster

1. From your Redshift Console, open your Redshift cluster. Go to the Properties tab.
2. In the “Network & Security settings” section, click on the “Edit” button.
3. Under the VPC security groups, select the Security Group you just created/edited.
4. Click “Save changes” when done.

​

Step 4: Create a new IAM Policy

1. From the IAM Console, under Access Management, go to Policies. Click on the “Create policy” button.
2. On the Create Policy page, switch to the JSON tab and paste the following policy:
   JSON

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "VisualEditor1",
               "Effect": "Allow",
               "Action": [
                   "s3:Get*",
                   "s3:List*"
               ],
               "Resource": [ "<bucket-arn>",
                             "<bucket-arn>/*"]
           }
       ]
   }
   

Click “Next” and optionally, add tags. Then click on “Next: Review”.

3. Give the Policy a name, and an optional description. Click “Create policy” when ready.

​

Step 5: Create a new Redshift IAM role

1. From the IAM Console, under Access Management, go to Roles. Click on the “Create role” button.
2. Choose the Trusted entity type as “AWS service”. Under Use Case, select “Redshift ” from “Use cases for other AWS services”. Under the types of Redshift use cases, select “Redshift - Customizable ”. Click “Next” when ready.
3. In the next step, select the policy that you created in Step 4. Click Next when done.
4. Give your role a name, and review if you have attached the correct policy that you made earlier. Click on Create Role when ready.

​

Step 6: Attach this role to your Redshift cluster

1. Under the Properties tab, go to the “Associated IAM roles” section.
2. Click on the “Manage IAM roles” button, and then select the “Associate IAM roles” option.
3. From the popup modal, select the Role that you just created in Step 5.

4. Click on “Associate IAM roles” to attach this role to your Redshift cluster.

​

Supported Datetime Formats

​

Export Events from MoEngage to Redshift