Exactly. It's ultimately up to your own security requirements. We run separate as we have a web server that runs a few instances of kibana and a few other things, which allows finer grained access controls.
Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [email protected] web: www.campaignmonitor.com On 20 August 2014 23:33, Andrew Ruslander <[email protected]> wrote: > Thanks for your answer, Mark. What would you recommend as the most secure > approach? I'm just trying to formulate some sort of argument, however > minimal, of Kibana on an ES node or not. I am assuming that *not *having > Kibana on the ES node is the more secure setup, as if it were, users would > be accessing the cluster directly, versus some external box that > communicates with the ES cluster under controlled ports. > > - Andrew > > On Tuesday, August 19, 2014 6:11:12 PM UTC-4, Mark Walkom wrote: >> >> Doesn't really matter as Kibana itself uses very little resources, the >> queries are still going to your cluster. You do need to consider security >> etc though. >> >> >> You can even run it as an elasticsearch "plugin" if you put it in the >> plugins directory and the access it via $host:9200/_plugin/kibana. >> >> Regards, >> Mark Walkom >> >> Infrastructure Engineer >> Campaign Monitor >> email: [email protected] >> web: www.campaignmonitor.com >> >> >> On 20 August 2014 05:01, Andrew Ruslander <[email protected]> wrote: >> >>> I couldn't find any official documentation or best practices, though it >>> seems implied in the Kibana installation instructions, but is there any >>> word on whether or not Kibana3 should or should not live on a node in the >>> ES cluster? Thoughts on pros and cons of doing so? >>> >>> Pro - one less box to stand up >>> Con - performance impacts on the ES node who drew the short straw? >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "elasticsearch" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ >>> msgid/elasticsearch/9d8c5951-8773-4f2f-ac0f-6b54becd6a96% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/elasticsearch/9d8c5951-8773-4f2f-ac0f-6b54becd6a96%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/9dceeb30-3f76-46c8-ac83-e8f3fbeddf7a%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/9dceeb30-3f76-46c8-ac83-e8f3fbeddf7a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624bNb5Ykx%3DnC6JJQCd%3DCjJ09f2QbU8aGCtAA6CpQFaGhcg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
