Table of Contents

Search

  1. Preface
  2. Connectors and connections
  3. Connection configuration
  4. Connection properties
  5. Swagger file generation for REST V2 connections

Connections

Connections

Amazon Redshift V2 connection properties

Amazon Redshift V2 connection properties

When you set up an Amazon Redshift V2 connection, configure the connection properties.
The following table describes the Amazon Redshift V2 connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Type
The Amazon Redshift V2 connection type.
Runtime Environment
Name of the runtime environment where you want to run the tasks.
Select a Secure Agent, Hosted Agent, or serverless runtime environment.
You cannot run an application ingestion task, database ingestion task, file ingestion task, or streaming ingestion task on a Hosted Agent or serverless runtime environment.
Hosted Agent is not applicable for mappings that run on an advanced cluster.
Username
User name of the Amazon Redshift account.
Password
Password for the Amazon Redshift account.
Access Key ID
Access key to access the Amazon S3 staging bucket.
Enter the access key value based on the following authentication methods:
  • Basic authentication. Enter the actual access key value.
  • IAM authentication.
    Do not enter the access key value.
  • Temporary security credentials using assume role. Enter access key of an IAM user with no permissions to access the Amazon S3 staging bucket.
  • Assume role for EC2.
    Do not enter the access key value.
If you use the connection for application ingestion or database ingestion tasks that use key-based authentication, provide the access key value.
Secret Access Key
Secret access key to access the Amazon S3 staging bucket.
The secret key is associated with the access key and uniquely identifies the account.
Enter the access key value based on the following authentication methods:
  • Basic authentication. Enter the actual access secret value.
  • IAM authentication.
    Do not enter the access secret value.
  • Temporary security credentials using assume role. Enter access secret of an IAM user with no permissions to access Amazon S3 staging bucket.
  • Assume role for EC2.
    Do not enter the access secret value.
If you use the connection for application ingestion or database ingestion tasks that use key-based authentication, provide the access key value.
IAM Role ARN
The Amazon Resource Number (ARN) of the IAM role assumed by the user to use the dynamically generated temporary security credentials.
Set the value of this property if you want to use the temporary security credentials to access the Amazon S3 staging bucket.
For more information about how to get the ARN of the IAM role, see the AWS documentation.
If you use the connection for application ingestion or database ingestion tasks that uses role-based authentication, but not the default role for the AWS cluster, specify an IAM role ARN. If you use the default role, leave this field blank.
External Id
The external ID for a more secure access to the Amazon S3 bucket when the Amazon S3 staging bucket is in a different AWS account.
Does not apply to application ingestion and database ingestion tasks.
Use EC2 Role to Assume Role
Optional. Select the check box to enable the EC2 role to assume another IAM role specified in the IAM Role ARN option.
The EC2 role must have a policy attached with a permission to assume an IAM role from the same or different account.
Does not apply to application ingestion and database ingestion tasks. By default, this check box is not selected.
Master Symmetric Key
1
A 256-bit AES encryption key in the Base64 format when you enable client-side encryption. You can generate a key using a third-party tool.
Does not apply to application ingestion and database ingestion tasks.
JDBC URL
The URL of the Amazon Redshift V2 connection.
Enter the JDBC URL in the following format:
jdbc:redshift://<amazon_redshift_host>:<port_number>/<database_name>
Cluster Region
The AWS cluster region in which the bucket you want to access resides.
Select a cluster region if you choose to provide a custom JDBC URL that does not contain a cluster region name in the
JDBC URL
connection property.
If you select a cluster region in both
Cluster Region
and
JDBC URL
connection properties, the agent ignores the cluster region that you specify in the
JDBC URL
connection property.
To use the cluster region name that you specify in the
JDBC URL
connection property, select
None
as the cluster region in this property.
You can only read data from or write data to the cluster regions supported by AWS SDK.
Select one of the following cluster regions:

    None

    Asia Pacific(Mumbai)

    Asia Pacific(Seoul)

    Asia Pacific(Singapore)

    Asia Pacific(Sydney)

    Asia Pacific(Tokyo)

    Asia Pacific(Hong Kong)

    AWS GovCloud (US)

    AWS GovCloud (US-East)

    Canada(Central)

    China(Bejing)

    China(Ningxia)

    EU(Ireland)

    EU(Frankfurt)

    EU(Paris)

    EU(Stockholm)

    South America(Sao Paulo)

    Middle East(Bahrain)

    US East(N. Virginia)

    US East(Ohio)

    US West(N. California)

    US West(Oregon)

Default is
None
.
Customer Master Key ID
The customer master key ID generated by AWS Key Management Service (AWS KMS) or the ARN of your custom key for cross-account access.
You must generate the customer master key ID for the same region where your Amazon S3 staging bucket resides. You can either enter the customer-generated customer master key ID or the default customer master key ID.
You can use a cross account KMS key for the same regions when you run mappings in advanced mode.
Doesn't apply to application ingestion and database ingestion tasks.
1
Doesn't apply to mappings in advanced mode.

0 COMMENTS

We’d like to hear from you!