Amazon Redshift View-Based Pre-Configuration Details

This page describes the Amazon Redshift view-based integration, configuration options, and features. For a tutorial to enable this integration, see the installation guide.

Feature Availability

Prerequisites

  • For automated installations, the credentials provided must be a superuser or have the ability to create databases and users and modify grants.

Supported Features

Authentication Methods

The Amazon Redshift view-based integration supports the following authentication methods to configure the integration and create data sources:

  • Username and Password: Users can authenticate with their Redshift username and password.

  • AWS Access Key: Users can authenticate with an AWS access key.

Tag Ingestion

Immuta cannot ingest tags from Redshift, but you can connect any of these supported external catalogs to work with your integration.

User Impersonation

Required Redshift privileges

Setup User:

  • OWNERSHIP ON GROUP IMMUTA_IMPERSONATOR_ROLE

  • CREATE GROUP

Immuta System Account:

  • GRANT EXECUTE ON PROCEDURE grant_impersonation

  • GRANT EXECUTE ON PROCEDURE revoke_impersonation

Impersonation allows users to query data as another Immuta user in Redshift. To enable user impersonation, see the User Impersonation page.

Multiple Integrations

Users can enable multiple Amazon Redshift view-based integrations with a single Immuta tenant.

Redshift Limitations

  • The host of the data source must match the host of the connection for the view to be created.

  • When using multiple Amazon Redshift view-based integrations, a user has to have the same user account across all hosts.

  • Case sensitivity of database, table, and column identifiers is not supported. The enable_case_sensitive_identifier parameter must be set to false (default setting) for your Redshift cluster to configure the integration and register data sources.

Last updated

Was this helpful?