DEVOPSdigest

AWS Batch for Amazon Elastic Kubernetes Service (Amazon EKS) is now available.

AWS Batch for Amazon EKS is designed for users who no longer want to shoulder the burden of configuring, fine-tuning, and managing Kubernetes clusters and pods to use with their batch processing workflows.

Furthermore, there is no charge for this service. Users only pay for the resources that their batch jobs launch.

AWS Batch for Amazon EKS offers a fully managed service to run batch workloads using clusters hosted on Amazon Elastic Compute Cloud (Amazon EC2) with no need to install and manage complex, custom batch solutions to address the differences highlighted earlier. AWS Batch provides a scheduler that controls and runs high-volume batch jobs, together with an orchestration component that evaluates when, where, and how to place jobs submitted to a queue. There’s no need for the user to coordinate any of this work­, simply submit a job request into the queue.

Job queueing, dependency tracking, retries, prioritization, compute resource provisioning for Amazon Elastic Compute Cloud (EC2) and Amazon Elastic Compute Cloud (EC2) Spot, and pod submission are all handled using a serverless queue. As a managed service, AWS Batch for Amazon EKS enables users to reduce their operational and management overhead and focus instead on the business requirements. It provides integration with other services such as AWS Identity and Access Management (IAM), Amazon EventBridge, and AWS Step Functions and allows the user to take advantage of other partners and tools in the Kubernetes ecosystem.

When running batch jobs on Amazon EKS clusters, AWS Batch is the main entry point to submit workload requests. Based on the queued jobs, AWS Batch then launches worker nodes in the users' cluster to process the jobs. These nodes are kept separate in a distinct namespace from other node groups in Amazon EKS. Similarly, nodes in other pods are isolated from those used with AWS Batch.