3 ms·
It looks nice, certainly it would be useful to have something quick to throw up in front of an index. What initially came to mind as something I would look for
by konradb 12y ago
It looks nice, certainly it would be useful to have something quick to throw up in front of an index. What initially came to mind as something I would look for is tangential - with no security for ES, I presumably can't use this approach in anything made generally available over the internet, as I'd have to open ES up to the world? Or is there a way round this?
- YousefED 12y agoGood question. From a security perspective you definitely want to be careful exposing your cluster to the outside and perhaps build an API around it as AznHisoka suggests (especially with recent security issues in mind). However, imo this can be quite cumbersome for simply building a dashboard for internal or client-only use / prototyping. Also, a reverse-proxy limiting requests made to your cluster can also block a lot of malicious requests (e.g.: prevent unintended inserts / updates / deletes). I probably should add a warning about this to the docs, thanks!
- dergachev 12y agoI built a simple nodejs-based proxy that's meant to sit in front of a world exposed solr instance: https://github.com/dergachev/solr-security-proxy/ https://github.com/dergachev/solr-security-proxy/ Perhaps it could be adapted to the elasticsearch scenario.