Connection Refused to Specific Redshift

We have an AWS Redshift instance that is been used with Looker Studio for a while, but a few weeks ago the connection stop to work and we are getting this error:

We noticed that other Redshift instance keep working as usual but this one not. Any thoughts about what can be done? Tnx

3 Likes

Solved by using “jdbc:postgresql://” instead of “jdbc:redshift://” on the connection url. Really strange because we have another redshift instance that works fine with “jdbc:redshift://”. :thinking:

2 Likes

Are you using redshift’s or PG’s jdbc? Redshift’s supports both prefixes while PG’s only supports PG prefix.

3 Likes