Elastic Cloud runs in either AWS or GCP. You get to choose but it's just between those. Unless you mean you were using AWS's ElasticSearch service... which is known to not be all that great.
You could build ES clusters on AWS directly on EC2 and it would be cheaper than Cloud, unless what you're really looking for is that support contract.
I spent a few months of my life learning ES inside and out and would choose this option every time. One of the best tech investments I've ever made.
> You could build ES clusters on AWS directly on EC2 and it would be cheaper than Cloud, unless what you're really looking for is that support contract.
Or you are willing to trade money for dev time. Setting up and running the ES cluster on EC2 will take time and energy (source, I did it ). Whereas setting up the ES cluster on either the Elastic Search hosted service or AWS ElasticSearch is really just clicking some buttons.
However, I'm sure the right solution also depends on the amount of data you are using and the problem you are trying to solve.
I can largely agree with the last statement. The problem I find with the hosted services is that people just tend to throw data at it without really knowing anything about cluster/node/shard performance. This typically blows up in their face at some point and even though Elastic Cloud has nice sliders in place for spend-more-money, they still have to go through the rebalancing pains (if they didn't write-lock the cluster outright). That should never happen.
If you have strictly time-series data and are willing to make compromises around retention window, hosted elasticsearch is an easy conclusion. Invariably though, I find that where performance is a real concern, you have to carefully plan what data you're indexing and that requires operations knowledge around elasticsearch. At that point you almost might as well host it yourself anyway.
Also if X-Pack was something I _had_ to have, and tbh there are free alternatives for all of its good features, I would consider Elastic Cloud.
I'm even a customer of theirs on some clusters, but lackluster support and pushy upselling experiences have made me want to move out of it.
An issue I had with AWS was that even after they launched VPC ES clusters, they still hid the node IPs in the API output(I guess they patched ES?!). Our use case as a data lake meant that we had severely degraded performance with the hadoop/spark drivers than one would expect form it.
Performance is miles and above better, there’s actual security options on the clusters and there’s way more features.