When I try to create an RDS data source my connection validation times out. Do you have any idea how to troubleshoot what I have missed?
My connection is on a VPC, it auto-populates fine. All I have to manually fill in is DB, un and PW and I have used these to connect to the database on my machine so I am sure they all work.
I get this error:
|sourceErrorCode:|DATA_SOURCE_TIMEOUT|
|sourceErrorMessage:|Connection to the data source timed out before validation is complete.|
Hi @gaynorg !
You get this error when Quicksight cannot connect to the RDS datasource. There are a couple reasons that this could happen.
If it’s a Postgres version 14 or higher, see here.
To set up the connection with a private VPC see here . A common error with this setup is to NOT have both Security Groups in the VPC connection. You need both security groups.
If you still cannot connect after working through these docs, I would recommend filing a case with AWS Support where we can dive into the details to help you further. Here are the steps to open a support case.
Hope that helps.
ws
Hello @gaynorg, I am going to mark @wstevens01’s response as the solution. If this problem persists after completing his recommendations and speaking with AWS Support, please post a new topic in the community and link back to this question. That will ensure you are at the top of the priority list for a response from one of our QuickSight experts. If you are able to get the connection establish, let us know and if you had to complete any additional steps in the process. Thank you!
what do you mean both security groups ?
not working right now 
still getting the same error
Hello @gaynorg, by both Security groups, I believe @wstevens01 is referencing a security group for the VPC and a security group for the RDS data source to allow traffic between both. Then you should be able to establish the QuickSight connection. This link that he posted is really helpful with the process:
I added the security groups to both sides for some reason one of the guides I read only mentioned adding it to 1 or I misread it anyway. The security groups to both sides& changing the encryption to MD5 was the solution everything is working now
Hello @gaynorg, glad you got it working! Thanks for following up.