Error setting up Redshift destination in Airbyte OSS deployed from helm chart

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

Error message ‘Could not connect with provided SSH configuration. Error: getSQLState(…) must not be null’ when setting up Redshift destination in Airbyte OSS. Warning in logs ‘Registered driver with driverClassName=com.amazon.redshift.jdbc.Driver was not found, trying direct instantiation.’


Question

Hi community!

I’m having a problem setting up Redshift as the destination in airbyte OSS deployed from the official helm chart. I want to transfer data from S3 to Redshift. When I manually create the Redshift destination, I see this error in the UI when clicking Set up destination
Could not connect with provided SSH configuration. Error: getSQLState(...) must not be null
I’m using no SSH tunnel (screenshot). However, when I look at the logs, I see this error
WARN main c.z.h.u.DriverDataSource(<init>):68 Registered driver with driverClassName=com.amazon.redshift.jdbc.Driver was not found, trying direct instantiation.
Wonder if I need to configure anything in particular in the values.yaml so the driver is installed

cc - <@U07C8CCC68Y> :pray:


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["redshift-destination", "airbyte-oss", "helm-chart", "ssh-configuration", "driver-installation"]
2

Ok, after some digging, I found that my redshift cluster didn’t have public access enabled, nor the security group allowed any external inbound traffic (only from another security group). This is now working :+1:

3

Similar to <Slack bug> reported about a month ago