-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Unrecognized client exception when calling the GetTableMetadata operation: The security token included in the request is invalid. #46
Comments
Are you sure you have access to that particular database and table in Athena with your user account? |
Hi! With this user account I am able to use AWS glue and set up a crawler to create tables from the oedi data lake, then run queries in Athena. I'm assuming this means I have access? |
You should be able to go to Athena console and see those specific db and table name. If you can't, then you will need to first create those. Please follow the instructions here: https://www.youtube.com/watch?v=qSR1MFpSiro&t=0s |
Thanks for the screenshot. That's very helpful. It seems like somehow the credentials being pulled is not granting you the required permission.
|
Issue overview
When attempting to use the buildstock-query notebooks, I'm getting a Client / Operational Error.
Current Behavior
Expected Behavior
Steps to Reproduce
from buildstock_query import BuildStockQuery
(works fine)
2.
aws configuration
(enter keys, region, etc.)
Account has:
my_run = BuildStockQuery(workgroup='rescore', db_name='euss-final', table_name='euss_res_final_2018_550k_20220901')
This and various other table names and working groups produce Client / Operational errors:
OperationalError: An error occurred (UnrecognizedClientException) when calling the GetTableMetadata operation: The security token included in the request is invalid.
Possible Solution
Details
Environment
Some additional details about your environment for this issue (if relevant):
Context
We're able to query and access the Data Lake via AWS Athena interface, but would also like to use the python querying tools to more easily interface with our analysis of residential data.
The text was updated successfully, but these errors were encountered: