Noting the many previous requests from other users, and assurance from AWS that something will happen: PostgreSQL 14+ support - please
…is there any update?
I think we would all expect QuickSight to support the same versions of Postgres as RDS does. If the product can’t be supported is it time to retire it?
I am sympathetic that maybe there are constraints due to the reported cuts & changes in teams at AWS this year, but this has been ‘on the roadmap’ for a long long time now.
How can partners recommend QuickSight when it doesn’t work out of the box with AWS’s own database services.
Hello @Richard_Moore, welcome to the QuickSight community!
I completely understand your frustration with this issue and I know this is a topic that has been brought up many times over the last few years. Since I know how important PostgreSQL support is for QuickSight users and the AWS roadmap is primarily driven by our customers, I have tagged this topic as a feature request.
Also, I know it isn’t a solution to the issue, but it may be worth reaching out to your AWS representative to inquire about migrating from PostgreSQL to RDS Postgres if utilizing QuickSight is business critical. Considering how long this has been on the roadmap, finding an alternative route to take advantage of QuickSight may be the best course of action. I’ll link some documentation below:
Hello @Richard_Moore, I wanted to check in and see if you had any follow-up questions on this topic. I understand there isn’t a direct solution, but let me know if I am able to assist you any further.
Otherwise, I can archive this topic, now that it is tagged as a feature request, for the support team. Thank you!
From what I can see the issue exists with Amazon RDS for PostgreSQL too. If I create a new RDS database instance, choose Postgres, using the default settings (version 16), it doesn’t work with QuickSight. You either have to choose a very old version (12 or 13), or manually create a SQL user with less secure (MD5) password security.
We have experienced the same thing with Aurora.
I personally have a workaround, but just wanted to note the frustrating experience that these two AWS services don’t work together out of the box. The proposed workarounds could encourage AWS customers to choose less secure defaults.
With that said, I don’t have anything else to add so feel free to archive this topic.
Hello @Richard_Moore, I completely understand and I appreciate you clarifying the issue even further. I also agree that compromising on security is never a recommended route and don’t want to encourage that as a work around. I’ll archive this for our support team, but you can also keep an eye on the What’s New tab of the community to stay informed on QuickSight updates. Thank you!