Unable to add new compute environment on JobQueue on AWS Batch

Question

Hello!

I'm unable to add new compute environments on an already existing job queue, currently the queue uses a AWS EC2 managed spot environment.

When editing the queue, it doesn't show the already added compute environment, but just says: "No resources. No FARGATE compute environments available", even though it is already running jobs on a AWS EC2 managed compute environment.

Does anyone know what is going on here? It seems that it isn't recognizing any compute environments.

Answer

Dear customer,

From your initial correspondence, I understand you don't expect the warning `No FARGATE compute environments available` when you edit/create your AWS Batch job queue, because you want to add an EC2 compute environment.

Please note, AWS Batch have recently introduced Batch on EKS clusters [1], which implied slight changes on the Batch Web Console as well. Hence, there is a new choice group at the top of the screen with the **Orchestration type**, defaults to **Fargate**. However, if you don't have any Fargate compute environments available, you will receive the aforementioned warning.

All you have to do is switching the **Orchestration type** selection to **Amazon Elastic Compute Cloud (Amazon EC2)**, so you can pick on of your EC2-based compute environments to assign with your job queue.

I hope this helps you solving the issue you are facing. If you still need additional assistance, please open a Premium Support case from your account, so we can provide more tailored help after checking the resources in your account.

References:
-------
[1] https://aws.amazon.com/about-aws/whats-new/2022/10/aws-batch-supports-amazon-eks/

Unable to add new compute environment on JobQueue on AWS Batch

References:

Relevant content