When comparing Amidb vs AWS Elasticsearch, the Slant community recommends AWS Elasticsearch for most people. In the question“What are the best hosted Elasticsearch services?” AWS Elasticsearch is ranked 7th while Amidb is ranked 9th. The most important reason people chose AWS Elasticsearch is:
The mark up is only about 130% of the raw instance cost. This makes is one of the cheapest ES hosting options.
Ranked in these QuestionsQuestion Ranking
Pros
Pro You can add expiry and notifications to Elasticsearch and Cassandra records in an unified manner
Pro Cheapest option at great quality
While it costs 1000's of dollars per month at other places for a cluster of 3, it runs around $100 @amidb, if you decide it to host it yourself. This is including hosts/bandwidth/transfer and SSD. You will save on other colud nosql databases as cassandra is included. You will also experience savings on cloud file storage costs, and much more....
Pro Offers caching of resultsets and other binaries
You can use REST apis to cache your query results and binaries. This combined with a local cache and cdn will make your applications super fast!
Pro Offers file uploads, staging and variants
You can associate files to elasticsearch or cassandra rows.
Pro End to end solution
Pro Only small markup from raw instance costs
The mark up is only about 130% of the raw instance cost. This makes is one of the cheapest ES hosting options.
Pro Easy to setup
Integrates nicely with AWS ecosystem. Basically One-click setup of ES clusters.
Pro It is a part of your AWS bill
Very simple to add it if your organization is already charged from AWS.
Cons
Con Not very popular
Con Monitoring is not good
The dashboards that you get with AWS's ES are not very useful and there's no way to add additional monitoring dashboards.
Con You are at your own
Deploy is simple, after you at your own.
Con Difficult or impossible to configure many options
There is no way to change most of the configs in your ES cluster.