This property doesn't apply to Amazon Redshift AssumeRole authentication with EC2 role.

This property doesn't apply to Amazon Redshift AssumeRole authentication with EC2 role.

The name of the database group to which you want to add the database user when you select the

Auto Create DBUser

option in this connection property.

The user that you add to this database group inherits the specified group privileges.

If you do not specify a database group name, the user is added to the public group and inherits its associated privileges.

You can also enter multiple database groups, separated by a comma, to add the user to each of the specified database groups.

The time duration that the password for the Amazon Redshift database user expires.

Specify a value between 900 seconds and 3600 seconds.

Default is 900.

Select to create a new Amazon Redshift database user at run time.

The agent adds the user you specified in the

Username

field to the database group. The added user assumes the privileges assigned to the database group.

Default is disabled.

Enter the access key ID when you use the following methods for S3 staging:

When the IAM user has access to S3 staging.
When the IAM user who assumes the S3 IAM role uses the temporary security credentials to access S3.

You do not need to enter the S3 access key ID if you use IAM authentication or the assume role for EC2 to access S3.

The secret key is associated with the access key and uniquely identifies the account.

Enter the secret access key value when you use following methods for S3 staging:

When the IAM user has access to S3 staging.
When the IAM user who assumes the S3 IAM role uses the temporary security credentials to access S3.

You do not need to enter the S3 secret access key if you use IAM authentication or the assume role for EC2 to access S3.

You can use a VPC endpoint to enable private communication with Amazon S3.

Select one of the following options:

Replace the asterisk symbol with the

bucket

keyword in the DNS name.

Enter the DNS name in the following format:

bucket.<DNS name of the interface endpoint>

For example,

bucket.vpce-s3.us-west-2.vpce.amazonaws.com

The external ID associated with the IAM role.

You can specify the external ID if you want to provide a more secure access to the Amazon S3 bucket when the Amazon S3 staging bucket is in same or different AWS accounts.

If required, you also have the option to specify the external ID in the AssumeRole request to the AWS Security Token Service (STS) using an external ID condition in the assumed IAM role's trust policy.

For more information about using an external ID, see External ID when granting access to your AWS resources.

This property doesn't apply to application ingestion and database ingestion tasks.

The AWS geographical region in which the Redshift cluster resides.

Select the cluster region from the list if you choose to provide a custom JDBC URL with a different cluster region from that specified in the

JDBC URL

field property. To continue to use the cluster region name specified in the

JDBC URL

field 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 the 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

.

For more information, see Enable encryption.

This property doesn't apply to application ingestion and database ingestion tasks.

The customer master key ID generated by AWS Key Management Service (AWS KMS) or the ARN of your custom key for cross-account access when you stage data in Amazon S3. The customer master key serves to encrypt your data at the destination before they are saved in Amazon S3.

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 in a connection in a mapping in advanced mode. The cluster and the staging bucket needs to be in the same region.

For more information about how to configure server-side encryption, see Enable encryption.

This property doesn't apply to application ingestion and database ingestion tasks.