Supply Chain & Retail Solutions user guide

Connecting a Redshift data warehouse (private connectivity)

Prerequisites​

• RA3 node type — other node types do not support cluster relocation or enhanced VPC routing.
• Multi-subnet — the cluster must have subnets in at least two different availability zones.
• Cluster relocation enabled — allows the cluster to be moved to another availability zone without data loss.
• Enhanced VPC routing enabled — ensures COPY and UNLOAD traffic does not use the public internet.
• A data lake is already configured in Peak in the same region as your Redshift cluster.
• An S3 gateway endpoint must be created in the same region as the Redshift cluster. See Creating an S3 gateway endpoint.

Steps​

1. In Peak, open Manage and select Data Bridge.

2. Select Add data warehouse.

3. Enter a unique name for the connection and select Amazon Redshift.

   • The name must be unique to your Peak organization.
   • Use only alphanumeric characters and underscores. No spaces or other special characters.
   • Minimum 3 characters, maximum 40 characters.
   • Must start and end with an alphanumeric character.
   • The name cannot be changed after the connection has been set up.

4. Select the region where your Redshift cluster is hosted. Ensure the region complies with your data localization requirements.

   Supported regions: Ireland (eu-west-1), London (eu-west-2), Mumbai (ap-south-1), North California (us-west-1), North Virginia (us-east-1).

5. Select Private connectivity.

6. Copy the Peak AWS account ID displayed in the configuration step.

7. In AWS, grant Peak access to your Redshift cluster:

   • Open the Redshift console and select your cluster.
   • On the Properties tab, scroll to Granted accounts and select Grant access.
   • Enter the Peak AWS account ID copied in the previous step.
   • Select Grant access to all VPCs and confirm.

8. In Peak, enter the cluster identifier (your AWS cluster name) and select the confirmation checkbox.

9. Select Next to proceed to the database step.

10. Enter the database credentials. See Credential fields.

11. In the Data lake step, select the data lake connection to link.

12. Set up the Redshift IAM role for data lake access. See Configuring the Redshift IAM role.

13. Review the configuration and select Finish.

Credential fields​

Configuring the Redshift IAM role​

1. In Peak, copy the Redshift IAM role policy from the Data lake step.
2. In the AWS IAM console, go to Access management > Policies and create a new policy. Paste the copied JSON on the JSON tab, then save the policy.
3. In Access management > Roles, select the role attached to your Redshift cluster.
4. Select Add permissions > Attach policies and attach the policy you just created.
5. Ensure the AmazonRedshiftAllCommandsFullAccess managed policy is also attached to this role.
6. In Peak, copy the Trusted entity policy from the Data lake step.
7. In the same IAM role, select Edit trust relationship, paste the copied JSON, and save.
8. Copy the IAM role ARN from the role's Summary section.
9. Paste the role ARN into the IAM role ARN field in Peak.

Creating an S3 gateway endpoint​

1. In the AWS console, go to VPC > Endpoints and select Create endpoint.
2. Enter an endpoint name.
3. Under Service category, select AWS services.
4. In the Service list, search for S3 and select the result with type Gateway.
5. Select the VPC where your Redshift cluster is hosted.
6. Select the route table associated with the Redshift cluster's subnet.
7. Under Policy, select Full access.
8. Select Create endpoint.

Result​