Troubleshooting AWS Batch

You might need to troubleshoot issues that are related to your compute environments, job queues, job definitions, or jobs. This chapter describes how to troubleshoot and resolve such issues in your AWS Batch environment.

AWS Batch uses IAM policies, roles, and permissions, and runs on Amazon EC2, Amazon ECS, AWS Fargate, and Amazon Elastic Kubernetes Service infrastructure. To troubleshoot issues that are related to these services, see the following:

• Troubleshooting IAM in the IAM User Guide

• Amazon ECS troubleshooting in the Amazon Elastic Container Service Developer Guide

• Amazon EKS troubleshooting in the Amazon EKS User Guide

• Troubleshoot EC2 instances in the Amazon EC2 User Guide

Contents

• AWS Batch

  • INVALID compute environment

    • Incorrect role name or ARN

    • Repair an INVALID compute environment

  • Jobs stuck in a RUNNABLE status

  • Spot Instances not tagged on creation

  • Spot Instances not scaling down

    • Attach AmazonEC2SpotFleetTaggingRole managed policy to your Spot Fleet role in the AWS Management Console

    • Attach AmazonEC2SpotFleetTaggingRole managed policy to your Spot Fleet role with the AWS CLI

  • Can't retrieve Secrets Manager secrets

  • Can't override job definition resource requirements

  • Error message when you update the desiredvCpus setting

• AWS Batch on Amazon EKS

  • INVALID compute environment

    • Unsupported Kubernetes version

    • Instance profile doesn't exist

    • Invalid Kubernetes namespace

    • Deleted compute environment

    • Nodes don't join the Amazon EKS cluster

  • AWS Batch on Amazon EKS job is stuck in RUNNABLE status

  • AWS Batch on Amazon EKS job is stuck in STARTING status

    • Scenario: Persisted Volume Claim Attach or Mount Failure

  • Verify that the aws-auth ConfigMap is configured correctly

  • RBAC permissions or bindings aren't configured properly