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

Page Not Found

The page or file you are looking for has been moved or no longer exists.

The following links might help you find the content you need:


You can also search the Documentation Portal or visit the home page.

English
  • Data Integration Connectors
  • All Products

Table of Contents

Search

  1. Part 1: Introduction to Amazon Redshift connectors
  2. Part 2: Data Integration with Amazon Redshift V2 Connector
  3. Part 3: Data Integration with Amazon Redshift Connector

Amazon Redshift Connectors

Amazon Redshift Connectors

Back Next

Prepare for authentication

Prepare for authentication

You can configure
Default
 and
Redshift IAM Authentication via AssumeRole
 authentication types in an Amazon Redshift V2 connection to connect to Amazon Redshift.
Before you begin, you need to create a registered user account with Amazon Redshift in the AWS console.
Refer to the following sections to understand the requirements for each authentication type and configure the prerequisites accordingly.

Default authentication

To use the Default authentication, you need at a minimum the JDBC URL, the user name, and password of your Amazon Redshift account.
Additionally, to stage the data on Amazon S3, you can choose from the following methods and specify the required properties in the Amazon Redshift V2 connection:
  • Use the
    S3 Access Key ID
     and
    S3 Secret Access Key
     details to gain access to S3 resources. To do this, perform the following tasks:
    1. Configure a minimal Amazon IAM policy. For instructions, see Create a minimal Amazon IAM policy.
    2. Create an IAM user, assign the policy to that user, and then generate the S3 access key ID and S3 secret access key in the AWS console.
      For more information about how to create an IAM user and generate keys, see the AWS documentation.
  • Configure an AssumeRole to enable S3 IAM users to assume an S3 IAM role
    or define an EC2 instance to assume an S3 IAM role
    and generate temporary security credentials for Amazon S3 staging.
    For instructions, see Configure an assume role for Amazon S3 staging. To know more about the AssumeRole for S3 staging, you can also check the following How-To Library article: Using an assume role for Amazon S3 resources
    • To use the AssumeRole for the S3 IAM role, specify the
      S3 IAM role ARN
      , along with the
      S3 Access Key ID
       and
      S3 Secret Access Key
       values of the user who assumes the S3 IAM role.
    • To use the AssumeRole for the EC2 instance to assume an S3 IAM role, enable the
      Use EC2 Role to Assume Role
       property. In this case, you do not have to specify the S3 access key ID and secret access key in the connection.
  • Configure IAM authentication. Assign the EC2 role with the minimum S3 policy in AWS. For instructions, see IAM authentication. When you create a connection, you do not have to explicitly specify the S3 access key ID and S3 secret access key.

Redshift IAM authentication via AssumeRole

To use the Redshift IAM authentication using the AssumeRole, you need at a minimum the JDBC URL, user name, database name, and the cluster identifier of your Amazon Redshift account. You also need to specify the Redshift IAM role ARN.
Configure the Redshift IAM role ARN with the required trust policies to generate temporary security credentials to access Amazon Redshift. You can either configure an AssumeRole to enable Redshift IAM users or define an EC2 instance to assume a Redshift IAM role and generate temporary security credentials to access Amazon Redshift.
For instructions, see Configure an assume role for Amazon Redshift. To know more about AssumeRole configurations, you can also check the following How-To Library article: Using an assume role for Amazon Redshift
  • To use the AssumeRole for the Redshift IAM user, specify the
    Redshift Access Key ID
     and
    Redshift Secret Access Key
     of the IAM user in the connection.
  • To use the AssumeRole for Amazon EC2, specify the Redshift IAM Role ARN and enable the
    Use EC2 Role to Assume Role
     field in the connection.
If you require S3 staging, you can follow the methods defined in the Default authentication section.
To configure client-side and server-side encryption for the Default authentication and Redshift IAM authentication via AssumeRole, see Enable encryption.
0 COMMENTS
We’d like to hear from you!