Amazon Redshift Connection

Connection Requirements

Before you create an Amazon Redshift connection, ensure that the Redshift cluster that you’re connecting to is SSL enabled. For more information about using SSL, see Configure Security Options for Connections in Amazon Web Services documentation.

Note SHA256 encryption isn't supported for the certificate bundle. You must use MD5 encryption.

Create the Connection

1. On the Data Manager Connections tab, click New Connection.
2. Click the name of the connector, and click Next.
3. Enter the connector settings.
4. To validate your settings and attempt to connect to the source, click Save & Test. If the connection fails, CRM Analytics shows possible reasons.

All settings require a value, unless otherwise indicated.

jdbc:redshift://examplecluster.cke7ebis04kb.us-west-2.redshift.amazonaws.com:5631/dev

jdbc:redshift:User=admin;Password=admin;Server=default.xxxxxxxxxx.us-east.2.redshift-serverless.amazonaws.com;Port=5439;Database=dev;

Filter Data Synced to CRM Analytics

Exclude unnecessary or sensitive data from syncing to CRM Analytics with data sync filters. Filters run on the source object and speed up data sync by pulling only the data you need into CRM Analytics.

Note If you expect to use excluded data in the future, use a recipe filter to limit the data written to a dataset instead of a data sync filter.

1. From Data Manager, click the Connections tab.
2. Select the connection associated with the object to filter.
3. Click the name of the object to filter.
4. Click Data Sync Filter.
5. Enter the filter.
6. Click Save.

For the Amazon Redshift connector, enter a filter in the syntax described in the Amazon Redshift help.

Amazon Redshift Connector Considerations

Keep these behaviors in mind when working with the Amazon Redshift connector.

• Connected object names must start with a letter and contain only letters, digits, or underscores. Object names can’t end with an underscore.
• Only field names with combinations of alphanumeric, dot, underscore, or dash characters are supported. If a connector includes field names that contain other characters, such as spaces or brackets, the sync fails.
• The connector can sync up to 100 million rows or 50 GB per object, whichever limit is reached first. When using the connector, Salesforce Government Cloud org data is protected in transit with advanced encryption and can sync up to 10 million rows or 5 GB for each connected object, whichever limit is reached first.
• Ensure that the Redshift cluster that you’re connecting to is SSL enabled. For more information about using SSL, see Configure Security Options for Connections in Amazon Web Services documentation.
• While connecting to a Redshift view, the field picker appears empty when a field’s length exceeds 32,000 characters and the source data table and view are in different database schemas. Decrease the field length in Redshift, or move the table and view to the same schema.
• When syncing a Redshift object, the job quits when the query takes longer than the 60-minute threshold or when Redshift can't send any data within a 20-minute window. Make sure the Redshift instance is sized properly to send data in the 20-minute window.
• Although allowing designated IPs isn’t usually the preferred or recommended practice in most cases, you must make your Redshift node available to Salesforce data centers with these IP ranges. Nodes in a VPC or behind a firewall aren’t supported.