-
Notifications
You must be signed in to change notification settings - Fork 670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading an iceberg table in a vpc fails with connection time out on endpoint URL: "https://sts.amazonaws.com/" #2760
Comments
Hi @AdrianoNicolucci , does it succeed with a vanilla boto3 call and not with aws sdk for pandas? is athena endpoint also set? |
@kukushking After testing it with a table that is just a csv table instead, I'm still getting the same issue of the lambda function timing out since it can't connect to athena. So perhaps it has nothing to do with the iceberg table specifically. However, When I attempt to query directly with boto3, I can see the query reach the athena service which tells me there is an issue somewhere with this method. |
After reviewing the logs and doing some further debugging, it looks like the error message
Here are the global endpoint configurations I have tried to set to force it to use the region endpoints but with no luck:
|
Describe the bug
Description of problem
I have a lambda function within a VPC that calls the method df =
wr.athena.read_sql_query
. I get the error message Connect timeout on endpoint URL: "https://sts.amazonaws.com/". I have configured vpc endpoints for my subnet that the lambda function runs in for athena, s3, glue and even sts. When I run the same function outside the VPC there is no problems.I have even tried set the sts endpoint in my code with
wr.config.sts_endpoint_url = 'https://sts.us-east-2.amazonaws.com' "
Error message
The text was updated successfully, but these errors were encountered: