Wondering how to create an AWS Batch Unmanaged Compute Environment using EC2 resources? We can help you.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see the steps our engineers employ to perform the same.

AWS Batch Unmanaged Compute Environment

1. Initially, we open the AWS Batch console

2. Then we select the Region to use from the navigation bar.

3. In the navigation pane, we select Compute environments >> Create environment.

4. We can select the type as Unmanaged.

5. For the name, we specify a unique name. It can be up to 128 characters in length, can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_). Make sure to make it strong.

6. Then for the Service role, we select a Batch service-linked role. It allows the AWS Batch service to make calls to the required AWS API operations on our behalf.

7. Ensure to select the option, Enable Compute Environment so that the compute environment can accept jobs from the AWS Batch job scheduler.

Eventually, we select, Create to finish.

8. In addition, if necessary, we can retrieve the Amazon ECS cluster ARN for the associated cluster.

To get the Amazon ECS cluster ARN for a compute environment, we run:

aws batch describe-compute-environments --compute-environments unmanagedCE --query "computeEnvironments[].ecsClusterArn"

9. Similarly, if necessary, we can launch container instances into the associated Amazon ECS cluster.

When we do so, we need to specify the Amazon ECS cluster ARN that the resources should register with the Amazon EC2 user data.

For instance, we replace ecsClusterArn with the cluster ARN we obtained in the previous command.

#!/bin/bash
echo "ECS_CLUSTER=ecsClusterArn" >> /etc/ecs/ecs.config

The unmanaged compute environment doesn’t have any compute resources until we launch them manually.

[Need further assistance? We are here to assist you]

Conclusion

In short, we saw how our Support Techs perform the AWS query for our customers.