We performed a comparison between Amazon Elasticsearch Service and Elastic Search based on real PeerSpot user reviews.
Find out in this report how the two Search as a Service solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."In case there is a failure, Elastic manages everything well, and there no major downtime."
"They have the good documentation in the help text and that is the reason the Amazon is the perfect solution in the current market."
"The initial set up is very easy...We really appreciate Amazon!"
"The stability of the product is good."
"Regarding valuable features of the solution, we found with the process, which we have used in both cases where we used the solution that while you're seeing the streaming of data, you can analyze in the initial phase what sort of data you are streaming and whether it is valuable."
"The most valuable features of Amazon Elasticsearch are ease of use, native JSON, and efficiency. Additionally, handles many use cases and search grammar was useful."
"It enables us to efficiently search and retrieve our event data, offering us a versatile approach to locate specific information within these logs."
"It's a good log management platform. In terms of infrastructure management, it's good."
"I value the feature that allows me to share the dashboards to different people with different levels of access."
"The most valuable feature is the out of the box Kibana."
"It is easy to scale with the cluster node model."
"Data indexing of historical data is the most beneficial feature of the product."
"It gives us the possibility to store and query this data and also do this efficiently and securely and without delays."
"The most valuable features are the detection and correlation features."
"The solution has good security features. I have been happy with the dashboards and interface."
"The solution offers good stability."
"Amazon Elasticsearch can improve the bullion in the near search and the ease of integration with Kibana. Additionally, there could be more flexibility in the configuration and documentation."
"There is a problem with the database. Amazon only provides the hosting to run our applications bias, but there is no option to manage the database within the Elasticsearch product."
"One glaring issue was with our mapping configuration as the system accepted the data we posted, but after a few months, when we attempted complex queries, we realized the date formatting had become problematic."
"The configuration should be more straightforward because we had to select a lot of things."
"I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels."
"I would say that, basically, the configuration part is an area with a shortcoming...Some upgradation is required on the configuration side so that we can get to use it."
"Improving machine learning capabilities would be beneficial."
"I would like to see more integration for the solution with different platforms."
"I would like to be able to do correlations between multiple indexes."
"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."
"There are potential improvements based on our client feedback, like unifying the licensing cost structure."
"Better dashboards or a better configuration system would be very good."
"They're making changes in their architecture too frequently."
"Performance improvement could come from skipping background refresh on search idle shards (which is already being addressed in the upcoming seventh version)."
Amazon Elasticsearch Service is ranked 3rd in Search as a Service with 6 reviews while Elastic Search is ranked 1st in Search as a Service with 59 reviews. Amazon Elasticsearch Service is rated 8.2, while Elastic Search is rated 8.2. The top reviewer of Amazon Elasticsearch Service writes "Easy to use, efficient, and straightforward installation". On the other hand, the top reviewer of Elastic Search writes "Played a crucial role in enhancing our cybersecurity efforts ". Amazon Elasticsearch Service is most compared with Amazon Athena, Amazon Kendra and Amazon AWS CloudSearch, whereas Elastic Search is most compared with Milvus, Faiss, Azure Search, Amazon Kendra and Exalead. See our Amazon Elasticsearch Service vs. Elastic Search report.
See our list of best Search as a Service vendors.
We monitor all Search as a Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.