As of January, 2018 Funnel's Redshift exporter is deprecated as part of the introduction of the new Amazon S3 connector. The new connector supports a wider range of dimensions and metrics, and allows for more configurability in general. It does not, however, support passing the exported data on to Redshift.

The main reason for deprecating the Redshift import is security. In order for it to work, you needed to allow external connections to the Redshift database, as well as handing out usernames and passwords for it, which was not ideal for the majority of users.

If you are using the legacy Redshift export you do not have to make any changes at this point. We will keep supporting it as is until August 31, 2018. 

However, if you want to make any changes to your export you will need to make some adjustments.

Changing an existing Redshift export

Should you want to change the data in your export you will need to do two things.

1. Set up a dedicated import job within your AWS account

This gives you full control over the import process as well as enabling you to use a stricter security policy. Learn how to set up your own Redshift import in this article: AWS Lambda Function for Redshift import

2. Notify Funnel so we can stop the existing Redshift import job

If the existing import keeps running it will attempt to load data into Redshift and will create conflicts with your newly created import. Therefore, it's important to make sure to let us know so that we can stop it and prevent that from happening.

Should you have any questions about this at all, please don't hesitate to reach out to us at

Did this answer your question?