Verify that the aws-auth ConfigMap is configured correctly
For Amazon EKS access entry authentication instead of the aws-auth ConfigMap,
see Amazon EKS access entry authentication.
Once an Amazon Batch-managed access entry is created for the Amazon Batch service-linked role on a cluster
(accessEntry.status=ACTIVE), it takes precedence over the aws-auth ConfigMap configuration for the role.
The ConfigMap entries for the Amazon Batch service-linked role are unused, and Amazon Batch authenticates using the access entry instead.
To return to ConfigMap authentication, you must set desiredState=DISABLED on all compute environments
that target the cluster to remove the Amazon Batch-managed access entry.
To verify that the aws-auth
ConfigMap is configured correctly:
-
Retrieve the mapped roles in the
aws-authConfigMap.$kubectl get configmap -n kube-system aws-auth -o yaml -
Verify that the
roleARNis configured as follows.rolearn: arn:aws-cn:iam::aws_account_number:role/AWSServiceRoleForBatchNoteThe path
aws-service-role/batch.amazonaws.com/has been removed from the ARN of the service-linked role. This is because of an issue with theaws-authconfiguration map. For more information, see Roles with paths do not work when the path is included in their ARN in the aws-authconfigmap. NoteYou can also review the Amazon EKS control plane logs. For more information, see Amazon EKS control plane logging in the Amazon EKS User Guide.
To resolve an issue where a job is stuck in a RUNNABLE status, we recommend
that you use kubectl to re-apply the manifest. For more information, see Step 2: Prepare your Amazon EKS cluster for Amazon Batch. Or, you can
use kubectl to manually edit the aws-auth
ConfigMap. For more information, see Enabling IAM user and role access to your
cluster in the Amazon EKS User Guide.