Use CloudWatch Logs to monitor Amazon Batch on Amazon EKS jobs - Amazon Batch
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Use CloudWatch Logs to monitor Amazon Batch on Amazon EKS jobs

You can use Amazon CloudWatch Logs to monitor, store, and view all your log files in one location. Using CloudWatch Logs, you can search, filter, and analyze log data from multiple sources.

You can download an Amazon for Fluent Bit image that includes a plugin to monitor Amazon Batch on Amazon EKS jobs in CloudWatch Logs. Fluent Bit is an open-source log processor and forwarder that's both Docker and Kubernetes compatible. We recommend that you use Fluent Bit as your log router because it's less resource intensive than Fluentd. For more information, see Using the Amazon for Fluent Bit image.


Attach the CloudWatchAgentServerPolicy policy to the Amazon Identity and Access Management policy of your worker nodes. For more information, see Verify prerequisites.

Install Amazon for Fluent Bit

For instructions on how to install Amazon for Fluent Bit and create the CloudWatch groups, see Setting up Fluent Bit or Quick Start with the CloudWatch agent and Fluent Bit.


Remember that Fluent Bit uses .5 CPU and 100 MB of memory on Amazon Batch nodes. This reduces the total available capacity for Amazon Batch jobs. Consider this when you size your jobs.

Turn on Fluent Bit for Amazon Batch nodes

To ensure the Fluent Bit logging DaemonSet runs on Amazon Batch managed nodes, modify the Fluent Bit DaemonSet tolerations:

tolerations: - key: "" operator: "Exists"