Amazon Redshift (Tech Preview) connector

warning

This connector is in Technology Preview status. It should not be used in a production environment or with production data. For more information, see the Feature release stages page.

Amazon Redshift (Tech Preview) connector enables you to connect to an Amazon Redshift database cluster setup via Amazon Redshift JDBC driver. Its flexible design allows smooth transfer of huge volume of data objects from/to the Amazon Redshift cluster. Through this connector, you can use a process to Insert, Update, Upsert, Unload, and Delete the data objects.

Important

The Amazon Redshift (Tech Preview) connector is only supported on basic runtime or runtime cluster.

note

• This is an open source connector and you can access the code in the Amazon Redshift connector repository.

Amazon Simple Storage Service (S3) and Data Encryption

The connector leverages the Amazon Simple Storage Service (S3) during the Insert and Upsert operation for temporary storage and retrieval of huge volume of data objects. The connector also offers the ability to utilize Amazon S3 data encryption options for protecting the sensitive data stored on disks in the Amazon S3 data centers. Depending on your choice, you can opt any one of the available encryption options listed below:Enter additional information for the connector.

• Server-Side Encryption with Amazon S3-Managed Keys (SSE-S3) – Each object is encrypted with a unique key. The key is then encrypted with a master key that it regularly rotates. This method uses 256-bit Advanced Encryption Standard (AES-256).
• Server-Side Encryption with AWS Key Management Service managed keys (SSE-KMS) – It is similar to the SSE-S3 encryption but offers additional data protection by using the Customer Master Keys (CMKs) to encrypt your Amazon S3 objects. CMKs can be created and managed using AWS Key Management Service (AWS KMS) - a key management system scaled for the cloud. AWS KMS encrypts only the object data and not the object’s metadata. For more information, see Protecting data using server-side encryption.
• Client-Side Encryption using a Client-Side Symmetric Master Key – In this option, you use a master key that is stored within your application for client-side data encryption. When you provide a client-side master key to the Amazon S3 encryption client, the S3 client uses the master key only to encrypt the data encryption key that it generates randomly. The S3 client uploads the encrypted data key and its material description as part of the object’s metadata. The S3 client uses the material description to determine which client-side master key to use for decryption. In this case, you manage the encryption process, the encryption keys, and related tools. For more information, see Protecting data using client-side encryption.

Connector configuration

To configure the connector to communicate with an Amazon Redshift cluster, set up the following two components:

• Amazon Redshift (Tech Preview) connection - Represents your Amazon Redshift cluster and/or AWS S3 login credentials.
• Amazon Redshift (Tech Preview) operation - Represents an action against a specific object i.e. Redshift data object. You will create one or more operations - one for each type of interaction required by your Integration scenario.

This design provides reusable components which contain connection and operation settings. After building the connection and operation, set up your connector within a process. When the process is defined properly, can map to and from virtually any system using the Amazon Redshift (Tech Preview) connector to transfer the data objects.

Supported editions

Amazon Redshift cluster version 1.0.12103 and above (integrated via Redshift JDBC Driver version 1.2.10.1009).

Prerequisites

To use the Amazon Redshift (Tech Preview) connector, you will require the following:

• Amazon Web Services (AWS) – Redshift cluster user account details like username and password.

• AWS access key which includes access key ID and secret key details for secured Amazon S3 connection. You can get the keys from the AWS Management Console (My Security Credentials page). If you don’t have an access key created already, create these keys in the AWS Management Console. For more information, see Understanding and getting your AWS credentials.

• Appropriate access rights to the Amazon S3 resource. You can verify your rights in Amazon S3 by selecting a bucket, folder, or file and clicking Properties > Permissions or by performing actions like creating or deleting a bucket, adding and uploading files, etc.

• Redshift JDBC driver version 1.2.10.1009 deployed to the appropriate basic runtime environment as a Custom Library Component. To do this,

  1. Download the Redshift JDBC driver JAR version 1.2.10.1009 from the Maven Repository.
  2. Upload the JAR file into to an account by using the Manage Account Libraries page (Settings - Account Libraries). For more information, see the topic Account library management.
  3. Create a Custom Library component that referenced that file and set the Custom Library Type to type Connector and the Connector Type to Redshift. Then, deploy the Custom Library to the appropriate basic runtime or runtime cluster environment(s).

  For more information, see the topic Working with custom libraries.

Tracked properties

This connector has no predefined tracked properties. See the topic Adding tracked fields to a connector operation to learn how to add a custom tracked field.