First of all, I know there have been multiple topics around this issue before, I listed them at the bottom of this post (could only list 2 since I’m new here but there are many more). However, I wanted to create a new one in order to stress the importance of this issue and how it is imho blocking many to consider Quicksight as a valuable option.
Quicksight has data source options for Aurora (PostgreSQL), RDS (PostgreSQL) & bare PostgreSQL, however, currently it only supports soon to be EOL version 12 or already EOL versions <12.
Recent versions 13, 14, 15 and 16 are not at all supported by Quicksight out of the box, the reason being that Quicksight uses an outdated Postgres JDBC driver which doesn’t support the new password encryption method scram-sha-256. This scram-sha-256 password encryption method has been in Postgres since version 10 and has become the default since version 13.
The other topics below mention work-arounds (not solutions) for the problem by changing the default password encryption setting back to ‘md5’. Which to me, sounds ridiculous. MD5 is an outdated approach of encrypting/hashing passwords and no longer up to par with current standards. Also, I would expect an AWS product like Quicksight to support other managed AWS services out of the box without the need to fiddle around with config settings + I would also expect it to work with up-to-date dependencies for security reasons. Especially since the JDBC driver used by Quicksight is 7 years old and has known security vulnerabilities.
Can someone here possibly escalate this up the chain until it reaches someone who has the ability to start addressing this issue?
Thanks!
Other reports of the same issue (there are more but I can only add 2 links to my post since I’m new here):
https://community.amazonquicksight.com/t/my-quicksight-cannot-connect-to-rds-postgresql-db-via-vpc/4696
https://community.amazonquicksight.com/t/aurora-postgresql-serverless-v2-supported-versions/18133