%% WARNING: DO NOT EDIT, AUTO-GENERATED CODE! %% See https://github.com/aws-beam/aws-codegen for more details. %% @doc Using AWS Batch, you can run batch computing workloads on the AWS %% Cloud. %% %% Batch computing is a common means for developers, scientists, and %% engineers to access large amounts of compute resources. AWS Batch utilizes %% the advantages of this computing workload to remove the undifferentiated %% heavy lifting of configuring and managing required infrastructure, while %% also adopting a familiar batch computing software approach. Given these %% advantages, AWS Batch can help you to efficiently provision resources in %% response to jobs submitted, thus effectively helping to eliminate capacity %% constraints, reduce compute costs, and deliver your results more quickly. %% %% As a fully managed service, AWS Batch can run batch computing workloads of %% any scale. AWS Batch automatically provisions compute resources and %% optimizes workload distribution based on the quantity and scale of your %% specific workloads. With AWS Batch, there's no need to install or manage %% batch computing software. This means that you can focus your time and %% energy on analyzing results and solving your specific problems. -module(aws_batch). -export([cancel_job/2, cancel_job/3, create_compute_environment/2, create_compute_environment/3, create_job_queue/2, create_job_queue/3, delete_compute_environment/2, delete_compute_environment/3, delete_job_queue/2, delete_job_queue/3, deregister_job_definition/2, deregister_job_definition/3, describe_compute_environments/2, describe_compute_environments/3, describe_job_definitions/2, describe_job_definitions/3, describe_job_queues/2, describe_job_queues/3, describe_jobs/2, describe_jobs/3, list_jobs/2, list_jobs/3, list_tags_for_resource/2, list_tags_for_resource/4, list_tags_for_resource/5, register_job_definition/2, register_job_definition/3, submit_job/2, submit_job/3, tag_resource/3, tag_resource/4, terminate_job/2, terminate_job/3, untag_resource/3, untag_resource/4, update_compute_environment/2, update_compute_environment/3, update_job_queue/2, update_job_queue/3]). -include_lib("hackney/include/hackney_lib.hrl"). %%==================================================================== %% API %%==================================================================== %% @doc Cancels a job in an AWS Batch job queue. %% %% Jobs that are in the `SUBMITTED', `PENDING', or `RUNNABLE' state are %% canceled. Jobs that have progressed to `STARTING' or `RUNNING' are not %% canceled (but the API operation still succeeds, even if no job is %% canceled); these jobs must be terminated with the `TerminateJob' %% operation. cancel_job(Client, Input) -> cancel_job(Client, Input, []). cancel_job(Client, Input0, Options0) -> Method = post, Path = ["/v1/canceljob"], SuccessStatusCode = undefined, Options = [{send_body_as_binary, false}, {receive_body_as_binary, false} | Options0], Headers = [], Input1 = Input0, Query_ = [], Input = Input1, request(Client, Method, Path, Query_, Headers, Input, Options, SuccessStatusCode). %% @doc Creates an AWS Batch compute environment. %% %% You can create `MANAGED' or `UNMANAGED' compute environments. `MANAGED' %% compute environments can use Amazon EC2 or AWS Fargate resources. %% `UNMANAGED' compute environments can only use EC2 resources. %% %% 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 either to use EC2 On-Demand Instances and EC2 Spot Instances, or to %% use Fargate and Fargate Spot capacity in your managed compute environment. %% You can optionally set a maximum price so that Spot Instances only launch %% when the Spot Instance price is less than 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 EC2 compute %% resources and have a lot of flexibility with how you configure your %% compute resources. For example, you can use custom AMI. However, you need %% to verify 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's 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 doesn't upgrade the AMIs in a compute environment after it's %% created. For example, it doesn't update the AMIs when a newer version of %% the Amazon ECS-optimized AMI is available. Therefore, you're 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, complete these steps: %% %% Create a new compute environment with the new AMI. %% %% Add the compute environment to an existing job queue. %% %% Remove the earlier compute environment from your job queue. %% %% Delete the earlier compute environment. create_compute_environment(Client, Input) -> create_compute_environment(Client, Input, []). create_compute_environment(Client, Input0, Options0) -> Method = post, Path = ["/v1/createcomputeenvironment"], SuccessStatusCode = undefined, Options = [{send_body_as_binary, false}, {receive_body_as_binary, false} | Options0], Headers = [], Input1 = Input0, Query_ = [], Input = Input1, request(Client, Method, Path, Query_, Headers, Input, Options, SuccessStatusCode). %% @doc 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. create_job_queue(Client, Input) -> create_job_queue(Client, Input, []). create_job_queue(Client, Input0, Options0) -> Method = post, Path = ["/v1/createjobqueue"], SuccessStatusCode = undefined, Options = [{send_body_as_binary, false}, {receive_body_as_binary, false} | Options0], Headers = [], Input1 = Input0, Query_ = [], Input = Input1, request(Client, Method, Path, Query_, Headers, Input, Options, SuccessStatusCode). %% @doc 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. Compute environments that use AWS Fargate resources must %% terminate all active jobs on that compute environment before deleting the %% compute environment. If this isn't done, the compute environment will end %% up in an invalid state. delete_compute_environment(Client, Input) -> delete_compute_environment(Client, Input, []). delete_compute_environment(Client, Input0, Options0) -> Method = post, Path = ["/v1/deletecomputeenvironment"], SuccessStatusCode = undefined, Options = [{send_body_as_binary, false}, {receive_body_as_binary, false} | Options0], Headers = [], Input1 = Input0, Query_ = [], Input = Input1, request(Client, Method, Path, Query_, Headers, Input, Options, SuccessStatusCode). %% @doc Deletes the specified job queue. %% %% You must first disable submissions for a queue with the `UpdateJobQueue' %% operation. All jobs in the queue are eventually terminated when you delete %% a job queue. The jobs are terminated at a rate of about 16 jobs each %% second. %% %% It's not necessary to disassociate compute environments from a queue %% before submitting a `DeleteJobQueue' request. delete_job_queue(Client, Input) -> delete_job_queue(Client, Input, []). delete_job_queue(Client, Input0, Options0) -> Method = post, Path = ["/v1/deletejobqueue"], SuccessStatusCode = undefined, Options = [{send_body_as_binary, false}, {receive_body_as_binary, false} | Options0], Headers = [], Input1 = Input0, Query_ = [], Input = Input1, request(Client, Method, Path, Query_, Headers, Input, Options, SuccessStatusCode). %% @doc Deregisters an AWS Batch job definition. %% %% Job definitions are permanently deleted after 180 days. deregister_job_definition(Client, Input) -> deregister_job_definition(Client, Input, []). deregister_job_definition(Client, Input0, Options0) -> Method = post, Path = ["/v1/deregisterjobdefinition"], SuccessStatusCode = undefined, Options = [{send_body_as_binary, false}, {receive_body_as_binary, false} | Options0], Headers = [], Input1 = Input0, Query_ = [], Input = Input1, request(Client, Method, Path, Query_, Headers, Input, Options, SuccessStatusCode). %% @doc Describes one or more of your compute environments. %% %% If you're 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. describe_compute_environments(Client, Input) -> describe_compute_environments(Client, Input, []). describe_compute_environments(Client, Input0, Options0) -> Method = post, Path = ["/v1/describecomputeenvironments"], SuccessStatusCode = undefined, Options = [{send_body_as_binary, false}, {receive_body_as_binary, false} | Options0], Headers = [], Input1 = Input0, Query_ = [], Input = Input1, request(Client, Method, Path, Query_, Headers, Input, Options, SuccessStatusCode). %% @doc Describes a list of job definitions. %% %% You can specify a `status' (such as `ACTIVE') to only return job %% definitions that match that status. describe_job_definitions(Client, Input) -> describe_job_definitions(Client, Input, []). describe_job_definitions(Client, Input0, Options0) -> Method = post, Path = ["/v1/describejobdefinitions"], SuccessStatusCode = undefined, Options = [{send_body_as_binary, false}, {receive_body_as_binary, false} | Options0], Headers = [], Input1 = Input0, Query_ = [], Input = Input1, request(Client, Method, Path, Query_, Headers, Input, Options, SuccessStatusCode). %% @doc Describes one or more of your job queues. describe_job_queues(Client, Input) -> describe_job_queues(Client, Input, []). describe_job_queues(Client, Input0, Options0) -> Method = post, Path = ["/v1/describejobqueues"], SuccessStatusCode = undefined, Options = [{send_body_as_binary, false}, {receive_body_as_binary, false} | Options0], Headers = [], Input1 = Input0, Query_ = [], Input = Input1, request(Client, Method, Path, Query_, Headers, Input, Options, SuccessStatusCode). %% @doc Describes a list of AWS Batch jobs. describe_jobs(Client, Input) -> describe_jobs(Client, Input, []). describe_jobs(Client, Input0, Options0) -> Method = post, Path = ["/v1/describejobs"], SuccessStatusCode = undefined, Options = [{send_body_as_binary, false}, {receive_body_as_binary, false} | Options0], Headers = [], Input1 = Input0, Query_ = [], Input = Input1, request(Client, Method, Path, Query_, Headers, Input, Options, SuccessStatusCode). %% @doc Returns a list of AWS Batch jobs. %% %% You must specify only one of the following items: %% %%