All Services

Analytics

Amazon Athena

Amazon Athena runs serverless SQL over data in S3 and supported federated sources using the AWS Glue Data Catalog, workgroups, open table formats, and optional provisioned capacity reservations.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon Athena.

Amazon Athena pricing and cost programs

Pricing model: Query and provisioned-capacity usage

On-Demand
Available
Reserved Instances or reserved capacity
Not applicable
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: Data scanned · DPU hours · Spark compute · Federated-query services

Programs and modes: SQL queries · Provisioned Capacity · Apache Spark

Workgroup configuration, data format, compression, and capacity mode affect charges.

Free Tier: Service-specific — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement Amazon Athena?

  • Queries data in place without provisioning warehouse servers or loading every dataset into a database first.
  • Works with the Glue Data Catalog, Lake Formation, common columnar formats, partitioned datasets, federated connectors, and supported transactional table formats.
  • Provides workgroup isolation and controls, per-query usage billing or capacity reservations, query history, result reuse options, and CloudWatch metrics.

How to implement Amazon Athena

  1. Place governed data in S3 using compressed columnar formats and intentional partitioning, file sizes, prefixes, schemas, retention, encryption, and lifecycle rules.
  2. Create Glue Catalog databases and tables through explicit definitions, crawlers, or table-format tooling; configure Lake Formation or IAM access to catalog, source data, KMS keys, and query results.
  3. Create workgroups with result locations, encryption, scan limits or capacity assignments, publish parameterized queries or applications, and monitor bytes scanned, queue time, failures, costs, and data-quality expectations.

Amazon Athena best practices

  • Use Parquet or ORC, compression, partition pruning, compact reasonably sized files, project only required columns, and avoid unnecessary scans, joins, or repeated transformation of raw text data.
  • Separate workloads with workgroups and accounts where appropriate, enforce result and usage settings, use capacity reservations for isolation when justified, and alarm on quota pressure or unexpected scanned bytes.
  • Apply least privilege through Lake Formation or IAM, encrypt source and result data, prevent untrusted SQL construction, validate federated connectors, expire query results appropriately, and keep catalog schemas synchronized with data.

Amazon Athena use cases and server impact

  • Ad hoc SQL over S3 data lakes
  • Log, security, and cost-data investigation
  • Federated and open-table-format analytics

Replaces SQL query-cluster infrastructure for intermittent lake analytics, but data layout, catalog accuracy, access policy, query efficiency, and source-system limits still determine reliability and cost.

Official implementation resources

Commonly paired AWS services

Planning guides that use Amazon Athena