I am new to quicksight and trying to to setup Athena resource in quick sight. I have a S3 bucket which contains some data that a lambda function needs to access.
Under “Allow Access and auto discovery for these resource”, I uncheck and check Amazon Athena, that takes me to setting page.
I can see the bucket I want to use, but when I switch to Lambda it says
“No Lambda Function Available”.
I can see that the lambda function is indeed available in US-EAST-1 region.
So I thought I must switch regions.
When I switch region from london to US-EAST-1, and browse to “Security & Permission” I see a message asking me to switch to London Region. So I am stuck in a chicken & egg situation.
Can someone please help me, to understand what I am doing wrong?
@sadiqkhan You will see lambda that is configured as a connector/ data source in Athena to access data from sources other than S3 (Athena Federated Query). Can you please confirm if you have the lambda configured in Athena? For more information, please visit this link: Using Amazon Athena Federated Query - Amazon Athena
To access data from S3 bucket, you can directly provide access to the S3 bucket.
Hi, @sadiqkhan. Welcome to the QuickSight Community! We hope Vetri’s solution worked for you. Let us know if this is resolved. (And if it is, we’d love it if you could click/tap “Solution" under his answer.) Thanks!
Hi @n_vetri , yes I have a lambda configured in athena. I guess the issue is something to do with how regions work with quick sight.
I can only access S3 and Lambda function that are in EU-WEST-2 (London) region, any bucket or lambda outside this region does not show up on quick sight.
Hi @sadiqkhan,
Essentially, you should be able to see all the buckets irrespective of the region. I think the best option is to open a support case with details so that one of our Engineer can look into this issue and help you resolve.
Hi, @sadiqkhan. In case you need them, here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able
We hope Vetri’s solution worked for you. Let us know if this is resolved. (And if it is, we’d love it if you could click/tap “Solution" under his answer.) Thanks!