Redshift Integration Prerequisite Checklist

This page offers a prerequisite checklist focused on customer's Redshift integration that would help answer questions beforehand

Deployment Patterns

Which deployment pattern and/or combination of the below patterns do you have?

• Single-AZ Deployment: This is the traditional deployment pattern where a Redshift cluster is deployed within a single Availability Zone (AZ).

• Multi-AZ Deployment: This is a more recent deployment pattern where a Redshift cluster is deployed across two Availability Zones.

• Redshift Serverless: This option allows you to run Redshift without managing infrastructure. It automatically scales resources based on your workload demands and offers a pay-per-use pricing model.

• RA3 Node Types with Redshift Managed Storage (RMS): These node types store data in RMS, which is backed by Amazon S3, providing high availability and durability by default

Networking Infrastructure

Do you have any of the following that you think would be a constraint in successfully establishing the Immuta - Redshift integration;

• PrivateLink

• IP Filtering

• VPC peering in between Redshift Clusters

User Authentication and Cluster Security

There are several authentication methods for users to securely access clusters and databases. Immuta supports limited number of authentication methods. Which one(s) do the customer use for their Redshift clusters?

• Traditional username and password

• AWS Access Key

• AWS IAM (Identity and Access Management) Authentication

  • IAM users and/or roles to authenticate using temporary credentials generated by STS?

  • Federated Access with Single Sign-on (SSO) that allows the integration with other SAML 2.0 based identity providers, such as Okta or Microsoft ADFS (Active Directory Federation Services)

• AWS Secrets Manager

• Amazon Cognito for web-based apps consuming data from Redshift

• Microsoft Active Directory or any other flavours of AD

Immuta Configuration Specifics

Immuta Redshift integration comes with a few different types. Which ones from the following are best suited to your requirements?

• Redshift and/or Redshift Serverless

• Redshift Spectrum (as External Tables)

  • Use an existing database

  • Create a new Immuta database

Documentation Review Recommendation

• Go through the official Redshift-Immuta integration documentation thoroughly and note any questions or concerns.

• Review the manual script thoroughly to understand what SQL statements are executed to setup the integration framework and Immuta integration database on Redshift.