Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Configuring AssumeRole Authentication for Amazon Redshift V2 Connector

Configuring AssumeRole Authentication for Amazon Redshift V2 Connector

Overview

Overview

You can use the AssumeRole authentication to securely access an Amazon Redshift database. Instead of storing the static database credentials, you can generate temporary security credentials through an IAM role configured with trust policies to connect to an Amazon Redshift database.
You can enable both new and existing database users to connect to Redshift using AssumeRole. You can configure IAM users and EC2 instances to assume the designated IAM role for authentication.
Additionally, you can enable cross-account access where the Redshift cluster, S3 bucket, and Redshift IAM role ARN reside in one account, and the IAM users or EC2 instances are in a different account. In this scenario, you need to configure the user accounts to assume the role in the Redshift cluster account.
The following image shows how Amazon Redshift V2 Connector uses temporary security credentials to connect to an Amazon Redshift database:
Amazon Redshift V2 Connector uses AWS STS to request temporary security credentials via
        the GetClusterCredentials API, which then enable the Redshift client to securely connect to
        Amazon Redshift.

0 COMMENTS

We’d like to hear from you!