Try our new research platform with insights from 80,000+ expert users

Amazon Athena vs Elastic Search comparison

 

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
9
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
89
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Vector Databases (2nd)
 

Mindshare comparison

As of February 2026, in the Search as a Service category, the mindshare of Amazon Athena is 5.2%, down from 11.9% compared to the previous year. The mindshare of Elastic Search is 18.3%, up from 14.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Market Share Distribution
ProductMarket Share (%)
Elastic Search18.3%
Amazon Athena5.2%
Other76.5%
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.
Anurag Pal - PeerSpot reviewer
Technical Lead at a consultancy with 10,001+ employees
Search and aggregations have transformed how I manage and visualize complex real estate data
Elastic Search consumes lots of memory. You have to provide the heap size a lot if you want the best out of it. The major problem is when a company wants to use Elastic Search but it is at a startup stage. At a startup stage, there is a lot of funds to consider. However, their use case is that they have to use a pretty significant amount of data. For that, it is very expensive. For example, if you take OLTP-based databases in the current scenario, such as ClickHouse or Iceberg, you can do it on 4GB RAM also. Elastic Search is for analytical records. You have to do the analytics on it. According to me, as far as I have seen, people will start moving from Elastic Search sooner or later. Why? Because it is expensive. Another thing is that there is an open source available for that, such as ClickHouse. Around 2014 and 2012, there was only one competitor at that time, which was Solr. But now, not only is Solr there, but you can take ClickHouse and you have Iceberg also. How are we going to compete with them? There is also a fork of Elastic Search that is OpenSearch. As far as I have seen in lots of articles I am reading, users are using it as the ELK stack for logs and analyzing logs. That is not the exact use case. It can do more than that if used correctly. But as it involves lots of cost, people are shifting from Elastic Search to other sources. When I am talking about pricing, it is not only the server pricing. It is the amount of memory it is using. The pricing is basically the heap Java, which is taking memory. That is the major problem happening here. If we have to run an MVP, a client comes to me and says, "Anurag, we need to do a proof of concept. Can we do it if I can pay a 4GB or 16GB expense?" How can I suggest to them that a minimum of 16GB is needed for Elastic Search so that your proof of concept will be proved? In that case, what I have to suggest from the beginning is to go with Cassandra or at the initial stage, go with PostgreSQL. The problem is the memory it is taking. That is the only thing.

Quotes from Members

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

Pros

"Athena has a really good UI and is very compatible with on-prem products."
"Amazon Athena works for scalability; I query data using tagged data that uses user usage of applications that contain very big data, millions and billions of lines, and it works very well."
"It's easy to set up the product."
"The solution is very easy to use and integrations are very smooth."
"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 is very stable. I never had any issues with it. The dashboarding tool is okay."
"All the quality features are there. There are about 60 to 70 reports available."
"Overall, considering key aspects like cost, learning curve, and data indexing architecture, Elasticsearch is a very good tool."
"The most valuable features of Elastic Enterprise Search are it's cloud-ready and we do a lot of infrastructure as code. By using ELK, we're able to deploy the solution as part of our ISC deployment."
"Elastic Enterprise Search is scalable. On a scale of one to 10, with one being not scalable and 10 being very scalable, I give Elastic Enterprise Search a 10."
"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."
"The most valuable features are the ease and speed of the setup."
"It helps us to analyse the logs based on the location, user, and other log parameters."
"The initial installation and setup were straightforward."
 

Cons

"The solution should include a better API for query services."
"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."
"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."
"You have to build out the metadata yourself because of the nature of the cloud."
"The documentation for Elastic Search can be challenging if you're not already familiar with the platform."
"Elasticsearch should have simpler commands for window filtering."
"There were also some difficult times with parallel and point-in-time interfaces, so better documentation could help, particularly more example-driven content."
"Dashboards could be more flexible, and it would be nice to provide more drill-down capabilities."
"The UI point of view is not very powerful because it is dependent on Kibana."
"There are potential improvements based on our client feedback, like unifying the licensing cost structure."
"Its licensing needs to be improved. They don't offer a perpetual license. They want to know how many nodes you will be using, and they ask for an annual subscription. Otherwise, they don't give you permission to use it. Our customers are generally military or police departments or customers without connection to the internet. Therefore, this model is not suitable for us. This subscription-based model is not the best for OEM vendors. Another annoying thing about Elasticsearch is its roadmap. We are developing something, and then they say, "Okay. We have removed that feature in this release," and when we are adapting to that release, they say, "Okay. We have removed that one as well." We don't know what they will remove in the next version. They are not looking for backward compatibility from the customers' perspective. They just remove a feature and say, "Okay. We've removed this one." In terms of new features, it should have an ODBC driver so that you can search and integrate this product with existing BI tools and reporting tools. Currently, you need to go for third parties, such as CData, in order to achieve this. ODBC driver is the most important feature required. Its Community Edition does not have security features. For example, you cannot authenticate with a username and password. It should have security features. They might have put it in the latest release."
"The upgrade experience and inflexibility with fields keeps Elastic Search from being a perfect 10."
 

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."
"It can be expensive."
"We are using the free open-sourced version of this solution."
"We use the free version for some logs, but not extensive use."
"I rate Elastic Search's pricing an eight out of ten."
"We are using the open-sourced version."
"​The pricing and license model are clear: node-based model."
"The price of Elasticsearch is fair. It is a more expensive solution, like QRadar. The price for Elasticsearch is not much more than other solutions we have."
"Although the ELK Elasticsearch software is open-source, we buy the hardware."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
882,637 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Financial Services Firm
14%
Manufacturing Company
11%
Healthcare Company
9%
Financial Services Firm
12%
Computer Software Company
12%
Manufacturing Company
9%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise3
Large Enterprise2
By reviewers
Company SizeCount
Small Business37
Midsize Enterprise10
Large Enterprise44
 

Questions from the Community

What needs improvement with Amazon Athena?
I don't have any specific answer on how Amazon Athena can be improved. This integration is more on the Glue side rather than on Amazon Athena, I would guess. Nothing comes to my mind here. In terms...
What is your primary use case for Amazon Athena?
The typical use case for Amazon Athena is that we have data in a data lake, and if we need to query the data from the data lake, we use Amazon Athena before it gets to the data warehouse where we w...
What advice do you have for others considering Amazon Athena?
I have experience of integration of Amazon Athena with AWS Glue. I think the pricing of Amazon Athena is quite reasonable as we use it in pay-as-you-go mode. On a scale from one to ten, I rate Amaz...
What do you like most about ELK Elasticsearch?
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 anal...
What is your experience regarding pricing and costs for ELK Elasticsearch?
On the subject of pricing, Elastic Search is very cost-efficient. You can host it on-premises, which would incur zero cost, or take it as a SaaS-based service, where the expenses remain minimal.
What needs improvement with ELK Elasticsearch?
While Elastic Search is a good product, I see areas for improvement, particularly regarding the misconception that any amount of data can simply be dumped into Elastic Search. When creating an inde...
 

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: February 2026.
882,637 professionals have used our research since 2012.