AWS Batch now supports user-defined pod labels on Amazon EKS
Today, we are introducing a new capability for AWS Batch to provide user-defined pod labels for jobs that run on your Amazon Elastic Kubernetes Service (Amazon EKS) clusters. Labels are key-value pairs that are used to specify identifying attributes of objects that are designed to be meaningful and relevant to users. Using labels, customers can map their own organizational structures and bring better accountability, compliance, and cost visibility for their workloads.
Today, we are introducing a new capability for AWS Batch to provide user-defined pod labels for jobs that run on your Amazon Elastic Kubernetes Service (Amazon EKS) clusters. Labels are key-value pairs that are used to specify identifying attributes of objects that are designed to be meaningful and relevant to users. Using labels, customers can map their own organizational structures and bring better accountability, compliance, and cost visibility for their workloads.
This means that customers can now implement tagging best practices that provides efficient capabilities to achieve infrastructure visibility and easily troubleshoot issues. Customers can specify pod labels within the eksProperties request for their jobs in AWS Batch either when they register a job definition, or when they submit the job request. Once specified, user-defined labels can be viewed by describing the job. Overrides specified during job submission are designed to allow customers to override label values from the job definition and add new key value pairs.
Support for user-defined pod labels is now generally available in regions where AWS Batch is available. To learn more about how to specify user-defined pod labels, please visit our documentation.