Fluent Bit supports Amazon Elasticsearch Service as a destination to route container logs
Customers using container services including Amazon Elastic Container Service (ECS), Amazon Elastic Kubernetes Services (EKS), or self-managed Kubernetes can now send their container logs to Amazon Elasticsearch Service using the Fluent Bit log router. Fluent Bit allows customers to route container logs to various AWS and partner monitoring solutions including CloudWatch, Amazon Kinesis, Datadog, Splunk, and now Amazon Elasticsearch Service.
Customers using container services including Amazon Elastic Container Service (ECS), Amazon Elastic Kubernetes Services (EKS), or self-managed Kubernetes can now send their container logs to Amazon Elasticsearch Service using the Fluent Bit log router. Fluent Bit allows customers to route container logs to various AWS and partner monitoring solutions including CloudWatch, Amazon Kinesis, Datadog, Splunk, and now Amazon Elasticsearch Service.
ECS customers can use the FireLens interface in their ECS task definition to send logs to Amazon Elasticsearch Service. FireLens configures Fluent Bit to send logs to a number of partner monitoring services. Once you deploy your task definition, it will automatically start routing logs. Customers using containers on EKS or self-managed Kubernetes can now route container logs to Amazon Elasticsearch Service by installing Fluent Bit as a DaemonSet. See a FireLens example to get started with sending logs to Amazon Elasticsearch Service here and the Fluent Bit release notes here.