Enable Redshift imports

Enable Redshift data imports in CARTO Self-Hosted

To import data into Redshift through CARTO Self-Hosted, follow these step-by-step instructions.

This requires access to an AWS account and an existing accessible Redshift endpoint.

1. Create an AWS IAM user

Create an IAM user with programmatic access. Take note of the user's ARN, Access Key ID, and Secret Access Key.

2. Create an AWS S3 Bucket

Create an S3 bucket with the following settings:

• ACLs should be allowed.

• If server-side encryption is enabled, the user must be granted permissions over the KMS key following the AWS documentation.

3. Create an AWS IAM role

Create an IAM role with the following settings:

1. Trusted entity type: Custom trust policy.

2. Custom trust policy: Make sure to replace <your_aws_user_arn>.

{
  "Version": "2012-10-17",
  "Statement": [
      {
          "Effect": "Allow",
          "Principal": {
              "AWS": "<your_aws_user_arn>"
          },
          "Action": [
              "sts:AssumeRole",
              "sts:TagSession"
          ]
      }
  ]
}

1. Add permissions: Create a new permissions policy, replacing <your_aws_s3_bucket_name>.

{
   "Version": "2012-10-17",
   "Statement": [
       {
           "Effect": "Allow",
           "Action": "s3:ListBucket",
           "Resource": "arn:aws:s3:::<your_aws_s3_bucket_name>"
       },
       {
           "Effect": "Allow",
           "Action": "s3:*Object",
           "Resource": "arn:aws:s3:::<your_aws_s3_bucket_name>/*"
       }
   ]
}

4. Configure your CARTO Self-Hosted deployment

Set the IAM role ARN, access key ID, and secret access key in your deployment:

☸️ Kots (Admin Console)

Kots

In the Admin Console, locate the AWS S3 bucket configuration and set the bucket behavior to Custom AWS S3. Fill in:

• AWS arn bucket role — the import role ARN (maps to importAwsRoleArn)

• The AccessKey ID for S3 buckets — your AWS access key ID (maps to importAwsAccessKeyId)

• The AccessKey Secret for S3 buckets — your AWS secret access key (maps to importAwsSecretAccessKey)

If you need import credentials that differ from your bucket credentials, set the keys shown in the Helm tab through the Custom Configuration field instead.

🛞 Helm (customizations.yaml)

Helm

Add the following lines to your customizations.yaml file:

appConfigValues:
  importAwsRoleArn: "<your_aws_user_arn>"

appSecrets:
  importAwsAccessKeyId:
    value: "<your_aws_user_access_key_id>"
  importAwsSecretAccessKey:
    value: "<your_aws_user_access_key_secret>"

5. Apply the configuration changes

Deploy the updated configuration to apply the changes to your CARTO Self-Hosted instance.

6. Configure Redshift integration in CARTO

1. Log into CARTO Self-Hosted, go to Data Explorer → Connections → Add new connection and create a new Redshift connection.

2. Go to Settings → Advanced → Integrations → Redshift → New, enter your S3 Bucket name and region, and copy the policy generated.

3. From the AWS console, go to S3 → Bucket → Permissions → Bucket policy and paste the policy from the previous step.

4. Go back to the CARTO Self-Hosted Redshift integration page, check I have already added the S3 bucket policy, and click Validate and save.

7. Import data to Redshift

Go to Data Explorer → Import data → Redshift connection. You should now be able to import a local dataset to Redshift! 🎉