- 新しい順
- 投票が多い順
- コメントが多い順
Hi Ziad, Originally it didn't have that permission since it is policy for the redshift serverless and not the redshift. It does have the "redshift-serverless:GetCredentials" though.
However I did an experiment and added the permission it was complaining about. With no surprise the error changed after that saying that there is no cluster endpoint which is correct and there is no cluster because redshift serverless doesn't have one but uses the workgroup instead. By the looks of it the ODBC driver inherently tries to connect to the cluster based environment and not the serverless one. I am looking for the advice on how does one connect PowerBI with Redshift Serverless using the AWS profile config
Hi Denys,
Does the assumed role contain a policy with the GetCredentials permission on the Serverless endpoint?
Thanks,
Ziad
Hi Denys,
If you ensure your ODBC driver is the latest available (2.0.0.9 currently available here), connection via AWS Profile will work. Older ODBC driver versions may face issues.
Thank you @Sean Beath and @Ziad - it was a great turn around so big shout out to all involved!
Hi again Denys,
Thank you for all these details. I fully got what you are trying to do. Have you tried to keep the cluster ID, region, ... fields empty (these are normally optional) and just stick with the server/host field?
Thanks
Yep, I haven't been using those at all
I generated the same use case and yes as you mentioned it seems that the ODBC AWS profile authentication is not yet supported for Redshift Serverless. I will raise this point. Thank you Denys.