1 Answer
- Newest
- Most votes
- Most comments
0
Is your boto3.client for the right region and account? Regio nwill be picked up from your environment or you can specify it to boto3.client('athena', region_name).
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 4 months ago
ya its the right region and account, tried stating the region name, still returning the same error :/
Out of curiosity I tried pretty much exactly what you're doing and it worked fine until I deliberately put a wrong schema name in the query, then I got your error. I'm stumped, I can't think of anything else that could be wrong.