Does this project have an active maintainer? about fluent-plugin-aws-elasticsearch-service HOT 11 CLOSED

@repeatedly - what would you think of extending uken/fluent-plugin-elasticsearch to support Amazon signing? Amazon signing seems to be the biggest (only?) feature lacking in uken/fluent-plugin-elasticsearch?

from fluent-plugin-aws-elasticsearch-service.

If someone wants to merge this feature into ES plugin, new active maintainer for AWS ES parts is needed.
But I think forking this project is better. ES can focus on ES feature, not transport.

from fluent-plugin-aws-elasticsearch-service.

How about using the Amazon Kinesis Firehose instead?
I have stopped using this plugin and started using it and https://github.com/awslabs/aws-fluent-plugin-kinesis because I had trouble as #25 and it seems there is no future to resolve it.

However, the Firehose outputs to the ES domains only same region, then this idea can apply in us-east-1, us-west-2, eu-west-1 regions :(
Although I always use ap-northeast-1, I created ES domains in us-west-2.

from fluent-plugin-aws-elasticsearch-service.

I am also running into issues using this plugin. Any good recommendation as an alternative? I looked at putting the logs into cloudwatch and stream to ES. But this is a very costly approach.

from fluent-plugin-aws-elasticsearch-service.

There are 2 approaches:

• someone becomes new maintainer if @atomita is ok
  • option is fluent-plugins-nursery for temporal place
• fork plugin (I don't want to do)

from fluent-plugin-aws-elasticsearch-service.

This plugin is small enough that rolling functionality into fluent-plugin-elasticsearch makes a lot of sense. On the other hand that plugin is not well-maintained either these days.

from fluent-plugin-aws-elasticsearch-service.

I'm not sure because I'm not a maintainer of elasticsearch plugin.
If the elasticsearch maintainers and contributors are okay, it is good idea.

from fluent-plugin-aws-elasticsearch-service.

On the other hand that plugin is not well-maintained either these days.

@yissachar - yeah, I thought this was being resolved in uken/fluent-plugin-elasticsearch#240, in particular that @repeatedly was being given access. I just re-read that PR now and it still seems unresolved. This is a real bummer because for many people, myself included, Fluentd loses a lot of value without a good well maintained Elasticsearch plugin.

from fluent-plugin-aws-elasticsearch-service.

@cosmo0920 are you interested to merge this plugins functionality in to uken/fluent-plugin-elasticsearch ?
@atomita are you good with this and let this plugin die?

from fluent-plugin-aws-elasticsearch-service.

No. I'm not familiar with AWS Elasticsearch Service.

from fluent-plugin-aws-elasticsearch-service.

I'd became an active maintainer. (But still @atomita wants to publish this plugin by his own.)
So, we can close this issue.

from fluent-plugin-aws-elasticsearch-service.