ACKF logoACKF
Analytics

Amazon Athena

View on GitHub

Amazon Athena

Amazon Athena is a serverless interactive query service that lets you run standard SQL to analyze data directly in Amazon S3. It operates as a pay-per-query, on-demand query layer without requiring you to provision or manage query infrastructure. Athena typically fits as the SQL query endpoint for data lakes and ad-hoc analytics in an AWS analytics architecture.

🗂 Resource Category

Analytics • Storage

🧠 Exam Memory Hook

Think: "Ad hoc SQL + serverless on S3 data = Amazon Athena"

📖 Ownership

Classification: AWS Managed Service

AWS responsibilities: AWS operates, scales, and patches the underlying service platform, including the control plane, query execution infrastructure, and the managed runtime that executes queries; AWS also manages underlying physical infrastructure, networking between service components, and service-level logging and metrics collection.

Customer responsibilities: The customer configures queries, schemas and metadata via the AWS Glue Data Catalog or Athena-managed catalog, defines S3 bucket layout and object formats, configures IAM policies, S3 bucket policies and encryption, monitors query performance and costs, optimises query design and partitioning, and implements data lifecycle and retention policies for data stored in S3.

Patching responsibilities: AWS patches and maintains the physical infrastructure, hypervisor, underlying operating systems, and the managed query runtime/platform used by Athena; the customer is responsible for patching and maintaining any client-side code, SQL query logic, user-defined functions or custom connectors they deploy, plus any libraries or dependencies included in those artifacts.

🏗 Typical Architecture

💡 Top 5 Features

  • Serverless SQL query execution without provisioning query clusters or instances.
  • Native support for querying data stored in Amazon S3 using standard ANSI SQL.
  • Integration with AWS Glue Data Catalog for table metadata and schema management.
  • Federated query capability to access data in external sources through connector Lambda functions.
  • Workgroups and query result configuration for separating queries, controlling output location, and managing cost visibility.

✅ Top 5 Use Cases

  • Ad-hoc and exploratory SQL analysis directly against a data lake stored in Amazon S3 without ETL into a separate warehouse.
  • Running scheduled or on-demand queries that transform or aggregate S3 data and write result sets back to S3 for downstream workflows.
  • Interactive log and event analysis where logs are kept in S3 and analysts run queries to troubleshoot or investigate events.
  • Business intelligence and dashboards where Athena serves as the query source for visualization tools like Amazon QuickSight.
  • Joining S3-resident datasets with external data sources using federated query connectors to combine data without data movement.

🏗 Architecture Placement

Amazon Athena sits as a regional, serverless SQL query layer in the analytics tier and is usually invoked by analysts, applications, or BI tools. It reads and writes data in Amazon S3 and relies on the AWS Glue Data Catalog for schema and table metadata when configured. Athena can also invoke or be integrated with federated connectors to query external data sources and emits metrics and query logs to Amazon CloudWatch. Access and result storage are controlled at the account and region level through IAM and S3 policies.

🎯 Commonly Used With

- Amazon S3
- AWS Glue
- Amazon QuickSight
- AWS Lake Formation
- Amazon CloudWatch

🌍 5 Real-World Examples

  • A financial investigations team runs ad-hoc SQL queries in Athena against transaction logs stored in S3 to trace suspicious activity without loading data into a separate warehouse.
  • A healthcare analytics team queries normalized, de-identified patient records stored in Parquet on S3 to produce research datasets for downstream analysis.
  • An online retailer uses Athena to analyse clickstream and sales event files in S3 to generate daily reports that feed back into pricing and inventory processes.
  • A media company runs Athena queries on large compressed log files in S3 to troubleshoot streaming delivery issues and identify problematic content sources.
  • A government geospatial program queries processed telemetry and sensor data in S3 to produce aggregated datasets for mapping and analysis workflows.

🎓 AWS Exam Clues

  • Serverless SQL for querying data stored in Amazon S3 without managing query clusters or servers.
  • Use when you need ad-hoc or interactive analysis on S3-resident datasets and want pay-per-query billing.
  • Consider AWS Glue Data Catalog and proper partitioning/columnar formats to optimise performance and cost.
  • Federated Query enables combining S3 data with external sources via connectors, reducing the need for ETL.
  • Workgroups, result configuration, and IAM/S3 policies are key for cost control, access isolation, and result storage governance.

📝 Quick Revision

Amazon Athena is a serverless interactive SQL query service that runs queries directly against data in Amazon S3, using the AWS Glue Data Catalog for metadata when configured. Use it for ad-hoc analytics and BI without provisioning infrastructure, but plan data formats, partitioning, IAM/S3 policies, and query cost controls for production use.

🏷 Keywords

Serverless SQL • S3 data lake • AWS Glue Data Catalog • Federated Query • Query results to S3 • Workgroups • Partitioning • Columnar formats • CTAS • JDBC/ODBC • Query optimization • Pay-per-query