Require farady_middleware in new install about fluent-plugin-aws-elasticsearch-service HOT 7 CLOSED

I've got the same issue here. Any suggestions from people? It seems like previously Faraday Middleware was not compatible with Faraday 0.9 but that looks like it was fixed ?

I'm not a ruby dev so I'm not particularly familiar with where to go from here, so any suggestions would be helpful! :)

from fluent-plugin-aws-elasticsearch-service.

I've found the source of the issue and have a fix! It seems that Ruby was not installing the gems in a place that the td-agent user has access to and therefore could not require the faraday_middleware gem. To fix this, first uninstall faraday_middleware with

sudo gem uninstall faraday_middleware

then reinstall it under the td-agent user using the following command:

sudo -u td-agent /usr/sbin/td-agent-gem install faraday_middleware

I also then stumbled across an issue whereby the plugin was unable to connect to our AWS Elasticsearch endpoint when we were just specifying the domain. To fix this, you must specify the protocol and port. For example, our endpoint config now looks like this:

<endpoint>
   url "http://xxx.ap-southeast-2.es.amazonaws.com:80"
   region "ap-southeast-2"
   access_key_id "xxx"
   secret_access_key "xxx"
</endpoint>

I hope this fixes any issues anyone might have!
cc @BoGs

from fluent-plugin-aws-elasticsearch-service.

Hi @BoGs.

I'm sorry, "v0.0. *" is bug-ridden.
Please try using the "v0.1.0".

thanks!

from fluent-plugin-aws-elasticsearch-service.

sorry...

I was mistaken dependencies.
I removed the "require 'faraday_middleware'".

Please try using the "v0.1.1".

thanks

from fluent-plugin-aws-elasticsearch-service.

thx for fixing that lines, I've removed gem install procedure of my docker container.

from fluent-plugin-aws-elasticsearch-service.

Thanks for the new version - it is working now. Thanks for the quick response.

from fluent-plugin-aws-elasticsearch-service.

Thank you for the reply!

from fluent-plugin-aws-elasticsearch-service.