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

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

Mindshare comparison

As of May 2026, in the Search as a Service category, the mindshare of Amazon Athena is 4.8%, down from 10.1% compared to the previous year. The mindshare of Elastic Search is 17.6%, up from 15.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Elastic Search17.6%
Amazon Athena4.8%
Other77.6%
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."
"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."
"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."
"Amazon Athena's ability to query structured and unstructured data has been beneficial."
"The solution is very easy to use and integrations are very smooth."
"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."
"Amazon Athena is very stable. I never had any issues with it. The dashboarding tool is okay."
"The search speed is most valuable and important."
"I have found the sort capability of Elastic very useful for allowing us to find the information we need very quickly."
"The best feature of Elastic Search is it does exactly what it says."
"Gives us a more user-friendly, centralized solution (for those who just needed a quick glance, without being masters of sed and awk) as well as the ability to implement various mechanisms for machine-learning from our logs, and sending alerts for anomalies."
"Elastic Enterprise Search is a very good solution and they should keep doing good work."
"The AI-based attribute tagging is a valuable feature."
"The solution is very good with no issues or glitches."
"The tool's stability and performance are good."
 

Cons

"You have to build out the metadata yourself because of the nature of the cloud."
"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."
"The solution should include a better API for query services."
"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."
"Transaction support is one of the biggest missing features."
"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."
"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."
"Elastic Enterprise Search could improve the report templates."
"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."
"More AI would be beneficial. I would also appreciate more simplicity in dashboards."
"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 documentation regarding customization could be better."
"The most significant issue I find with Elastic Search is that it gets out of sync, and this has happened in both cases where I have implemented it."
"We have an issue with the volume of data that we can handle."
"Elasticsearch is useful for different business processes, but there are some problems."
 

Pricing and Cost Advice

"It doesn't cost much if you are already part of the AWS ecosystem."
"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 solution operates on a serverless model so you only pay for data that you consume."
"Athena is very inexpensive for being a cloud tool."
"The solution is not expensive because users have the option of choosing the managed or the subscription model."
"The pricing structure depends on the scalability steps."
"The price of Elastic Enterprise is very, very competitive."
"We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition."
"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"This product is open-source and can be used free of charge."
"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."
"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
892,646 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
13%
Computer Software Company
10%
Outsourcing Company
7%
Financial Services Firm
12%
Computer Software Company
9%
Manufacturing Company
9%
Retailer
6%
 

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 Business39
Midsize Enterprise11
Large Enterprise46
 

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 is your experience regarding pricing and costs for ELK Elasticsearch?
When it comes to pricing, I think we had to pay AWS approximately 1,000 to 1,200 per month for the overall stack. I am not quite certain about how much Elastic Search costs specifically because I w...
What needs improvement with ELK Elasticsearch?
Elastic Search has many features, including Kibana and Logstash, which we regularly use. However, one downside in our product is cost, as it can be expensive when maintaining multiple shards and in...
What is your primary use case for ELK Elasticsearch?
As a developer, I use Elastic Search in developing one of my applications, basically integrating the back-end with Elastic Search. Our main use case for Elastic Search is for Logstash, which is a s...
 

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: April 2026.
892,646 professionals have used our research since 2012.