Open andrewkwok2022 opened 2 years ago
Finally got the CloudWatch Log Events after creating VPC Endpoints for com.amazonaws.us-west-2.logs, but still want to know how to configure "INPUT" in Fargate.
We can not create section INPUT on AWS EKS Fargate. AWS only ACCEPT FILTER, PARSER, & OUTPUT sections as mentioned in this https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html
Describe the question/issue
I tried to enable logging for my EKS Fargate but in vain. I would like to know what I have done wrong for the configuration:
I have followed the these 2 guides (https://aws.amazon.com/blogs/containers/fluent-bit-for-amazon-eks-on-aws-fargate-is-here/ https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html ) to set up the namespace, configmap and iam policy. When I “
kubectl describe
” the pod, I can see “Logging: LoggingEnabled
” in Annotations and “Successfully enabled logging for pod” from “fargate-scheduler
” in Events. However, after applying all the required config and yaml files, I have not seen anything related to my EKS cluster in CloudWatch Logs.Here is my logging-config.yaml
Apart from that, as the server logs of my Jboss application are stored in the directory /usr/local/jboss/standalone/log, and I figure out that if nodegroup is in used, Fluent Bit provides input config to specify the location to “save” the log (ref: https://aws.amazon.com/blogs/containers/capturing-logs-at-scale-with-fluent-bit-and-amazon-eks/ )
Example:
How to do the same thing in EKS Fargate, so that I can collect all the log messages from my application inside a specific folder?
Thank you!
Cluster Details
EKS Fargate