Support cloud-aws Elasticsearch Plugin Within Graylog ES Client about graylog2-images HOT 4 CLOSED

I think this is a general problem with Docker on EC2. The ES plugin is making use of the EC2 metadata to publish cluster informations. But the metadata is not accessable inside of a container. There are projects like this you could try: https://github.com/dump247/docker-ec2-metadata
Or you go with the native EC2 instance of the Graylog appliance: https://github.com/Graylog2/graylog2-images/tree/master/aws

from graylog2-images.

It looks like graylog-server is using the 1.3.2 version of the Elasticsearch client (https://github.com/Graylog2/graylog2-server/blob/1.0.2/pom.xml#L223), but the omnibus install is using 1.4.5, hence the exceptions about not finding an injectable constructor when using the Elasticsearch cloud-aws plugin (the 1.3.2 client works with 1.4.5 ES server, but ES plugins are more strict with regards to version requirements).

from graylog2-images.

Yeah, the linked client library is always a little bit behind. Depends on when the server binary was compiled. But of cause we try to run a recent version of ES. Did you install the plugin for the Graylog-Server as well?

from graylog2-images.

I was successful in using the elasticsearch/elasticsearch-cloud-aws/2.4.1 version of the cloud-aws plugin, but with a Docker container built from a new Dockerfile that installed components (graylog-server, graylog-web, elasticsearch, mongodb) individually instead of using the omnibus deb package.

from graylog2-images.