No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon Athena vs Elastic Search comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Amazon Athena
Ranking in Search as a Service
6th
Average Rating
7.8
Reviews Sentiment
7.2
Number of Reviews
11
Ranking in other categories
No ranking in other categories
Elastic Search
Ranking in Search as a Service
1st
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
100
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Vector Databases (6th)
 

Mindshare comparison

As of September 2026, in the Search as a Service category, the mindshare of Amazon Athena is 5.3%, down from 5.9% compared to the previous year. The mindshare of Elastic Search is 15.7%, down from 19.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Elastic Search15.7%
Amazon Athena5.3%
Other79.0%
Search as a Service
 

Featured Reviews

YM
Senior Software Engineer at a tech services company with 10,001+ employees
Serverless analytics has reduced daily data query costs and supports accurate financial reporting
The best features Amazon Athena offers are its straightforward framework to perform ad hoc analysis on the data that we have. We use it primarily as our main query engine, so we are not using anything such as Snowflake or similar solutions. We essentially ingest the data into S3 buckets, and then we use Amazon Athena for querying the data. It is our main query platform on AWS. All of our queries, for transformations, are Athena-based queries that are orchestrated via Step Functions. We only pay for the amount of data that we scan. Since we operate on a relatively lower amount of data on a daily basis, we incur a very low cost on our querying. The pay-per-query pricing of Amazon Athena impacts my daily operations significantly. For other query engines, we pay for the query execution time, but in Amazon Athena, you only pay for the amount of data that you have scanned. Our queries primarily filter out the data. Since we operate on a daily basis, we are only concerned with today's data. When querying the data, we automatically put the filter to have the data in today's timestamp only. This way, we incur very low costs compared to other query engines. Our query scans are about 10 to 20 MBs, and despite performing 100 to 150 queries per day, this keeps our costs very manageable. Amazon Athena has positively impacted my organization by providing a completely serverless infrastructure. We have Step Functions, Lambda, and S3 buckets where we store our data. Our main infrastructure is serverless. We wanted a query engine that is less demanding in terms of setup efforts and cost-efficient, so we decided to go with Amazon Athena. It fulfills all our use cases, plus the ACID compliance that it brings, because we use Iceberg on top of Amazon Athena. This ensures our queries and data are consistent, durable, and that the queries are isolated in terms of execution. Athena's ACID compliance, especially with Iceberg, impacts our data consistency and reliability. We apply Iceberg with Parquet, which helps us compress the data to a very good volume. With the applied compression algorithms, we preserve our data consistency during parallel transformations. ACID compliance helps us achieve this, ensuring we do not compromise on our data and that our GDPR for the data is preserved.
reviewer2817942 - PeerSpot reviewer
Senior Software Engineer at a consultancy with 11-50 employees
Logging and vector search have transformed observability and empowered reliable ai agents
Elastic Search is not specifically being used for certain purposes. I deploy Elastic Search database on the cloud and use cloud services so that nobody can attack. However, I do not use Elastic Search to resolve attack issues. The basic main purpose of Elastic Search, as of now, I feel it can do more in the AI area. Sometime I saw that when I am developing RAG and have to generate the embeddings, which I call metadata, sometimes it tries to fail. That durability or issue handling should be improved, but apart from that, I did not find anything as of now. As per my use case, whatever I am using seems pretty good. Apart from that, some definitely improvement will be there. One improvement is that it should be faster. Whenever I am searching any logs, it takes much time. For example, if I open my log in Notepad or a similar tool, I can search the text within a second. With Elastic Search, it takes a little bit of time, ten to fifteen seconds. That can be improved. Sometimes, engineers take time to assign when I create a ticket.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Athena is serverless, so we don’t have to provision or manage compute clusters, and we can simply point Athena at our data in S3 and run SQL queries immediately."
"The best feature of Amazon Athena is that we can use Glue to build the schema from the data and then we can query the data directly on S3."
"The solution is very easy to use and integrations are very smooth."
"Amazon Athena is very stable. I never had any issues with it. The dashboarding tool is okay."
"Athena has a really good UI and is very compatible with on-prem products."
"After implementing Amazon Athena in our project, we have observed significant savings in cost structure and effort, and the end user is very happy and is conducting analytical work using Amazon Athena."
"It's easy to set up the product."
"Amazon Athena has positively impacted my organization by providing a completely serverless infrastructure."
"Elastic Search's main advantages are the visuals that represent and visualize all entities and system components in a simplified diagram, which provides the ability to identify which component in the system has an issue."
"Elastic Search is very quick when handling a large volume of data."
"It is a stable and good platform."
"We chose Elasticsearch because we could build a model in a short amount of time, allowing us to build a whole setup in one month and get 93% accuracy, with complex AI-based features built in a shorter span and with high accuracy that wasn't possible with other search enterprise vendors we used."
"Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time analytics with Elastic benefits us due to the huge traffic volume in our organization, which reaches up to 60,000 requests per second. With logs of approximately 25 GB per day, manually analyzing traffic behavior, payloads, headers, user agents, and other details is impractical."
"Elasticsearch includes a graphical user interface (GUI) called Kibana, and the GUI features are extremely beneficial to us."
"The solution has good security features. I have been happy with the dashboards and interface."
"The AI-based attribute tagging is a valuable feature."
 

Cons

"I think it would be better if the product were more mature. It's still a young product compared to Power BI or Qlik. I find that development is a bit difficult, but it might be because I'm used to other tools. The dashboarding capabilities could be better. The reporting and statement generation could be better. I couldn't technically initiate picture-perfect reporting, for example, to send out statements every month for banking customers."
"Amazon Athena can be improved, especially when working with S3 tables, which is a caveat for us."
"I use Python to query in Amazon Athena, and it's very complex and difficult just to save Amazon Athena results as an Excel file."
"One improvement I can suggest is that Athena needs to work better with third-parties. For example, the process of querying a Microsoft SQL warehouse could be improved."
"If you compare it with Palantir, if you have some data and you want to quickly have a look at it, then that feature is not available in Amazon Cloud."
"While implementing Amazon Athena, I observed an issue where, even after writing an exclusion pattern on the AWS Glue side, whenever the end user queries, it skips the exclusion pattern, overriding it and directly fetching data from the S3 bucket."
"Transaction support is one of the biggest missing features."
"The solution should include a better API for query services."
"Whenever I am searching any logs, it takes much time; for example, if I open my log in Notepad or a similar tool, I can search the text within a second, but with Elastic Search, it takes a little bit of time, ten to fifteen seconds."
"It should be easier to use. It has been getting better because many functions are pre-defined, but it still needs improvement."
"Scalability of Elastic Search presents disadvantages, particularly when handling minimal or production-level data."
"The solution itself needs improvement. There is an index issue in which the data starts to crash as it increases."
"The price could be better."
"The initial configuration could be easier; at first, the learning curve is a little high, and over time, it becomes easier."
"Elastic Enterprise Search could improve the report templates."
"This is not exactly a stable solution, which is why we are considering another compatible tool, and whether we go on with Elasticsearch or change it."
 

Pricing and Cost Advice

"It doesn't cost much if you are already part of the AWS ecosystem."
"Athena is very inexpensive for being a cloud tool."
"The solution operates on a serverless model so you only pay for data that you consume."
"I am happy with what they are charging and how they charge it, especially because they charge you per query, and not per series."
"The pricing structure depends on the scalability steps."
"We are using the free open-sourced version of this solution."
"The solution is not expensive because users have the option of choosing the managed or the subscription model."
"It can move from $10,000 US Dollars per year to any price based on how powerful you need the searches to be and the capacity in terms of storage and process."
"​The pricing and license model are clear: node-based model."
"The solution is free."
"We use the free version for some logs, but not extensive use."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
913,683 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
12%
Outsourcing Company
10%
Healthcare Company
7%
Financial Services Firm
11%
Outsourcing Company
9%
Manufacturing Company
9%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise3
Large Enterprise4
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise50
 

Questions from the Community

What needs improvement with Amazon Athena?
Amazon Athena can be improved, especially when working with S3 tables, which is a caveat for us. It does not work very well with Amazon Athena, as we have to do multiple settings in terms of provid...
What is your primary use case for Amazon Athena?
My main use case for Amazon Athena is querying data that sits in S3 buckets. Currently, I am working for an aviation client for which we receive data on a daily basis. We take this data from a sour...
What advice do you have for others considering Amazon Athena?
Regarding Amazon Athena's AI capabilities, we do not utilize them. However, data governance is ensured, and security is adequate since we operate within the VPC. ACID compliance helps preserve GDPR...
What is your experience regarding pricing and costs for ELK Elasticsearch?
The pricing for Elastic Search is mainly budgeted according to the organization budget, so we take it as a yearly subscription, and that is acceptable since we do get a fair discount when we are ta...
What needs improvement with ELK Elasticsearch?
When we get the logs, it is mostly about how we edit the configurations and how we make changes according to the requirements of our organization. In these cases, the logs sometimes can be a bit in...
What is your primary use case for ELK Elasticsearch?
I am the Elastic Search admin for my organization, and we are using Elastic Search to handle the traffic to GCP. The monitoring of all the clusters and all the deployments are quite good, and compa...
 

Comparisons

 

Also Known As

No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

bp, Cerner, Expedia, Finra, HESS, intuit, Kellog's, Philips, TIME, workday
T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Find out what your peers are saying about Amazon Athena vs. Elastic Search and other solutions. Updated: September 2026.
913,683 professionals have used our research since 2012.