AWS Batch Now Supports EKS Access Entry Authentication, Beyond the aws-auth ConfigMap!

Hi, it's Shii-chan! Today we have an authentication update for AWS Batch on EKS!

AWS What's New aws.amazon.com

What was announced?

According to AWS What's New, AWS Batch now supports Amazon EKS access entry authentication for compute environments.

The story so far

EKS access entries are an API-driven way to grant IAM principals access to Kubernetes clusters, complementing the existing aws-auth ConfigMap.

Until now, AWS Batch could not authenticate through this mechanism.

What changes

AWS Batch can authenticate to your cluster through access entries, which simplifies cluster setup and authentication lifecycle management.

It's good news if you'd rather manage access through APIs than edit a ConfigMap!

Dive Deep

To get started, use the CreateComputeEnvironment or UpdateComputeEnvironment APIs to set accessEntry.desiredState to ENABLED on all AWS Batch compute environments targeting your cluster.

• AWS Batch creates one access entry per cluster
• It associates the AWSBatchClusterPolicy with that access entry
• You can configure it through the AWS CLI, AWS SDKs, or the AWS Management Console
• It is supported in all AWS Regions where AWS Batch is available

For details, see "Amazon EKS access entry authentication" in the AWS Batch User Guide.

Wrap-up

• AWS Batch supports EKS access entry authentication
• Enable it by setting accessEntry.desiredState to ENABLED
• One access entry is created per cluster with AWSBatchClusterPolicy attached

This is for teams running AWS Batch on EKS who want tidier, API-driven authentication!