Data Integration Connections > Connection properties > Amazon Redshift connection properties
  

Amazon Redshift connection properties

When you set up an Amazon Redshift connection, you must configure the connection properties.
The following table describes the Amazon Redshift connection properties:
Connection property
Description
Runtime Environment
The name of the runtime environment where you want to run the tasks.
Username
User name of the Amazon Redshift account.
Password
Password for the Amazon Redshift account.
Schema
Amazon Redshift schema name.
Default is public.
AWS Access Key ID
Optional. Amazon S3 bucket access key ID.
To run tasks on Secure Agent installed on an EC2 system, you might leave the Access Key ID blank.
To run tasks on Secure Agent that is not installed on an EC2 system, you must provide the Access Key ID.
AWS Secret Access Key
Optional. Amazon S3 bucket secret access key ID.
To run tasks on Secure Agent installed on an EC2 system, you might leave the Secret Access Key blank.
To run tasks on Secure Agent that is not installed on an EC2 system, you must provide the Secret Access Key.
Master Symmetric Key
Optional. Amazon S3 encryption key.
Provide a 256-bit AES encryption key in the Base64 format.
Customer Master Key ID
Optional. Specify the customer master key ID or alias name generated by AWS Key Management Service (AWS KMS). You must generate the customer master key ID for the same region where Amazon S3 bucket reside. You can either specify the customer generated customer master key ID or the default customer master key ID.
JDBC URL
Amazon Redshift connection URL.
Number of bytes needed to support multibytes for varchar
Applicable to Create Target. Reads the Varchar precision of the source table and creates the target table with 1x/2x/3x/4x times of the source precision to successfully write multibyte characters in the target table.
Note: You cannot create a target table if the Varchar precision exceeds 65535 that is maximum allowed.
Note: When you test a connection, Secure Agent validates Redshift connection. Validation of AWS Access key and AWS Secret key requires the Amazon S3 bucket name present in the advanced source and target properties. Therefore, Secure Agent validates AWS Access key and AWS Secret key when a synchronization or mapping task is run.