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

Amazon AWS CloudSearch 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 AWS CloudSearch
Ranking in Search as a Service
7th
Average Rating
8.4
Number of Reviews
13
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 (8th), Vector Databases (6th)
 

Mindshare comparison

As of November 2026, in the Search as a Service category, the mindshare of Amazon AWS CloudSearch is 6.8%, down from 6.8% compared to the previous year. The mindshare of Elastic Search is 15.3%, down from 18.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service Mindshare Distribution
ProductMindshare (%)
Elastic Search15.3%
Amazon AWS CloudSearch6.8%
Other77.9%
Search as a Service
 

Featured Reviews

HM
Software Developer at ECFY Consulting Private Limited
Search workflows have become faster and our team manages operational records more efficiently
Improvements for Amazon AWS CloudSearch can be made, but I will first start with the biggest improvement. The biggest improvement area is that Amazon AWS CloudSearch feels a little older compared to newer AWS services. The second thing about improvement is the documentation. The documentation could definitely be refreshed with more practical examples and troubleshooting scenarios. During setup, a few indexing issues took longer to diagnose because error messages were pretty generic. Better debugging visibility would reduce trial-and-error work. Monitoring is decent through Amazon CloudWatch, but I would like more detailed search-level diagnostics out of the box. Sometimes it is not obvious why certain queries rank results differently unless you manually test a lot. More transparent query analysis, indexing, and insights would be useful. Logging exists, but deeper visibility would help during optimization.
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

"The initial setup is straightforward."
"It's the best solution for any company. It has a hosting ERP system for any task. AWS is stable. AWS is more flexible and its elastic concept is a new concept. AWS is also very secure. It has many layers of security, like hardware security and software security. This is a big issue."
"We were able to build the core search functionality using this product."
"It is remarkably efficient and beneficial."
"The best feature is its scalability in that Cloud is always on the fly."
"Amazon AWS CloudSearch is practical and dependable for teams that want managed search without a lot of infrastructure management."
"Document indexing, text-based search API, and Geospatial searches are all good features."
"The most valuable feature of Amazon AWS CloudSearch is its ability to receive data quickly, and you can access your data easily in a short time."
"The Attack Discovery feature helps to dig into incidents from where they occurred to determine how the incident originated and its source; it gives an entire path of attack propagation, showing when it started, what happened, and all events that took place to connect the entire cyber incident."
"The security portion of Elasticsearch is particularly beneficial, allowing me to view and analyze security alerts."
"I appreciate the indexing capabilities and the speed of indexing in their product, which demonstrates how quickly logs are collected and stored."
"The AI-based attribute tagging is a valuable feature."
"Big businesses cannot survive without Elastic Search because it gives us very good visibility and handles our use cases very well."
"I find the solution to be fast."
"In the last 18 months Elastic has really caught up and also gone way beyond AWS by putting together all the missing components that make ELK Elasticsearch the most comprehensive stack in the entire Big Data ecosystem."
"The solution is valuable for log analytics."
 

Cons

"Security is a concern but they're working on it."
"A reboot should be enhanced."
"Latlon data type only supports single value per document. All other types support multiple values. We faced issues with this because we had scenarios where, for each document, we needed to store multiple latlon values for different geographical locations."
"Amazon AWS CloudSearch is highly stable. However, the speed depends on your internet connection."
"Regarding the period of propagation on CDN servers, sometimes we update photos or files and we don't see the update instantly. We need to wait for sometime, which is quite boring because we may be setting up a marketing campaign which is related to the product's photo and we need to wait to start."
"Maybe they are common in Egypt, but you should make a request on Amazon to create a function to monitor CPU performance, memory, and files. It is very difficult in AWS. I would tell them it should be simple, just drag and drop. I think they could develop this option so we can drag and drop to monitor performance of the processor and memory."
"Amazon's technical support needs to improve as they only solve about half our problems."
"The solution should improve the recovery aspects that it has on offer."
"Machine learning on search needs improvement."
"This solution is stable, but at times the stack will freeze and you have to remove and recreate the cluster."
"The solution has quite a steep learning curve. The usability and general user-friendliness could be improved."
"The metadata gets stored along with indexes and isn't queryable."
"They should improve its documentation. Their official documentation is not very informative. They can also improve their technical support. They don't help you much with the customized stuff. They also need to add more visuals. Currently, they have line charts, bar charts, and things like that, and they can add more types of visuals. They should also improve the alerts. They are not very simple to use and are a bit complex. They could add more options to the alerting system."
"In Elastic Search, the improvements I would like to see require many resources."
"The open source version should ship basic security versions with it."
"I would like to see more integration for the solution with different platforms."
 

Pricing and Cost Advice

"Our license costs around $4,000 per month."
"Amazon AWS CloudSearch charging is based on how many resources you consume or and the solution is known to be a bit expensive."
"I'm not sure how much we pay a year. It might be around $30,000 a year."
"We chose AWS because of its cost and stability."
"In comparison to IBM and Microsoft, the pricing is more favorable."
"There was no license needed to use this solution."
"On a scale of one to ten, where one point is cheap, and ten points are expensive, I rate the pricing as medium or reasonable."
"​The pricing and license model are clear: node-based model."
"The solution is affordable."
"The price of Elastic Enterprise is very, very competitive."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"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."
"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"There is a free version, and there is also a hosted version for which you have to pay. We're currently using the free version. If things go well, we might go for the paid version."
"To access all the features available you require both the open source license and the production license."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
920,929 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
13%
Construction Company
11%
Outsourcing Company
10%
Educational Organization
9%
Financial Services Firm
11%
Outsourcing Company
9%
Manufacturing Company
9%
Comms Service Provider
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise6
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise50
 

Questions from the Community

What is your experience regarding pricing and costs for Amazon AWS CloudSearch?
We purchased Amazon AWS CloudSearch through the AWS Marketplace. Pricing was understandable once we estimated indexing volume and query traffic. Though it can grow if you scale instances aggressive...
What needs improvement with Amazon AWS CloudSearch?
Improvements for Amazon AWS CloudSearch can be made, but I will first start with the biggest improvement. The biggest improvement area is that Amazon AWS CloudSearch feels a little older compared t...
What is your primary use case for Amazon AWS CloudSearch?
The main use case for us was to search the operational records from our company databases and perform full-text search across operational records and uploaded documents. We needed something where u...
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...
 

Also Known As

No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

SmugMug
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 AWS CloudSearch vs. Elastic Search and other solutions. Updated: September 2026.
920,929 professionals have used our research since 2012.