Not supporting custom SQL in Direct Query dataset with IAM Identity Center

Question & Answer
,
1

QuickSight does not support custom SQL in a Direct Query dataset when authenticating with SSO (IAM Identity Center).
Only adding the table from IdC-enabled Redshift into a Direct Query dataset works.
Will QuickSight support custom SQL for an SSO-authenticated dataset later?
Is there any reason or a hard blocker from QuickSight to not support custom SQL?

2

Hello @hoyeon !

I have never run into this issue while using Custom SQL. Could you share more about your set up or show the error or blocker you are getting from QuickSight when trying to use custom sql?

I can also mark this as a feature request for the QuickSight team.

3

If you do not authenticate with IAM Identity Center, Custom SQL works. QuickSight with AWS IAM Identity Center, Custom SQL button does not appear on the dataset page.

4

Any update for this question?

5

Hi @hoyeon ,

Modifying my response (My initial response was to create a support ticket as I hadn’t noticed that this issue was being hit with Redshift connection in trusted identity propagation mode. Thanks to Hoyeon for pointing that out.)

Custom SQL isn’t supported currently with Redshift connections in trusted identity propagation mode.
This is called out in documentation - Authorizing connections from Amazon QuickSight to Amazon Redshift clusters - Amazon QuickSight

Trusted identity propagation is not currently supported for the following features.

SPICE datasets
Custom SQL on data sources
Alerts
Email reports
Amazon QuickSight Q
CSV, Excel, and PDF exports
Anomaly detection

I’m checking with product team on whether there are any plans to add custom SQL support in near future. Will provide an update once I hear back. If not, we will file a PFR for same.

Regards,
Arun Santhosh
Pr QuickSight SA