QuickSight Connection Time-Out Error to RDS with a MYSQL DataBase Engine

Question & Answer
, ,
1

Hello, I am trying to set up a QuickSight visualization with a connection to an RDS database instance, where the engine is MYSQL. I am following this tutorial: Visualize data in Amazon RDS for SQL Server using Amazon QuickSight.

I followed all instruction with two modifications:

  1. The database engine is MYSQL, not Microsoft SQL Server.
  2. I connected my database instance to a Microsoft Azure Data Studio client, not Microsoft SQL Server.

The problem arises when I try to connect a new RDS datasource to QuickSight. This error occurs: “DATA_SOURCE_TIMEOUT”, “Connection to the data source time out before validation is complete.” This occurs even after verifying that I have the latest version of MYSQL engine available on RDS (8.0.39). I’ve also verified that QuickSight and RDS instance are in the same region.

When I checked the logs for my database instance, there were mysql-error-running.log and mysql-error.log files; however, they were empty to my surprise when I opened them.

Has anyone else encountered this issue? Any advice would be greatly appreciated. Many thanks.

2

Hi, have you configured the security groups allowing traffic from the correct ports between Quicksight and RDS? You can try testing with a bit more open permissions in your test environment and narrow it down from there

3

Hello @rajatdg,

Thanks for your feedback. Yes, I set up this security group that I called QS SecGP-2. Port 3306 was the one that I saw recommended for MYSQL.

image
image2308Ă—786 94.9 KB
This is the DNS Resolver Security Group that I set for my VPC connection in QuickSight in the setting Manage QuickSight Connections.

My RDS instance is also assigned to port 3306 and is attached to a VPC Security Group (RDS SecGP-2) with an outbound rule allowing all traffic.

What are the specific settings in my security groups that you’d recommend I open to try to narrow in on the problem?

Thanks again.

1 Like
4

Hi @Jeremy_Schwartzbord,
It’s been awhile since last communication took place on this thread; did you have any additional questions or were you able to find a work around for your case?

If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.

Thank you!

5

Hi Bret, thanks for your message. I didn’t find a workaround. I also didn’t receive other comments from my last response on the thread. I guess my question to the community will stay unresolved?

Best, Jeremy

6

Hi @Jeremy_Schwartzbord,
While I have not encountered this personally, timeout almost always means a network issue so I do believe it has something to do with security groups and/or VPC. It’s a bit hard to tell where the issue is occurring without being able to troubleshoot.

The best option for additional assistance in your case may be to create a support ticket so that you can get more in depth support for your case.

I’ll include some additional documentation for setting up VPC’s to use with QuickSight in case you haven’t reviewed!

1 Like
7

Hi @Jeremy_Schwartzbord,
Were you able to create a support ticket for your case? If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.

Thank you!

8

Hi @Jeremy_Schwartzbord,
I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community.

Thank you!