> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/data-sources/databases/amazon-athena-aws-athena.md).
# Amazon Athena (AWS Athena)
Amazon Athena is an interactive query service that makes it easy to analyze data directly in Amazon Simple Storage Service (Amazon S3) using standard SQL.
Before connecting AWS Athena with Jet Admin, you need to have the following credential information:
* Host
* Port
* AWS access key
* AWS secret key
* Database name
* S3 staging dir
## Connect AWS Athena to Jetadmin
1. Click `Add Resource` from the data section on the left-side menu
2. Choose AWS Athena
3. Choose `Instant Connection` as a setup method
4. Type a unique resource name
5. Choose region which is closer to your location and has smaller delay
6. Fill in the Host, Port, AWS access key, AWS secret key, Database name, and S3 staging dir fields
7. Click `Choose Tables`
8. Choose the needed tables and click `Add Resource`
###
Use the fields in your own connection form; the screenshot contains empty inputs or example placeholders.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.jetadmin.io/user-guide/data-sources/databases/amazon-athena-aws-athena.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.