1 Answer
- Newest
- Most votes
- Most comments
1
Hello.
Is it possible that the problem is not caused by the security group but by the Aurora database engine as in the answer at the URL below?
If the security group allows all communication, it is possible that the configuration parameters on the Aurora side and the JDBC driver used by QuickSight are not compatible, causing the connection to fail.
https://community.amazonquicksight.com/t/my-quicksight-cannot-connect-to-rds-postgresql-db-via-vpc/4696/2
If you are using PostgreSQL 14 or later, the following answers may be helpful.
https://community.amazonquicksight.com/t/issues-in-connecting-aurora-postgres-14-in-private-subnet-to-quicksight/20501
Relevant content
- asked 6 months ago
- asked 2 years ago
- Accepted Answerasked 3 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
Hi, But I was able to connect to a RDS db which is publicly available. So, I don't think it's an issue with JDBC drivers.
If the settings are as you explained, all communications from within the same VPC should be able to connect, so you should be able to connect from QuickSight as well, but maybe you've set the wrong security group, etc.? By the way, is RDS public access still enabled? There may be no problem since QuickSight and RDS are connected in the same VPC, but if public access is enabled, please try disabling it once.
This was the exact issue we had. After disabling public access in the RDS it started to working. Thanks.