AWS.Batch (aws-elixir v0.7.0) View Source

AWS Batch enables you to run batch computing workloads on the AWS Cloud.

Batch computing is a common way for developers, scientists, and engineers to access large amounts of compute resources, and AWS Batch removes the undifferentiated heavy lifting of configuring and managing the required infrastructure. AWS Batch will be familiar to users of traditional batch computing software. This service can efficiently provision resources in response to jobs submitted in order to eliminate capacity constraints, reduce compute costs, and deliver results quickly.

As a fully managed service, AWS Batch enables developers, scientists, and engineers to run batch computing workloads of any scale. AWS Batch automatically provisions compute resources and optimizes the workload distribution based on the quantity and scale of the workloads. With AWS Batch, there is no need to install or manage batch computing software, which allows you to focus on analyzing results and solving problems. AWS Batch reduces operational complexities, saves time, and reduces costs, which makes it easy for developers, scientists, and engineers to run their batch jobs in the AWS Cloud.

Link to this section Summary

Functions

Cancels a job in an AWS Batch job queue.

Creates an AWS Batch compute environment.

Creates an AWS Batch job queue.

Deletes an AWS Batch compute environment.

Deletes the specified job queue.

Deregisters an AWS Batch job definition.

Describes one or more of your compute environments.

Describes a list of job definitions.

Describes one or more of your job queues.

Describes a list of AWS Batch jobs.

Returns a list of AWS Batch jobs.

List the tags for an AWS Batch resource.

Registers an AWS Batch job definition.

Submits an AWS Batch job from a job definition.

Associates the specified tags to a resource with the specified resourceArn.

Terminates a job in a job queue.

Deletes specified tags from an AWS Batch resource.

Updates an AWS Batch compute environment.

Link to this section Functions

Link to this function

cancel_job(client, input, options \\ [])

View Source

Cancels a job in an AWS Batch job queue.

Jobs that are in the SUBMITTED, PENDING, or RUNNABLE state are cancelled. Jobs that have progressed to STARTING or RUNNING are not cancelled (but the API operation still succeeds, even if no job is cancelled); these jobs must be terminated with the TerminateJob operation.

Link to this function

create_compute_environment(client, input, options \\ [])

View Source

Creates an AWS Batch compute environment.

You can create MANAGED or UNMANAGED compute environments.

In a managed compute environment, AWS Batch manages the capacity and instance types of the compute resources within the environment. This is based on the compute resource specification that you define or the launch template that you specify when you create the compute environment. You can choose to use Amazon EC2 On-Demand Instances or Spot Instances in your managed compute environment. You can optionally set a maximum price so that Spot Instances only launch when the Spot Instance price is below a specified percentage of the On-Demand price.

Multi-node parallel jobs are not supported on Spot Instances.

In an unmanaged compute environment, you can manage your own compute resources. This provides more compute resource configuration options, such as using a custom AMI, but you must ensure that your AMI meets the Amazon ECS container instance AMI specification. For more information, see Container Instance AMIs in the Amazon Elastic Container Service Developer Guide. After you have created your unmanaged compute environment, you can use the DescribeComputeEnvironments operation to find the Amazon ECS cluster that is associated with it. Then, manually launch your container instances into that Amazon ECS cluster. For more information, see Launching an Amazon ECS Container Instance in the Amazon Elastic Container Service Developer Guide.

AWS Batch does not upgrade the AMIs in a compute environment after it is created (for example, when a newer version of the Amazon ECS-optimized AMI is available). You are responsible for the management of the guest operating system (including updates and security patches) and any additional application software or utilities that you install on the compute resources. To use a new AMI for your AWS Batch jobs:

Create a new compute environment with the new AMI.

Add the compute environment to an existing job queue.

Remove the old compute environment from your job queue.

Delete the old compute environment.

Link to this function

create_job_queue(client, input, options \\ [])

View Source

Creates an AWS Batch job queue.

When you create a job queue, you associate one or more compute environments to the queue and assign an order of preference for the compute environments.

You also set a priority to the job queue that determines the order in which the AWS Batch scheduler places jobs onto its associated compute environments. For example, if a compute environment is associated with more than one job queue, the job queue with a higher priority is given preference for scheduling jobs to that compute environment.

Link to this function

delete_compute_environment(client, input, options \\ [])

View Source

Deletes an AWS Batch compute environment.

Before you can delete a compute environment, you must set its state to DISABLED with the UpdateComputeEnvironment API operation and disassociate it from any job queues with the UpdateJobQueue API operation.

Link to this function

delete_job_queue(client, input, options \\ [])

View Source

Deletes the specified job queue.

You must first disable submissions for a queue with the UpdateJobQueue operation. All jobs in the queue are terminated when you delete a job queue.

It is not necessary to disassociate compute environments from a queue before submitting a DeleteJobQueue request.

Link to this function

deregister_job_definition(client, input, options \\ [])

View Source

Deregisters an AWS Batch job definition.

Job definitions will be permanently deleted after 180 days.

Link to this function

describe_compute_environments(client, input, options \\ [])

View Source

Describes one or more of your compute environments.

If you are using an unmanaged compute environment, you can use the DescribeComputeEnvironment operation to determine the ecsClusterArn that you should launch your Amazon ECS container instances into.

Link to this function

describe_job_definitions(client, input, options \\ [])

View Source

Describes a list of job definitions.

You can specify a status (such as ACTIVE) to only return job definitions that match that status.

Link to this function

describe_job_queues(client, input, options \\ [])

View Source

Describes one or more of your job queues.

Link to this function

describe_jobs(client, input, options \\ [])

View Source

Describes a list of AWS Batch jobs.

Link to this function

list_jobs(client, input, options \\ [])

View Source

Returns a list of AWS Batch jobs.

You must specify only one of the following:

  • a job queue ID to return a list of jobs in that job queue

  • a multi-node parallel job ID to return a list of that job's nodes

  • an array job ID to return a list of that job's children

You can filter the results by job status with the jobStatus parameter. If you do not specify a status, only RUNNING jobs are returned.

Link to this function

list_tags_for_resource(client, resource_arn, options \\ [])

View Source

List the tags for an AWS Batch resource.

AWS Batch resources that support tags are compute environments, jobs, job definitions, and job queues. ARNs for child jobs of array and multi-node parallel (MNP) jobs are not supported.

Link to this function

register_job_definition(client, input, options \\ [])

View Source

Registers an AWS Batch job definition.

Link to this function

submit_job(client, input, options \\ [])

View Source

Submits an AWS Batch job from a job definition.

Parameters specified during SubmitJob override parameters defined in the job definition.

Link to this function

tag_resource(client, resource_arn, input, options \\ [])

View Source

Associates the specified tags to a resource with the specified resourceArn.

If existing tags on a resource are not specified in the request parameters, they are not changed. When a resource is deleted, the tags associated with that resource are deleted as well. AWS Batch resources that support tags are compute environments, jobs, job definitions, and job queues. ARNs for child jobs of array and multi-node parallel (MNP) jobs are not supported.

Link to this function

terminate_job(client, input, options \\ [])

View Source

Terminates a job in a job queue.

Jobs that are in the STARTING or RUNNING state are terminated, which causes them to transition to FAILED. Jobs that have not progressed to the STARTING state are cancelled.

Link to this function

untag_resource(client, resource_arn, input, options \\ [])

View Source

Deletes specified tags from an AWS Batch resource.

Link to this function

update_compute_environment(client, input, options \\ [])

View Source

Updates an AWS Batch compute environment.

Link to this function

update_job_queue(client, input, options \\ [])

View Source

Updates a job queue.