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

Amazon Athena vs Amazon OpenSearch Service comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 8, 2026

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
5th
Average Rating
7.8
Reviews Sentiment
7.2
Number of Reviews
11
Ranking in other categories
No ranking in other categories
Amazon OpenSearch Service
Ranking in Search as a Service
3rd
Average Rating
7.6
Reviews Sentiment
6.7
Number of Reviews
13
Ranking in other categories
Application Performance Monitoring (APM) and Observability (29th), Log Management (17th)
 

Mindshare comparison

As of November 2026, in the Search as a Service category, the mindshare of Amazon Athena is 5.4%, down from 5.9% compared to the previous year. The mindshare of Amazon OpenSearch Service is 13.4%, up from 5.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Amazon OpenSearch Service13.4%
Amazon Athena5.4%
Other81.2%
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.
Md. Shahariar Hossen - PeerSpot reviewer
Senior Software Engineer at Cefalo
Event tracking has become smoother and data analytics provide clear insights for user actions
Amazon OpenSearch Service is not providing the processing feature directly. From Amazon OpenSearch Service, we are actually maintaining the AWS SQS, the queue service, which is responsible for providing information about what data has to be modified. So using that SQS, we're actually providing it, but we're not directly using Amazon OpenSearch Service for keeping data to other data pipeline thing. So far we didn't use it for any machine learning purposes, but in future, we have plans to extend or implement this feature. Since AWS itself is secure and Amazon OpenSearch Service is a part of this entire ecosystem, it becomes much easier for security purposes. From the validation point of view, Amazon OpenSearch Service itself provides easy to communicate APIs and up-to-date documents, which is much beneficial. For example, if I'm missing anything, I can directly go and check the documentation. That is actually much easier. I would rate it as really good so far. It's much faster. For our local machine, we can also use a kind of replica of Amazon OpenSearch Service just for development purposes. That is another good feature. I would say for the encryption thing and also the user access control management, it's much faster. For some of these hashing algorithms, it also worked really well so far. To be honest, I didn't find any places where it can be improved. However, I think they could provide more abstraction. For example, still for searching, we have to write down the queries in a specific manner, such as for a specific JSON structure or in a specific way. Otherwise, they don't provide us the actual results. For at least this purpose, I think abstraction could be a bit easier or a bit improved. Other than that, right now there is the age of AI, so some kind of prompting could also work, but I'm not sure how it could be integrated. As a user, lower prices or reasonable pricing is always better. Those can be improved as well. However, it is good that most of the services including Amazon OpenSearch Service actually provide pay as you go pricing. So if there were a bit lower version or a bit less payment methodology, it might be much better.

Quotes from Members

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

Pros

"It's easy to set up the product."
"Athena has a really good UI and is very compatible with on-prem products."
"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."
"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."
"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."
"Amazon Athena is very stable. I never had any issues with it. The dashboarding tool is okay."
"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 has positively impacted my organization by providing a completely serverless infrastructure."
"In case there is a failure, Elastic manages everything well, and there no major downtime."
"The stability of the product is good."
"The customer service is excellent, rated nine out of ten."
"The business analytics capabilities are the most important feature it provides."
"Amazon OpenSearch Service has enhanced our organization's ability to store and search large amounts of data efficiently."
"They have the good documentation in the help text and that is the reason the Amazon Elasticsearch is the perfect solution for the current market."
"Our customers have seen tangible benefits from Amazon OpenSearch Service, especially in terms of their applications running smoothly, so they do get a return on investment."
"It's actually easier to collaborate since it is already deployed in the AWS cloud itself."
 

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."
"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."
"The solution should include a better API for query services."
"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."
"In terms of its integration capabilities, I would say it's not straightforward. It works, but it's a little bit tricky."
"They can enhance data visualization."
"The price is fair yet leans towards the expensive side. I'd rate it five out of ten with respect to capabilities vs. cost."
"The pricing aspect is a concern. The service is way too costly. For the past month, I used only 30 to 40 MB of data, and the cost was $500. AWS could improve pricing."
"One improvement I would like to see is support for auto-scaling."
"I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels."
"We faced documentation challenges during integration after migrating from Elasticsearch to Amazon OpenSearch Service. Better documentation on integration, query handling, and a more user-friendly UI could enhance the product."
"The configuration should be more straightforward because we had to select a lot of things."
"In terms of data handling capabilities with Amazon OpenSearch Service, they can be complex and managing data in comparison to other SIM solutions is a major drawback, as it is very hard to handle the data."
 

Pricing and Cost Advice

"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."
"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 is not expensive, but priced averagely, I will say."
"You only pay for what you use."
"There is a community edition available and the price of the commercial offering is reasonable."
"Compared to other cloud platforms, it is manageable and not very expensive."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
921,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
13%
Outsourcing Company
10%
Comms Service Provider
7%
Financial Services Firm
14%
Manufacturing Company
10%
Computer Software Company
8%
Outsourcing Company
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 Business7
Midsize Enterprise2
Large Enterprise4
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon Athena?
My experience with Amazon Athena regarding pricing, setup costs, and licensing is quite clear after more than three years of usage. I am part of my client's FinOps cloud team, assisting in reducing...
What needs improvement with Amazon Athena?
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 ...
What is your primary use case for Amazon Athena?
My main use case for Amazon Athena is serving a healthcare organization in the US that needed an interactive SQL editor to write complex queries and retrieve details instead of checking manually in...
What is your experience regarding pricing and costs for Amazon OpenSearch Service?
I would consider the pricing as a six based on how much data we are handling; if we handle minimal data, it's cheap, but for large data, it becomes costly. Our clients usually pay between $1,000 to...
What needs improvement with Amazon OpenSearch Service?
Amazon OpenSearch Service is not providing the processing feature directly. From Amazon OpenSearch Service, we are actually maintaining the AWS SQS, the queue service, which is responsible for prov...
What is your primary use case for Amazon OpenSearch Service?
Amazon OpenSearch Service is a user-friendly version of Elasticsearch, as per my understanding. I have been using it for our volunteer management system where around 5,000 to 6,000 users are using ...
 

Also Known As

No data available
Amazon Elasticsearch Service
 

Overview

 

Sample Customers

bp, Cerner, Expedia, Finra, HESS, intuit, Kellog's, Philips, TIME, workday
VIDCOIN, Wyng, Yellow New Zealand, zipMoney, Cimri, Siemens, Unbabel
Find out what your peers are saying about Amazon Athena vs. Amazon OpenSearch Service and other solutions. Updated: November 2026.
921,028 professionals have used our research since 2012.