You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I setup an Elasticsearch + Kibana for my cluster and I choose public access for first time use and testing. I am trying to install fluentd in order to centralize my application logs. I researched a lot of other methods like Clock-watch and fluent-bit but I went with fluentd as it looked very simple. My issue is that when i deploy my fluent yaml file it is not connecting to Elasticsearch thus not creating an index on Kibana. Note that I am using fine-grained access control that is why I have a master user and password. In addition, I read some articles that state that I need to include aws-es-proxy but other articles do not even mention it, Please anyone give suggestions which is the best practice. My goal is to simply get my API application Pod logs to Kibana.
Kindly see the logs after using different fluentd images to resolve this issue:
Duplicated of #244.
AWS Elasticsearch Service requests to use AWS Sign V4 like as other AWS managed services.
This is not issue, just a limitation of AWS Elasticsearch Service.
Closing.
Kindly note that while troubleshooting my issue I did provide the access key in my env but was receiving the same errors. Thank you for the reference I will do more research there to fix my issue.
fluent-plugin-elasticsearch does not handle AWS access key and its secret.
These modified lines are unused.
Instead, you can use dtan4/aws-sign-proxy for proxy request into AWS Elasticsearch Service.
It also can refer as quay.io/dtan4/aws-sign-proxy:latest on Docker repo/release tag.
I setup an Elasticsearch + Kibana for my cluster and I choose public access for first time use and testing. I am trying to install fluentd in order to centralize my application logs. I researched a lot of other methods like Clock-watch and fluent-bit but I went with fluentd as it looked very simple. My issue is that when i deploy my fluent yaml file it is not connecting to Elasticsearch thus not creating an index on Kibana. Note that I am using fine-grained access control that is why I have a master user and password. In addition, I read some articles that state that I need to include aws-es-proxy but other articles do not even mention it, Please anyone give suggestions which is the best practice. My goal is to simply get my API application Pod logs to Kibana.
Kindly see the logs after using different fluentd images to resolve this issue:
image: quay.io/fluent/fluentd-kubernetes-daemonset
image: fluent/fluentd:stable
fluentd-deployment.yaml
The text was updated successfully, but these errors were encountered: