og-aws icon indicating copy to clipboard operation
og-aws copied to clipboard

Cover Elasticsearch

Open jlevy opened this issue 8 years ago • 12 comments

AWS' own Elasticsearch service is growing in popularity. Discuss basics, when to manage yourself vs with AWS' managed service, etc.

jlevy avatar Sep 26 '16 19:09 jlevy

@nitingithub want to take this one?

jlevy avatar Sep 26 '16 21:09 jlevy

This would probably need some comment on how AWS is lacking behind quite a bit regarding the available ES versions and the implications to get a system running securely in a VPC

zoellner avatar Oct 11 '16 17:10 zoellner

@zoellner yeah, what I've heard too. That's exactly the sort of tip we should put in!

jlevy avatar Oct 11 '16 17:10 jlevy

PR welcome, or if you'd like to put that tip here (any links/details to add?) we can incorporate it.

jlevy avatar Oct 11 '16 17:10 jlevy

In addition to version lagging (which right now is not actually too bad, they bumped up to 2.3 I believe in July), they have scripts disabled. And there are some relatively straightforward uses that require scripts in elasticsearch, e.g. sorting an aggregation by query score is one I just ran into.

dcosson avatar Oct 12 '16 04:10 dcosson

I can help here. I think Elasticsearch Service is one of the most powerful yet unknown service...as long as I ramp up my GitHub game lol ;-)

kimschmidtsbrain avatar Oct 22 '16 05:10 kimschmidtsbrain

dorrin [8:22 AM]
I'd like to hear stories from people who switched from managed ElasticSearch to building and maintaining their own cluster

rjhintz [10:01 AM]
@dorrin Regarding: Elasticsearch. This was a recent topic on Reddit/aws. It seemed to draw some informed opinion (as opposed to "normal" Reddit.) https://www.reddit.com/r/aws/comments/55dpn6/elasticsearch_on_aws_managed_or_roll_your_own/

jlevy avatar Nov 04 '16 17:11 jlevy

Price can also be a factor. ElasticSearch service's instances are more expensive than regular EC2 instances.

DorrinPk avatar Nov 04 '16 17:11 DorrinPk

Piping in from the field here. AWS ES does not allow use of the /_cluster/state/metadata endpoint. This causes problems with supporting tools, like Elasticsearch Curator.

See https://github.com/elastic/curator/issues/717

untergeek avatar Nov 05 '16 02:11 untergeek

Troubleshooting the ES service is also a problem. You can't see the instances behind the ES cluster so if you can't fix an issue by adding more memory or storage then you should contact support.

DorrinPk avatar Nov 30 '16 19:11 DorrinPk

AWS has a list of ES service limits as well : http://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/aes-limits.html Mainly no scripting, plugins, heap size limit, max instance count.

DorrinPk avatar Nov 30 '16 19:11 DorrinPk

Another major security gotcha to list: http://www.zdnet.com/article/first-came-mass-mongodb-ransacking-now-copycat-ransoms-hit-elasticsearch/

jlevy avatar Jan 20 '17 22:01 jlevy