Amazon Athena

Name: Amazon Athena API
Brand: Amazon Athena
Availability: InStock

✓ Official Vendor SpecAnalyticsBusiness IntelligenceapiKey60 EndpointsREST

For Agents

Use the Amazon Athena API to run SQL queries on data in Amazon S3 on AWS, with 60 operations covering the full control-plane lifecycle.

Quickstart

Get started with Amazon Athena in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"run a SQL query against data in S3"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon Athena API.

Submit SQL queries against S3 data using the Glue Data Catalog or a federated data source

Track query execution status, scanned bytes, and cost per query

Create workgroups that enforce per-team result locations and cost controls

Save reusable named queries and parameterised prepared statements

GET STARTED

Start building with Amazon Athena API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Amazon Athena API for, with concrete tasks.

★ Ad-hoc analytics on an S3 data lake

Run interactive SQL against terabytes of Parquet, JSON, or CSV data sitting in Amazon S3 without provisioning a warehouse. Athena reads table metadata from the Glue Data Catalog, executes the query in a serverless engine, and writes results to a configured S3 location. Teams can be productive within an hour once the catalog is in place.

Submit the query 'SELECT region, SUM(amount) FROM sales WHERE year = 2026 GROUP BY region' through Athena's primary workgroup and return the query execution id.

Per-team query isolation with workgroups

Separate analyst, finance, and engineering query traffic by creating distinct workgroups, each with its own result S3 location, scanned-bytes limit, and CloudWatch metrics. Workgroup configuration enforces guardrails such as encryption requirements and per-query cost ceilings without relying on policy checks at the IAM layer alone. Setup takes minutes per workgroup.

Create a workgroup named 'analytics-prod' with a per-query data-scanned limit of 1 TB and a result S3 location of s3://athena-results/analytics-prod/.

Parameterised report generation

Define prepared statements for routine report queries — for example a tenant-scoped revenue report — so applications can execute the same template with different bound parameters without re-sending the SQL text. Combined with named queries, this gives analysts a small, governed library of canonical queries.

Create a prepared statement named 'tenant_revenue' under workgroup 'analytics-prod' with the SQL 'SELECT month, SUM(amount) FROM sales WHERE tenant_id = ? GROUP BY month'.

AI agent answering analytics questions through Jentic

A data agent can answer business questions on demand by searching for the Athena query intent through Jentic, loading the StartQueryExecution and GetQueryResults schemas, and executing them with scoped credentials. The agent reasons over the returned rows without ever holding raw AWS access keys. Multi-step query and result handling becomes a single agent intent.

Search Jentic for 'run a SQL query against data in S3', load StartQueryExecution and GetQueryResults schemas, and execute a query that returns last week's revenue by region.

Key Endpoints

60 endpoints — amazon athena is an interactive query service that runs standard sql against data stored in amazon s3 without provisioning infrastructure.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=AmazonAthena.StartQueryExecution

Start a SQL query execution

POST

/#X-Amz-Target=AmazonAthena.GetQueryResults

Retrieve results for a completed query

POST

/#X-Amz-Target=AmazonAthena.GetQueryExecution

Describe a query execution and its status

POST

/#X-Amz-Target=AmazonAthena.CreateWorkGroup

Create a workgroup with cost and access controls

POST

/#X-Amz-Target=AmazonAthena.CreateNamedQuery

Save a named query

POST

/#X-Amz-Target=AmazonAthena.CreatePreparedStatement

Create a parameterised prepared statement

POST

/#X-Amz-Target=AmazonAthena.StartQueryExecution

Start a SQL query execution

POST

/#X-Amz-Target=AmazonAthena.GetQueryResults

Retrieve results for a completed query

POST

/#X-Amz-Target=AmazonAthena.GetQueryExecution

Describe a query execution and its status

POST

/#X-Amz-Target=AmazonAthena.CreateWorkGroup

Create a workgroup with cost and access controls

POST

/#X-Amz-Target=AmazonAthena.CreateNamedQuery

Save a named query

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS IAM access keys for Amazon Athena are stored encrypted in the Jentic vault. Jentic signs each request with AWS SigV4 at execution time and returns only the API response — raw access keys never enter the agent's context.

Intent-based discovery

Agents express intents like 'run a SQL query against data in S3' and Jentic returns matching Amazon Athena operations along with their input schemas, so the agent picks the right call without browsing the AWS service reference.

Time to first call

Direct Amazon Athena integration: 2-5 days for IAM scoping, SigV4 wiring, retry logic, and pagination handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Redshift Data API

Redshift Data API runs SQL against Redshift clusters rather than S3 data lakes

Choose Redshift Data API when data already lives in Redshift; choose Athena for serverless querying of S3 data.

Complementary

EMR on EKS

EMR on EKS runs heavyweight Spark and Hive workloads alongside Athena's interactive queries

Use EMR on EKS for long-running batch jobs that exceed Athena's interactive query envelope.

Alternative

Kinesis Data Analytics

Kinesis Data Analytics runs SQL on streaming data rather than data at rest in S3

Choose Kinesis Data Analytics for continuous streaming SQL; choose Athena for ad-hoc SQL on data already landed in S3.

FAQs

Specific to using Amazon Athena API through Jentic.

What authentication does the Amazon Athena API use?

The Amazon Athena API uses AWS Signature Version 4 (HMAC) request signing with IAM-issued credentials, the same scheme as every AWS service API. Jentic's MAXsystem stores those AWS credentials encrypted in the vault, generates short-lived signed requests at execution time, and never passes raw access keys into the agent's context.

Can I run a sql query on data in my s3 bucket with the Amazon Athena API?

Yes — the Amazon Athena API exposes 60 operations including the actions needed for that scenario. Use the operations listed in the key endpoints section as the starting point, then chain calls as needed for your workflow.

What are the rate limits for the Amazon Athena API?

AWS applies per-account, per-region request rate limits to the Amazon Athena control plane. Specific limits are not encoded in the OpenAPI spec; consult the AWS service quotas console for the Amazon Athena entry, and design retries with exponential backoff to absorb throttling responses.

How do I run a SQL query against data in S3 through Jentic?

Run pip install jentic, then call client.search('run a SQL query against data in S3') to discover the Amazon Athena operations that match. Load the schema for the chosen operation with client.load(...) and execute it with client.execute(...). Jentic handles AWS request signing automatically against the credentials stored in your Jentic vault.

Is the Amazon Athena API free to call?

AWS does not charge for control-plane API calls themselves on most Amazon Athena operations, but the underlying resources you create or operate (fleets, queries, deployments, and so on) incur usage charges according to the Amazon Athena pricing page. Refer to the AWS pricing page for the service to estimate cost.

Which operations should an agent call first when working with the Amazon Athena API?

For most workflows, agents should start by listing existing resources to understand the current state, then call the create or update operation that matches the intent. The endpoints listed under Key Endpoints in the catalog give a ranked starting set.