Howdi - i hope someone can guide me here -
i am trying to implement the AWS provided amazon connect datalake and generate some reports in quicksights to see how this works. how ever i am unable to see any columns in the Athena data source when adding to quicksight as a dataset and it fails. what am i missing
i have gone through the initial setup - and i can query the linked resource tables from Athena ok eg “contact_record” . so then i have i tried adding this table as an Athena datasource in quicksights .i can see the database and table but it says no columns available when i try to preview the table. i feel there is a missing step , can i add the linked table directly to athena or do i need another step before this or how is this is done usually.
This shows that you are creating new table in Athena but column not created. You need to create a source in Athena let assume you are using S3. or if you are using the Glue services and you can use Catalogue. It will create a database, table and columns then you can use the it with Quicksight.
For Quicksight connection you can follow this documentation.
Also i can query the data fine when using the athena console
to note this is an amazon connect datalake which is provided by AWS automatically and shared from a managed aws account and shared to the consumer account via lake formation
as per this post
@andres007 Thanks yes i understand the only reason i am going to custom query is because its failing to add the athen data source if i try what you suggested i get this error - as mentioned previously if i query directly from athena console i can see the data
Mmhh, looks like a permissions issue, did you add the S3 bucket to the QuickSight permissions? I never connected Amazon Connect to QuickSight so i do not know the steps, but i found a blog that might be useful for you.
Please take a look and let us know if/what solves your access issues.
Ok, never tried that, but if lakeformation is involved then you need to give your quicksight user permission to access the data, since the user for the console is not the same as the one for QuickSight.
Here is a link to the documentation and inside a couple of blogs on how to provide access to lakeformation managed resources to QuickSight users.
@andres007 Thank you for your assistance . Yes it was a permission issue . in lake formation i have added “GRANT on target” LIST permission to the resource link table “connect_ctr” and adding the quicksight user ARN as the IAMprinciple
