What users are saying about
Top Rated
154 Ratings
23 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.3 out of 100
Top Rated
154 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.7 out of 100

Likelihood to Recommend

Amazon CloudSearch

Amazon Cloudsearch can be suitable for some queries that require fast data. For example, in our case, we used CloudSearch, in a tool called Global Search. That will search everything like names, emails and a lot of stuff in our application. If you want fast data and you have a simple query, Global Search isn't appropriate for you.
Anonymous | TrustRadius Reviewer

Elasticsearch

Elasticsearch's best use case is when you want to store loosely-structured data and be able to search for it near-instantly. And you want to do that in a highly tolerant distributed system. My company doesn't use it this way but I've heard of other companies using ES to store system logs. Another company uses it to store giant store-catalogs.
Anonymous | TrustRadius Reviewer

Pros

Amazon CloudSearch

  • Really fast queries
  • Good Reporting
  • Reduce the cost of the server
Anonymous | TrustRadius Reviewer

Elasticsearch

  • Super-fast search on millions of documents. We've got over 2 billion documents in our index and the retrieve speeds are still in the < 1-second range.
  • Analytics on top of your search. If you organize your data appropriately, Elasticsearch can serve as a distributed OLAP system
  • Elasticsearch is great for geographic data as well, including searching and filtering with geojson, and a variety of geospatial algorithms.
Anatoly Geyfman | TrustRadius Reviewer

Cons

Amazon CloudSearch

  • Can take some time to implement
  • The initial configuration can be tricky
  • Takes some time to update the values
Anonymous | TrustRadius Reviewer

Elasticsearch

  • Setting Java memory thresholds can be a pain for those not accustomed to things like Eden Space & Old Generation which can lead to over allocation, or more likely, under allocation. Apache Solr had a similar issue. It would be nice if the program would take an extra step and dogfood it's own advice by analyzing the system & processes to return a solid recommendation for that configuration. The proper configuration information is outlined in the documentation, it would be nice if that was automated.
  • The only health check that ElasticSearch reports back is a "red" status without any real solid information about what is going on, though its usually memory thresholds or disk I/O. I am currently on ElasticSearch 1.5 so that may have changed for newer versions. When the status goes "red", I as the administrator of the software, feel like I lose control of whats going on which should rarely happen. Something more verbose would eliminate that.
  • This is more of a critique of the ElasticStack in general. The whole top to bottom stack is starting to get feature creep with things that are better suited in other software and increasing the barrier for entry for people to get started with setting up a robust logging infrastructure. ElasticSearch as a storage search engine, is pretty streamlined, but I can see that the tools that comprise the ELK Stack are going to require a certification with constant study at some point. During major release for Logstash a while back, it literally took a month to learn a new language because Elastic completely changed the syntax. For a medium sized organization of only a couple of admins, that is a pretty high bar where time is money. They really should work on refining/automating the tools & search engine they have, instead of shoehorning/changing things on to an already rock solid foundation.
Colby Shores | TrustRadius Reviewer

Likelihood to Renew

Amazon CloudSearch

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 10.0
Based on 1 answer
We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.
Aaron Gussman | TrustRadius Reviewer

Usability

Amazon CloudSearch

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 10.0
Based on 1 answer
To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching.If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.
Anonymous | TrustRadius Reviewer

Support Rating

Amazon CloudSearch

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 7.5
Based on 12 answers
We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.
Anonymous | TrustRadius Reviewer

Implementation Rating

Amazon CloudSearch

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 9.0
Based on 1 answer
Do not mix data and master roles. Dedicate at least 3 nodes just for Master
Anonymous | TrustRadius Reviewer

Alternatives Considered

Amazon CloudSearch

I didn't investigate the best alternatives to CloudSearch, but did help with implementing this feature in our application. But from what i tested and used - Cloudsearch is very fast to get queries. Some negative points can be the time to implement this and some configurations that can be tricky.
Anonymous | TrustRadius Reviewer

Elasticsearch

As far as we are concerned, Elasticsearch is the gold standard and we have barely evaluated any alternatives. You could consider it an alternative to a relational or NoSQL database, so in cases where those suffice, you don't need Elasticsearch. But if you want powerful text-based search capabilities across large data sets, Elasticsearch is the way to go.
Anonymous | TrustRadius Reviewer

Return on Investment

Amazon CloudSearch

  • Positive Point - Reduced the server load
  • Negative point - Not suitable for all queries
  • Negative Point - Time to implement this feature
Anonymous | TrustRadius Reviewer

Elasticsearch

  • Faster searches on our application have resulted in better usability and increased application use
  • Analytics dashboard has given our managers a better understanding of day-to-day activities
  • Being a backup data store, we need not touch SQL database while doing data dumps for local data science projects
Swastik Nath | TrustRadius Reviewer

Pricing Details

Amazon CloudSearch

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Amazon CloudSearch Editions & Modules

Additional Pricing Details

Elasticsearch

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Elasticsearch Editions & Modules

Edition
Standard$16.001
Gold$19.001
Platinum$22.001
EnterpriseContact Sales
  1. per month
Additional Pricing Details

Add comparison