no implicit conversion of nil into String about fluent-plugin-aws-elasticsearch-service HOT 5 CLOSED

And the only record of this error I can find here is on this comment and then @mzahidriaz reports he was successful with this plugin, so I think I'm close!

@mzahidriaz Is there any chance you could share (roughly) your config (either here or in #2) so we can understand the differences?

from fluent-plugin-aws-elasticsearch-service.

@jdrydn I'd love to share my config. But unfortunately I won't have those configuration with me. I started out to use this plugin to push the fluent logs directly to amazon elasticsearch service, but then we decided to use our own backup instance to store logs and push month old logs to S3.

Try adding credentials to your fluent setting.

from fluent-plugin-aws-elasticsearch-service.

Also for standard policy to AWS elasticsearch service

Created a new group and add your user to that group, then set the policy for the elasticsearch service and allow the access to your IAM group.

In this way any user to that group can push the data to elasticsearch service.

And then use your aws access key and secret in configuration

from fluent-plugin-aws-elasticsearch-service.

@mzahidriaz Thanks for getting back to me 👍 I'll definitely setup a new IAM user for this ES instance and try from there. Also fantastic advice with the policy & groups. I'm definitely going to do that today!

Does that mean this plugin will always fail whenever the access key and/or secret is omitted? Because that sounds like a bug!

At the moment I'm using the internal IPs for authentication (since the original ES plugin doesn't support IAM credentials) and I thought I could just switch to this plugin without any config changes before switching to an IAM user - guess I was wrong! 😜

from fluent-plugin-aws-elasticsearch-service.

#12 should clarify this opaque error. Closing.

from fluent-plugin-aws-elasticsearch-service.