Cloud Data Integration Current Version
- Cloud Data Integration Current Version
- All Products
Name of the runtime environment where you want to run the tasks.
Specify a Secure Agent, Hosted Agent, or serverless runtime environment.
You cannot run application ingestion tasks and database ingestion tasks on a Hosted Agent or serverless runtime environment.
User name of the Amazon Redshift account.
Password for the Amazon Redshift account.
Access Key ID
Access key to access the Amazon S3 bucket. Provide the access key value based on the following authentication methods:
If you want to use the connection for an application ingestion or database ingestion task, you must use the basic authentication method to provide the access key value.
Secret Access Key
Secret access key to access the Amazon S3 bucket.
The secret key is associated with the access key and uniquely identifies the account. Provide the access key value based on the following authentication methods:
If you want to use the connection for an application ingestion or database ingestion task, you must provide the actual access secret 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 AWS resources.
You cannot use the temporary security credentials in streaming ingestion tasks.
For more information about how to obtain the ARN of the IAM role, see the AWS documentation.
Optional. Specify the external ID for a more secure access to the Amazon S3 bucket when the Amazon S3 bucket is in a different AWS account.
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.
By default, the Use EC2 Role to Assume Role check box is not selected.
Master Symmetric Key
Optional. Provide 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.
The URL of the Amazon Redshift V2 connection.
Enter the JDBC URL in the following format:
Optional. 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 URLconnection property.
If you specify a cluster region in both
JDBC URLconnection properties, the Secure Agent ignores the cluster region that you specify in the
JDBC URLconnection property.
To use the cluster region name that you specify in the
JDBC URLconnection property, select
Noneas the cluster region in this property.
Select one of the following cluster regions:
None. You can only read data from or write data to the cluster regions supported by AWS SDK used by the connector.
Customer Master Key ID
Optional. Specify the customer master key ID generated by AWS Key Management Service (AWS KMS) or the ARN of your custom key for cross-account access.
Cross-account access is not applicable to elastic mappings.
You must generate the customer master key ID for the same region where your Amazon S3 bucket resides. You can either specify the customer-generated customer master key ID or the default customer master key ID.
1Applies only to mappings.
The remaining properties are applicable for both mappings and