This section provides information on how to enable Redshift connectivity and create one or more connections to Redshift sources.
Before you begin, please verify that your meets the following requirements:
NOTE: In the Admin Settings page are some deprecated parameters pertaining to Redshift. Please ignore these parameters and their settings. They do not apply to this release.
When Redshift jobs are run, the UNLOAD SQL command in Redshift converts all nulls to empty strings. Null values appear as empty strings in generated results, which can be confusing. This is a known issue with Redshift.
You can create Redshift connections through the following methods.
Tip: SSL connections are recommended. Details are below.
Any user can create a Redshift connection through the application.
Specify the properties for your Redshift database connection. The following parameters are specific to Redshift connections:
|IAM Role ARN for Redshift-S3 Connectivity|
(Optional) You can specify an IAM role ARN that enables role-based connectivity between Redshift and the S3 bucket that is used as intermediate storage during Redshift bulk COPY/UNLOAD operations. Example:
For more information, see Create Connection Window.
To enable SSL connections to Redshift, you must enable them first on your Redshift cluster. For more information, see https://docs.aws.amazon.com/redshift/latest/mgmt/connecting-ssl-support.html.
In your connection to Redshift, please add the following string to your Connect String Options:
Save your changes.
Import a dataset from Redshift. Add it to a flow, and specify a publishing action. Run a job.
NOTE: When publishing to Redshift through the Publishing dialog, output must be in Avro or JSON format. This limitation does not apply to direct writing to Redshift.
For more information, see Verify Operations.
After you have run your job, you can publish the results to Redshift through the Job Details page. See Publishing Dialog.