Amazon EKS adds built-in logging support for AWS Fargate
Amazon Elastic Kubernetes Service (Amazon EKS) now allows you to forward container logs from pods running on AWS Fargate to AWS services for log storage and analytics including Amazon Cloudwatch, Amazon Elasticsearch, Amazon Kinesis Data Firehose, and Amazon Kinesis Streams.
Amazon Elastic Kubernetes Service (Amazon EKS) now allows you to forward container logs from pods running on AWS Fargate to AWS services for log storage and analytics including Amazon Cloudwatch, Amazon Elasticsearch, Amazon Kinesis Data Firehose, and Amazon Kinesis Streams.
Amazon EKS with AWS Fargate now includes a built-in log router, so there are no sidecars to install or maintain. You simply define where you want to send your data using a Kubernetes ConfigMap, and logs are routed to a destination of your choice. Under the hood, EKS uses a version of Fluent Bit which is managed by AWS and upstream conformant. This means you get a consistent interface while configuring logging on your EKS clusters across compute types whether your pods run on Amazon EC2 or AWS Fargate.
To get started visit EKS documentation or read more in the blog post.