Redshift connection issue

Hi,

Since this morning we experiences connection issue between Looker Studio and Redshift with the following error message

Sorry, we encountered an error and were unable to complete your request.

Error ID: 35491014

The API call on https://lookerstudio.google.com/u/0/getAccountTree is in 403 with the response

{"reason":26,"errorStatus":{"reason":26,"code":7,"reasonStr":"JDBC_ACCESS_DENIED","errorCategoryStr":"ACCESS","category":1,"uniqueErrorCode":"35491014"},"params":{"errorId":"35491014"}}

On a dashboard we see this error

Unable to access table or database: FATAL: no pg_hba.conf entry for host "::ffff:142.251.74.0", 

Nothing change on our side between yesterday and today. We also already experience those errors randomly for one week now but now it's all the time.

Our redshift is publicly expose to the internet but with a security group that allow the IPs of your documentation https://support.google.com/looker-studio/answer/11377200#zippy=%2Cin-this-article

Thanks for your help

Arnaud.

 

Solved Solved
1 4 1,374
1 ACCEPTED SOLUTION

Hi, I received the error message and resolved the problem by re-uploading the AWS CA bundle to your Redshift connection in Looker Studio. Ensure SSL is enabled.

View solution in original post

4 REPLIES 4

Hi, 

I found other similar question with some suggestion.

https://www.googlecloudcommunity.com/gc/Looker-Studio/Unable-to-add-AWS-redshift-data-source/m-p/755...

Can you check connectivity of your Redshift instance? 

Hi,

I saw this post and yes the connectivity of my redshift instance is fine and I have others third party connect to it without any issues.

Like I said everything is working fine until next week, so it seems some permissions configuration that change ?

Hi, I received the error message and resolved the problem by re-uploading the AWS CA bundle to your Redshift connection in Looker Studio. Ensure SSL is enabled.

Hi, 

Thanks, I try to configure the connexion with SSL enable and now it works ! Strange because it used to work even without SSL