Configuring AssumeRole Authentication for Amazon Redshift V2 Connector

Configuring AssumeRole Authentication for Amazon Redshift V2 Connector

AssumeRole with Cross-account access in Redshift

AssumeRole with Cross-account access in Redshift

You can enable cross-account access for AssumeRole authentication. Attach the AWS IAM user policies for access key and secret key and trust policy to define which user can assume the Redshift role. Based on the use case, you can define the policy either for a new user or an existing user in Redshift database.

Enabling trust and permission policies for cross-account access

Let's consider a use case where the Redshift cluster, S3 bucket, and Redshift IAM Role ARN are in the same account, for example Account A. The IAM user whose access key and secret key you configure in the connection properties resides in Account B.
Enable the following policies for cross-account access:
  • Trust policy of the Redshift IAM Role ARN in Account A:
    Cross account policy for IAM Role ARN for Acc A
  • Permission policy of the IAM user in Account B:
    Trust policy for account B

0 COMMENTS

We’d like to hear from you!