beatcracker / rancher-graylog Goto Github PK

I think the port of the Mongo database should not be open to the public for security reasons. It is still accessible by other Rancher services.

When deploying the stack in our Rancher environment, the log of the graylog container always prints:

2.8.2017 02:01:512017-08-02 00:01:51,542 ERROR: org.graylog2.indexer.cluster.Cluster - Couldn't read cluster health for indices [graylog_*] (Could not connect to http://127.0.0.1:9200)

It seems to be wrong to contact 127.0.0.1, right should be mongo:9200 but I didn't find the place to configure the address.

I host a server in Germany and was notified by the German Federal Office for Information Security (BSI) of the following;

Elasticsearch is a popular search engine based on Apache Lucene,
often used with web applications.

If an Elasticsearch server is openly accessible from the Internet
and not protected by any forms of authentification, anyone who can
connect to the server has unrestricted access to the data stored
with it. This allows attackers to modify or delete any data or
potentially steal sensitive information. In addition, prior to
versions 1.2.x an attacker can use dynamic scripting to perform
arbitrary code execution on the machine that Elasticsearch is
hosted on.

Can we add authentication & internal NW constraints to the compose file?
I might have time to submit a PR later today