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
10
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

Ciro Baldim Guerra - PeerSpot reviewer
Sr Analytics Engineer at Itau Unibanco S.A.
Have struggled with exporting complex data and have disabled code suggestions due to inefficiency
I think there is room for improvement in Amazon Athena, and the first thing I will put is the data output. 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. The only option is copying the data, but sometimes if it exceeds 100 lines, if you copy and paste in Excel, it's very bad. You can't copy above 100 lines. The other option is downloading a CSV file, but the CSV file is not UTF-8 Unicode. Here in Brazil, we speak Portuguese, and there are a lot of special characters in the words and even names, and everything gets garbled when you put it in a CSV. You have to decode, encode, and there are a lot of problems. It could easily save as an Excel file since there are a lot of engines to help with it, so an XLSX file extension could be this way. Another point I would mention is the word completion. When I'm coding and making statements and queries, Amazon Athena tries to help me write the code, and that's very problematic. Sometimes I'm using some tables that I use every day, and Amazon Athena doesn't get the tables I'm using and suggests very improbable data. I have access to more than 30 databases and hundreds of tables. So, I turn it off, I disable the word completion because when I'm coding, the word completion makes the coding slower. It's very difficult, and every time I have to press escape to skip the completion. It's very ineffective, so I disable it because in other applications it functions very well, such as VS Code.
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

"One of the most valuable features is the ability to partition your databases. I also like the federal query functionality, for cases when you have to query outside your S3 storage, or even completely outside of the AWS platform."
"Amazon Athena's ability to query structured and unstructured data has been beneficial."
"It's easy to set up the product."
"The solution is very easy to use and integrations are very smooth."
"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."
"Athena has a really good UI and is very compatible with on-prem products."
"Amazon Athena is very stable. I never had any issues with it. The dashboarding tool is okay."
"I would recommend Elastic Search to other people who want to have fast search in their applications."
"On the subject of pricing, Elastic Search is very cost-efficient, as you can host it on-premises, which would incur zero cost, or take it as a SaaS-based service, where the expenses remain minimal."
"The pricing and license model are clear: node-based model."
"Data indexing of historical data is the most beneficial feature of the product."
"There are a lot of good things about this solution. First, it is an extremely fast search. We have quite an extensive number of logs, and we can search through billions of documents in just a few minutes, and get the results we're looking for."
"This is a very rich product, and it's got a very wide functionality, and a wide range of functionalities which I don't see in the other products, especially not in the cheaper ones."
"The most valuable feature of Elastic Enterprise Search is the Discovery option for the visualization of logs on a GPU instead of on the server."
"ELK Elasticsearch is 100% scalable as scalability is built into the design"
 

Cons

"The solution should include a better API for query services."
"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."
"Amazon Athena can be improved, especially when working with S3 tables, which is a caveat for us."
"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."
"In terms of its integration capabilities, I would say it's not straightforward. It works, but it's a little bit tricky."
"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."
"Transaction support is one of the biggest missing features."
"You have to build out the metadata yourself because of the nature of the cloud."
"It is hard to learn and understand because it is a very big platform. This is the main reason why we still have nothing in production. We have to learn some things before we get there."
"There are challenges with performance management and scalability."
"More AI would be beneficial. I would also appreciate more simplicity in dashboards."
"The one area that can use improvement is the automapping of fields."
"There is a lack of technical people to develop, implement and optimize equipment operation and web queries."
"The solution must provide AI integrations."
"They're making changes in their architecture too frequently."
"The deployment was a struggle as I faced challenges with bash commands and understanding how to run things on my system."
 

Pricing and Cost Advice

"The solution operates on a serverless model so you only pay for data that you consume."
"It doesn't cost much if you are already part of the AWS ecosystem."
"Athena is very inexpensive for being a cloud tool."
"I am happy with what they are charging and how they charge it, especially because they charge you per query, and not per series."
"We are using the free version and intend to upgrade."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"The solution is less expensive than Stackdriver and Grafana."
"The cost varies based on factors like usage volume, network load, data storage size, and service utilization. If your usage isn't too extensive, the cost will be lower."
"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."
"It can be expensive."
"The price of Elastic Enterprise is very, very competitive."
"I rate Elastic Search's pricing an eight out of ten."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
912,022 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
13%
Outsourcing Company
10%
Healthcare Company
7%
Financial Services Firm
11%
Manufacturing Company
9%
Outsourcing Company
8%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise3
Large Enterprise3
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: August 2026.
912,022 professionals have used our research since 2012.