A for Athena

A for Amutha, A for Athena: My First AWS Deep Dive ☁️

Introduction

Cloud computing has changed the way students, developers and organizations store and analyze data. As the amount of data increases, simply storing data is not enough. We also need efficient ways to search, analyze and understand that data.

As part of my AWS learning journey, I explored Amazon Athena, an interactive and serverless query service provided by Amazon Web Services (AWS).

The fun part for me is the connection between my name and the service:

A for Amutha → A for Athena

Amazon Athena allows users to analyze data stored in Amazon S3 using standard SQL, without setting up or managing database servers. This makes it useful for students and developers who want to perform data analysis without maintaining complicated infrastructure.
What is Amazon Athena?

Amazon Athena is a serverless interactive query service that allows users to analyze data directly from Amazon S3 using SQL.

Unlike a traditional database where we may need to create and manage servers, Athena does not require us to provision or maintain servers for SQL queries.

A simple way to understand it is:

S3 stores the data → Athena reads the data → SQL analyzes the data → results are returned.

Athena can work with different data formats including CSV, JSON, Apache Parquet, ORC and Avro. It can also integrate with AWS Glue Data Catalog to maintain information about datasets and their schemas.

Why was Athena created?

Organizations often have large amounts of data stored in Amazon S3. Traditionally, analyzing that data could require additional infrastructure, data processing systems or databases.

Athena provides a simpler approach: instead of moving all the data into a separate database, users can query data where it already exists in S3.

This makes Athena particularly useful for ad-hoc analysis, log analysis, reporting and exploring large datasets**.

How Amazon Athena Works

The basic workflow can be understood in five steps:

1. Data is stored in Amazon S3.
2. A database and table schema are defined in Athena.
3. Athena identifies how the data is structured.
4. The user writes a SQL query.
5. Athena processes the data and returns the results.

Architecture / Flow Diagram

Place the following diagram here in your Dev.to article:

         ┌──────────────────────┐
         │      Amazon S3       │
         │                      │
         │ CSV / JSON / Parquet │
         └──────────┬───────────┘
                    │
                    ▼
         ┌──────────────────────┐
         │    Amazon Athena     │
         │                      │
         │   Serverless SQL     │
         │      Queries         │
         └──────────┬───────────┘
                    │
              SQL Processing
                    │
                    ▼
         ┌──────────────────────┐
         │    Query Results     │
         │                      │
         │ Console / S3 / BI    │
         └──────────────────────┘

Athena can also work with AWS Glue Data Catalog, which can store metadata about tables and datasets. Query results are written to an S3 location configured for Athena.

Key Features of Amazon Athena

1. Serverless Architecture

The biggest feature of Athena is that it is serverless.

There is no need to create, configure, patch or maintain query servers. AWS manages the underlying infrastructure, allowing developers to concentrate on writing queries and analyzing data.

1. Standard SQL Queries

Athena supports standard SQL, which means students who already know SQL can start analyzing datasets without learning an entirely new programming language.

For example:

SELECT department, COUNT(*) AS student_count
FROM students
GROUP BY department;

This query can count students in each department.

1. Multiple Data Formats

Athena can query several formats such as:

• CSV
• JSON
• Apache Parquet
• Apache ORC
• Avro

This makes it suitable for different types of datasets and data-lake environments.

1. Integration with AWS Glue

Athena integrates with the AWS Glue Data Catalog, which can act as a central metadata repository for datasets stored in S3.

This helps Athena understand the structure of the data before running queries.

1. Federated Queries

Athena can also query data from sources beyond S3 using data source connectors. This allows SQL-based analysis across multiple supported data sources.

🎓 College / Student Use Case

Imagine our college stores student activity data in Amazon S3.

The dataset could contain:

student_id,department,event,score
101,AIML,Hackathon,85
102,CSE,Workshop,92
103,AIML,Workshop,78
104,ECE,Hackathon,88

Instead of downloading the complete dataset and manually analyzing it, a student project could use Athena to directly query the data.

For example, we could find the average score for each department:

SELECT department,
       AVG(score) AS average_score
FROM student_events
GROUP BY department;

This could help a college analytics system understand participation and performance across departments.

A similar approach could be used for:

• Attendance analysis
• Workshop participation
• Hackathon statistics
• Placement data analysis
• Library usage
• Campus event analytics

💻 Practical Example

Suppose a college stores a file called:

student_events.csv

inside an S3 bucket.

After creating an Athena table for the dataset, we can execute:

SELECT event,
       COUNT(*) AS participants
FROM student_events
GROUP BY event
ORDER BY participants DESC;

Athena analyzes the data stored in S3 and returns the number of participants for each event.

The important point is that we do not need to move the entire dataset into a traditional database before performing the query.

Athena can query the data directly from S3.

---

🌍 Real-World Use Case

Amazon Athena can be used for large-scale analytics and log analysis.

For example, AWS describes organizations using Athena in analytics pipelines. One example is TNG FinTech Group, which uses Amazon Athena together with AWS Glue to perform serverless queries on financial transaction data. Athena helps its wallet service retrieve information about past transactions without requiring manual intervention.

Another use case is analyzing large datasets such as application logs, where teams can query data stored in S3 to investigate events and identify patterns. AWS specifically describes Athena as useful for analyzing logs and performing ad-hoc queries.

Advantages

No Server Management

Athena is serverless, so users don't have to maintain database servers or clusters.

Easy for SQL Users

Anyone familiar with SQL can start querying datasets without learning a complex infrastructure system.

Works Directly with S3

Data does not have to be moved into a separate database just to perform an ad-hoc query.

Automatic Scaling

Athena is designed to execute queries in parallel and scale according to workload.

AWS Integration

Athena works with services such as Amazon S3 and AWS Glue, and can integrate with other AWS and external data sources.
Limitations / Things to Consider

Cost

Athena is not simply "free because it is serverless." Pricing depends on the selected pricing model and, for SQL queries, can depend on the amount of data processed.

AWS also charges normal S3 costs for storage, requests and applicable data transfer. Query results stored in S3 can also incur S3 charges.

For example, AWS currently provides an example where scanning 3 TB of uncompressed data under its per-query pricing model results in a $15 query cost. The actual cost depends on the pricing model, region and workload.

For students, it is important to avoid repeatedly scanning unnecessarily large datasets.

Complexity

Although SQL itself is easy to understand, managing schemas, partitions, data formats and permissions becomes more complicated as a project grows.

Scalability

Athena is designed to scale automatically, but inefficient queries can still process large amounts of data. Using compression, partitioning and columnar formats such as Parquet can reduce the amount of data scanned and therefore improve efficiency and cost.

Security

Security still needs to be configured correctly. Access to Athena and the underlying S3 data can be controlled using IAM policies and S3 permissions. Athena also supports querying encrypted S3 data and writing encrypted results.

Security

A cloud analytics service should not only be fast; it must also protect data.

Amazon Athena uses AWS security mechanisms such as IAM policies to control access. The underlying data is usually stored in Amazon S3, so S3 permissions and encryption are also important.

AWS recommends using IAM policies to restrict access to Athena operations, while access to the underlying S3 dataset must also be appropriately controlled.

For a college project, this means sensitive student information should not simply be placed in a publicly accessible bucket.

Conclusion

Amazon Athena demonstrates how cloud computing can simplify data analytics.

Instead of setting up and managing database servers, we can store data in Amazon S3 and use SQL through Athena to analyze it. Its serverless architecture, SQL support, integration with AWS Glue and ability to work with different data formats make it useful for many analytics scenarios.

For students, Athena provides an interesting way to learn cloud computing, SQL, data lakes and analytics together. A college project could use it to analyze student activities, attendance, events or other datasets stored in S3.

My key takeaway is simple:

Store the data in the cloud, query it with SQL, and let AWS manage the infrastructure.

And for me:

A for Amutha → A for Athena.

📚 References

1. Amazon Athena Documentation
   AWS Amazon Athena Documentation

2. Amazon Athena Features
   AWS Athena Features

3. Amazon Athena Getting Started Guide
   AWS Athena Getting Started

4. Amazon Athena Pricing
   AWS Athena Pricing

5. Amazon Athena Security Documentation
   AWS Athena Security