Closed damvinod closed 1 year ago
Hi,
Looking at the issue it seems to me that the problem is more on the plugin itself than the Bitnami packaging of fluentd. Did you check with the plugin developers?
Thanks @javsalgar.
The issue was resolved after configuring the IAM role as part of fluend configuration which is specific to the pluginfluent-plugin-aws-elasticsearch-service
based on the below documentation.
https://github.com/atomita/fluent-plugin-aws-elasticsearch-service#eks
Name and Version
bitnami/fluentd-5.0.18
What steps will reproduce the bug?
We have a use-case to use fluend as aggregator to push logs to Cloudwatch. We are enabling IRSA for the fluentd-aggregator pod so that it has necessary permission to pipe logs to Cloudwatch.
fluentd image is build with below config.
DockerFile
Gemfile
Are you using any custom parameters or values?
No response
What is the expected behavior?
fluentd-aggregator pod should be able to pipe logs to Cloudwatch.
What do you see instead?
Additional information
Verified the below: