<?php
// This file was auto-generated from sdk-root/src/data/batch/2016-08-10/docs-2.json
return [ 'version' => '2.0', 'service' => '<fullname>Batch</fullname>
Using Batch, you can run batch computing workloads on the Amazon Web Services Cloud. Batch computing is a common means for developers, scientists, and engineers to access large amounts of compute resources. Batch uses the advantages of the batch computing to remove the undifferentiated heavy lifting of configuring and managing required infrastructure. At the same time, it also adopts a familiar batch computing software approach. You can use Batch to efficiently provision resources d, and work toward eliminating capacity constraints, reducing your overall compute costs, and delivering results more quickly.

As a fully managed service, Batch can run batch computing workloads of any scale. Batch automatically provisions compute resources and optimizes workload distribution based on the quantity and scale of your specific workloads. With Batch, there\'s no need to install or manage batch computing software. This means that you can focus on analyzing results and solving your specific problems instead.
', 'operations' => [ 'CancelJob' => '
Cancels a job in an Batch job queue. Jobs that are in the SUBMITTED or PENDING are canceled. A job inRUNNABLE remains in RUNNABLE until it reaches the head of the job queue. Then the job status is updated to FAILED.

Jobs that progressed to the STARTING or RUNNING state aren\'t canceled. However, the API operation still succeeds, even if no job is canceled. These jobs must be terminated with the TerminateJob operation.
', 'CreateComputeEnvironment' => '
Creates an Batch compute environment. You can create MANAGED or UNMANAGED compute environments. MANAGED compute environments can use Amazon EC2 or Fargate resources. UNMANAGED compute environments can only use EC2 resources.

In a managed compute environment, 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. Either, you can choose to use EC2 On-Demand Instances and EC2 Spot Instances. Or, you can 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.
 <note>
Multi-node parallel jobs aren\'t supported on Spot Instances.
 </note>
In an unmanaged compute environment, you can manage your own EC2 compute resources and have flexibility with how you configure your compute resources. For example, you can use custom AMIs. However, you must verify that each of your AMIs meet the Amazon ECS container instance AMI specification. For more information, see container instance AMIs in the Amazon Elastic Container Service Developer Guide. After you created your unmanaged compute environment, you can use the DescribeComputeEnvironments operation to find the Amazon ECS cluster that\'s associated with it. Then, 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.
 <note>
To create a compute environment that uses EKS resources, the caller must have permissions to call eks:DescribeCluster.
 </note> <note>
Batch doesn\'t automatically upgrade the AMIs in a compute environment after it\'s created. For example, it also doesn\'t update the AMIs in your compute environment when a newer version of the Amazon ECS optimized AMI is available. You\'re responsible for the management of the guest operating system. This includes any updates and security patches. You\'re also responsible for any additional application software or utilities that you install on the compute resources. There are two ways to use a new AMI for your Batch jobs. The original method is to 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.

In April 2022, Batch added enhanced support for updating compute environments. For more information, see Updating compute environments. To use the enhanced updating of compute environments to update AMIs, follow these rules:

Either don\'t set the service role (serviceRole) parameter or set it to the AWSBatchServiceRole service-linked role.

Set the allocation strategy (allocationStrategy) parameter to BEST_FIT_PROGRESSIVE or SPOT_CAPACITY_OPTIMIZED.

Set the update to latest image version (updateToLatestImageVersion) parameter to true.

Don\'t specify an AMI ID in imageId, imageIdOverride (in  ec2Configuration ), or in the launch template (launchTemplate). In that case, Batch selects the latest Amazon ECS optimized AMI that\'s supported by Batch at the time the infrastructure update is initiated. Alternatively, you can specify the AMI ID in the imageId or imageIdOverride parameters, or the launch template identified by the LaunchTemplate properties. Changing any of these properties starts an infrastructure update. If the AMI ID is specified in the launch template, it can\'t be replaced by specifying an AMI ID in either the imageId or imageIdOverride parameters. It can only be replaced by specifying a different launch template, or if the launch template version is set to $Default or $Latest, by setting either a new default version for the launch template (if $Default) or by adding a new version to the launch template (if $Latest).

If these rules are followed, any update that starts an infrastructure update causes the AMI ID to be re-selected. If the version setting in the launch template (launchTemplate) is set to $Latest or $Default, the latest or default version of the launch template is evaluated up at the time of the infrastructure update, even if the launchTemplate wasn\'t updated.
 </note>', 'CreateJobQueue' => '
Creates an 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 that the 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.
', 'CreateSchedulingPolicy' => '
Creates an Batch scheduling policy.
', 'DeleteComputeEnvironment' => '
Deletes an 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 Fargate resources must terminate all active jobs on that compute environment before deleting the compute environment. If this isn\'t done, the compute environment enters an invalid state.
', 'DeleteJobQueue' => '
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.
', 'DeleteSchedulingPolicy' => '
Deletes the specified scheduling policy.

You can\'t delete a scheduling policy that\'s used in any job queues.
', 'DeregisterJobDefinition' => '
Deregisters an Batch job definition. Job definitions are permanently deleted after 180 days.
', 'DescribeComputeEnvironments' => '
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 launch your Amazon ECS container instances into.
', 'DescribeJobDefinitions' => '
Describes a list of job definitions. You can specify a status (such as ACTIVE) to only return job definitions that match that status.
', 'DescribeJobQueues' => '
Describes one or more of your job queues.
', 'DescribeJobs' => '
Describes a list of Batch jobs.
', 'DescribeSchedulingPolicies' => '
Describes one or more of your scheduling policies.
', 'ListJobs' => '
Returns a list of Batch jobs.

You must specify only one of the following items:

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 nodes for that job

An array job ID to return a list of the children for that job

You can filter the results by job status with the jobStatus parameter. If you don\'t specify a status, only RUNNING jobs are returned.
', 'ListSchedulingPolicies' => '
Returns a list of Batch scheduling policies.
', 'ListTagsForResource' => '
Lists the tags for an Batch resource. Batch resources that support tags are compute environments, jobs, job definitions, job queues, and scheduling policies. ARNs for child jobs of array and multi-node parallel (MNP) jobs aren\'t supported.
', 'RegisterJobDefinition' => '
Registers an Batch job definition.
', 'SubmitJob' => '
Submits an Batch job from a job definition. Parameters that are specified during SubmitJob override parameters defined in the job definition. vCPU and memory requirements that are specified in the resourceRequirements objects in the job definition are the exception. They can\'t be overridden this way using the memory and vcpus parameters. Rather, you must specify updates to job definition parameters in a resourceRequirements object that\'s included in the containerOverrides parameter.
 <note>
Job queues with a scheduling policy are limited to 500 active fair share identifiers at a time.
 </note> <important>
Jobs that run on Fargate resources can\'t be guaranteed to run for more than 14 days. This is because, after 14 days, Fargate resources might become unavailable and job might be terminated.
 </important>', 'TagResource' => '
Associates the specified tags to a resource with the specified resourceArn. If existing tags on a resource aren\'t specified in the request parameters, they aren\'t changed. When a resource is deleted, the tags that are associated with that resource are deleted as well. Batch resources that support tags are compute environments, jobs, job definitions, job queues, and scheduling policies. ARNs for child jobs of array and multi-node parallel (MNP) jobs aren\'t supported.
', 'TerminateJob' => '
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.
', 'UntagResource' => '
Deletes specified tags from an Batch resource.
', 'UpdateComputeEnvironment' => '
Updates an Batch compute environment.
', 'UpdateJobQueue' => '
Updates a job queue.
', 'UpdateSchedulingPolicy' => '
Updates a scheduling policy.
', ], 'shapes' => [ 'ArrayJobDependency' => [ 'base' => NULL, 'refs' => [ 'JobDependency$type' => '
The type of the job dependency.
', ], ], 'ArrayJobStatusSummary' => [ 'base' => NULL, 'refs' => [ 'ArrayPropertiesDetail$statusSummary' => '
A summary of the number of array job children in each available job status. This parameter is returned for parent array jobs.
', ], ], 'ArrayProperties' => [ 'base' => '
An object that represents an Batch array job.
', 'refs' => [ 'SubmitJobRequest$arrayProperties' => '
The array properties for the submitted job, such as the size of the array. The array size can be between 2 and 10,000. If you specify array properties for a job, it becomes an array job. For more information, see Array Jobs in the Batch User Guide.
', ], ], 'ArrayPropertiesDetail' => [ 'base' => '
An object that represents the array properties of a job.
', 'refs' => [ 'JobDetail$arrayProperties' => '
The array properties of the job, if it\'s an array job.
', ], ], 'ArrayPropertiesSummary' => [ 'base' => '
An object that represents the array properties of a job.
', 'refs' => [ 'JobSummary$arrayProperties' => '
The array properties of the job, if it\'s an array job.
', ], ], 'AssignPublicIp' => [ 'base' => NULL, 'refs' => [ 'NetworkConfiguration$assignPublicIp' => '
Indicates whether the job has a public IP address. For a job that\'s running on Fargate resources in a private subnet to send outbound traffic to the internet (for example, to pull container images), the private subnet requires a NAT gateway be attached to route requests to the internet. For more information, see Amazon ECS task networking in the Amazon Elastic Container Service Developer Guide. The default value is "DISABLED".
', ], ], 'AttemptContainerDetail' => [ 'base' => '
An object that represents the details of a container that\'s part of a job attempt.
', 'refs' => [ 'AttemptDetail$container' => '
The details for the container in this job attempt.
', ], ], 'AttemptDetail' => [ 'base' => '
An object that represents a job attempt.
', 'refs' => [ 'AttemptDetails$member' => NULL, ], ], 'AttemptDetails' => [ 'base' => NULL, 'refs' => [ 'JobDetail$attempts' => '
A list of job attempts that are associated with this job.
', ], ], 'Boolean' => [ 'base' => NULL, 'refs' => [ 'ComputeResourceUpdate$updateToLatestImageVersion' => '
Specifies whether the AMI ID is updated to the latest one that\'s supported by Batch when the compute environment has an infrastructure update. The default value is false.
 <note>
An AMI ID can either be specified in the imageId or imageIdOverride parameters or be determined by the launch template that\'s specified in the launchTemplate parameter. If an AMI ID is specified any of these ways, this parameter is ignored. For more information about to update AMI IDs during an infrastructure update, see Updating the AMI ID in the Batch User Guide.
 </note>
When updating a compute environment, changing this setting requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
', 'ContainerDetail$readonlyRootFilesystem' => '
When this parameter is true, the container is given read-only access to its root file system. This parameter maps to ReadonlyRootfs in the Create a container section of the Docker Remote API and the --read-only option to  docker run .
', 'ContainerDetail$privileged' => '
When this parameter is true, the container is given elevated permissions on the host container instance (similar to the root user). The default value is false.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources and shouldn\'t be provided, or specified as false.
 </note>', 'ContainerProperties$readonlyRootFilesystem' => '
When this parameter is true, the container is given read-only access to its root file system. This parameter maps to ReadonlyRootfs in the Create a container section of the Docker Remote API and the --read-only option to docker run.
', 'ContainerProperties$privileged' => '
When this parameter is true, the container is given elevated permissions on the host container instance (similar to the root user). This parameter maps to Privileged in the Create a container section of the Docker Remote API and the --privileged option to docker run. The default value is false.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources and shouldn\'t be provided, or specified as false.
 </note>', 'EksContainerSecurityContext$privileged' => '
When this parameter is true, the container is given elevated permissions on the host container instance. The level of permissions are similar to the root user permissions. The default value is false. This parameter maps to privileged policy in the Privileged pod security policies in the Kubernetes documentation.
', 'EksContainerSecurityContext$readOnlyRootFilesystem' => '
When this parameter is true, the container is given read-only access to its root file system. The default value is false. This parameter maps to ReadOnlyRootFilesystem policy in the Volumes and file systems pod security policies in the Kubernetes documentation.
', 'EksContainerSecurityContext$runAsNonRoot' => '
When this parameter is specified, the container is run as a user with a uid other than 0. If this parameter isn\'t specified, so such rule is enforced. This parameter maps to RunAsUser and MustRunAsNonRoot policy in the Users and groups pod security policies in the Kubernetes documentation.
', 'EksContainerVolumeMount$readOnly' => '
If this value is true, the container has read-only access to the volume. Otherwise, the container can write to the volume. The default value is false.
', 'EksPodProperties$hostNetwork' => '
Indicates if the pod uses the hosts\' network IP address. The default value is true. Setting this to false enables the Kubernetes pod networking model. Most Batch workloads are egress-only and don\'t require the overhead of IP allocation for each pod for incoming connections. For more information, see Host namespaces and Pod networking in the Kubernetes documentation.
', 'EksPodPropertiesDetail$hostNetwork' => '
Indicates if the pod uses the hosts\' network IP address. The default value is true. Setting this to false enables the Kubernetes pod networking model. Most Batch workloads are egress-only and don\'t require the overhead of IP allocation for each pod for incoming connections. For more information, see Host namespaces and Pod networking in the Kubernetes documentation.
', 'EksSecret$optional' => '
Specifies whether the secret or the secret\'s keys must be defined.
', 'JobDefinition$propagateTags' => '
Specifies whether to propagate the tags from the job or job definition to the corresponding Amazon ECS task. If no value is specified, the tags aren\'t propagated. Tags can only be propagated to the tasks when the tasks are created. For tags with the same name, job tags are given priority over job definitions tags. If the total number of combined tags from the job and job definition is over 50, the job is moved to the FAILED state.
', 'JobDetail$propagateTags' => '
Specifies whether to propagate the tags from the job or job definition to the corresponding Amazon ECS task. If no value is specified, the tags aren\'t propagated. Tags can only be propagated to the tasks when the tasks are created. For tags with the same name, job tags are given priority over job definitions tags. If the total number of combined tags from the job and job definition is over 50, the job is moved to the FAILED state.
', 'JobDetail$isCancelled' => '
Indicates whether the job is canceled.
', 'JobDetail$isTerminated' => '
Indicates whether the job is terminated.
', 'LinuxParameters$initProcessEnabled' => '
If true, run an init process inside the container that forwards signals and reaps processes. This parameter maps to the --init option to docker run. This parameter requires version 1.25 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version | grep "Server API version"
', 'MountPoint$readOnly' => '
If this value is true, the container has read-only access to the volume. Otherwise, the container can write to the volume. The default value is false.
', 'NodeDetails$isMainNode' => '
Specifies whether the current node is the main node for a multi-node parallel job.
', 'NodePropertiesSummary$isMainNode' => '
Specifies whether the current node is the main node for a multi-node parallel job.
', 'RegisterJobDefinitionRequest$propagateTags' => '
Specifies whether to propagate the tags from the job or job definition to the corresponding Amazon ECS task. If no value is specified, the tags are not propagated. Tags can only be propagated to the tasks during task creation. For tags with the same name, job tags are given priority over job definitions tags. If the total number of combined tags from the job and job definition is over 50, the job is moved to the FAILED state.
 <note>
If the job runs on Amazon EKS resources, then you must not specify propagateTags.
 </note>', 'SubmitJobRequest$propagateTags' => '
Specifies whether to propagate the tags from the job or job definition to the corresponding Amazon ECS task. If no value is specified, the tags aren\'t propagated. Tags can only be propagated to the tasks during task creation. For tags with the same name, job tags are given priority over job definitions tags. If the total number of combined tags from the job and job definition is over 50, the job is moved to the FAILED state. When specified, this overrides the tag propagation setting in the job definition.
', 'UpdatePolicy$terminateJobsOnUpdate' => '
Specifies whether jobs are automatically terminated when the computer environment infrastructure is updated. The default value is false.
', ], ], 'CEState' => [ 'base' => NULL, 'refs' => [ 'ComputeEnvironmentDetail$state' => '
The state of the compute environment. The valid values are ENABLED or DISABLED.

If the state is ENABLED, then the Batch scheduler can attempt to place jobs from an associated job queue on the compute resources within the environment. If the compute environment is managed, then it can scale its instances out or in automatically based on the job queue demand.

If the state is DISABLED, then the Batch scheduler doesn\'t attempt to place jobs within the environment. Jobs in a STARTING or RUNNING state continue to progress normally. Managed compute environments in the DISABLED state don\'t scale out.
 <note>
Compute environments in a DISABLED state may continue to incur billing charges. To prevent additional charges, turn off and then delete the compute environment. For more information, see State in the Batch User Guide.
 </note>
When an instance is idle, the instance scales down to the minvCpus value. However, the instance size doesn\'t change. For example, consider a c5.8xlarge instance with a minvCpus value of 4 and a desiredvCpus value of 36. This instance doesn\'t scale down to a c5.large instance.
', 'CreateComputeEnvironmentRequest$state' => '
The state of the compute environment. If the state is ENABLED, then the compute environment accepts jobs from a queue and can scale out automatically based on queues.

If the state is ENABLED, then the Batch scheduler can attempt to place jobs from an associated job queue on the compute resources within the environment. If the compute environment is managed, then it can scale its instances out or in automatically, based on the job queue demand.

If the state is DISABLED, then the Batch scheduler doesn\'t attempt to place jobs within the environment. Jobs in a STARTING or RUNNING state continue to progress normally. Managed compute environments in the DISABLED state don\'t scale out.
 <note>
Compute environments in a DISABLED state may continue to incur billing charges. To prevent additional charges, turn off and then delete the compute environment. For more information, see State in the Batch User Guide.
 </note>
When an instance is idle, the instance scales down to the minvCpus value. However, the instance size doesn\'t change. For example, consider a c5.8xlarge instance with a minvCpus value of 4 and a desiredvCpus value of 36. This instance doesn\'t scale down to a c5.large instance.
', 'UpdateComputeEnvironmentRequest$state' => '
The state of the compute environment. Compute environments in the ENABLED state can accept jobs from a queue and scale in or out automatically based on the workload demand of its associated queues.

If the state is ENABLED, then the Batch scheduler can attempt to place jobs from an associated job queue on the compute resources within the environment. If the compute environment is managed, then it can scale its instances out or in automatically, based on the job queue demand.

If the state is DISABLED, then the Batch scheduler doesn\'t attempt to place jobs within the environment. Jobs in a STARTING or RUNNING state continue to progress normally. Managed compute environments in the DISABLED state don\'t scale out.
 <note>
Compute environments in a DISABLED state may continue to incur billing charges. To prevent additional charges, turn off and then delete the compute environment. For more information, see State in the Batch User Guide.
 </note>
When an instance is idle, the instance scales down to the minvCpus value. However, the instance size doesn\'t change. For example, consider a c5.8xlarge instance with a minvCpus value of 4 and a desiredvCpus value of 36. This instance doesn\'t scale down to a c5.large instance.
', ], ], 'CEStatus' => [ 'base' => NULL, 'refs' => [ 'ComputeEnvironmentDetail$status' => '
The current status of the compute environment (for example, CREATING or VALID).
', ], ], 'CEType' => [ 'base' => NULL, 'refs' => [ 'ComputeEnvironmentDetail$type' => '
The type of the compute environment: MANAGED or UNMANAGED. For more information, see Compute environments in the Batch User Guide.
', 'CreateComputeEnvironmentRequest$type' => '
The type of the compute environment: MANAGED or UNMANAGED. For more information, see Compute Environments in the Batch User Guide.
', ], ], 'CRAllocationStrategy' => [ 'base' => NULL, 'refs' => [ 'ComputeResource$allocationStrategy' => '
The allocation strategy to use for the compute resource if not enough instances of the best fitting instance type can be allocated. This might be because of availability of the instance type in the Region or Amazon EC2 service limits. For more information, see Allocation strategies in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>

BEST_FIT (default)

Batch selects an instance type that best fits the needs of the jobs with a preference for the lowest-cost instance type. If additional instances of the selected instance type aren\'t available, Batch waits for the additional instances to be available. If there aren\'t enough instances available or the user is reaching Amazon EC2 service limits, additional jobs aren\'t run until the currently running jobs are completed. This allocation strategy keeps costs lower but can limit scaling. If you\'re using Spot Fleets with BEST_FIT, the Spot Fleet IAM Role must be specified. Compute resources that use a BEST_FIT allocation strategy don\'t support infrastructure updates and can\'t update some parameters. For more information, see Updating compute environments in the Batch User Guide.

BEST_FIT_PROGRESSIVE

Batch selects additional instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types with lower cost vCPUs. If additional instances of the previously selected instance types aren\'t available, Batch selects new instance types.

SPOT_CAPACITY_OPTIMIZED

Batch selects one or more instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types that are less likely to be interrupted. This allocation strategy is only available for Spot Instance compute resources.

With both BEST_FIT_PROGRESSIVE and SPOT_CAPACITY_OPTIMIZED strategies using On-Demand or Spot Instances, and the BEST_FIT strategy using Spot Instances, Batch might need to exceed maxvCpus to meet your capacity requirements. In this event, Batch never exceeds maxvCpus by more than a single instance.
', ], ], 'CRType' => [ 'base' => NULL, 'refs' => [ 'ComputeResource$type' => '
The type of compute environment: EC2, SPOT, FARGATE, or FARGATE_SPOT. For more information, see Compute environments in the Batch User Guide.

 If you choose SPOT, you must also specify an Amazon EC2 Spot Fleet role with the spotIamFleetRole parameter. For more information, see Amazon EC2 spot fleet role in the Batch User Guide.
', 'ComputeResourceUpdate$type' => '
The type of compute environment: EC2, SPOT, FARGATE, or FARGATE_SPOT. For more information, see Compute environments in the Batch User Guide.

 If you choose SPOT, you must also specify an Amazon EC2 Spot Fleet role with the spotIamFleetRole parameter. For more information, see Amazon EC2 spot fleet role in the Batch User Guide.

When updating a compute environment, changing the type of a compute environment requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
', ], ], 'CRUpdateAllocationStrategy' => [ 'base' => NULL, 'refs' => [ 'ComputeResourceUpdate$allocationStrategy' => '
The allocation strategy to use for the compute resource if there\'s not enough instances of the best fitting instance type that can be allocated. This might be because of availability of the instance type in the Region or Amazon EC2 service limits. For more information, see Allocation strategies in the Batch User Guide.

When updating a compute environment, changing the allocation strategy requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide. BEST_FIT isn\'t supported when updating a compute environment.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>

BEST_FIT_PROGRESSIVE

Batch selects additional instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types with lower cost vCPUs. If additional instances of the previously selected instance types aren\'t available, Batch selects new instance types.

SPOT_CAPACITY_OPTIMIZED

Batch selects one or more instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types that are less likely to be interrupted. This allocation strategy is only available for Spot Instance compute resources.

With both BEST_FIT_PROGRESSIVE and SPOT_CAPACITY_OPTIMIZED strategies using On-Demand or Spot Instances, and the BEST_FIT strategy using Spot Instances, Batch might need to exceed maxvCpus to meet your capacity requirements. In this event, Batch never exceeds maxvCpus by more than a single instance.
', ], ], 'CancelJobRequest' => [ 'base' => '
Contains the parameters for CancelJob.
', 'refs' => [], ], 'CancelJobResponse' => [ 'base' => NULL, 'refs' => [], ], 'ClientException' => [ 'base' => '
These errors are usually caused by a client action. One example cause is using an action or resource on behalf of a user that doesn\'t have permissions to use the action or resource. Another cause is specifying an identifier that\'s not valid.
', 'refs' => [], ], 'ComputeEnvironmentDetail' => [ 'base' => '
An object that represents an Batch compute environment.
', 'refs' => [ 'ComputeEnvironmentDetailList$member' => NULL, ], ], 'ComputeEnvironmentDetailList' => [ 'base' => NULL, 'refs' => [ 'DescribeComputeEnvironmentsResponse$computeEnvironments' => '
The list of compute environments.
', ], ], 'ComputeEnvironmentOrder' => [ 'base' => '
The order that compute environments are tried in for job placement within a queue. Compute environments are tried in ascending order. For example, if two compute environments are associated with a job queue, the compute environment with a lower order integer value is tried for job placement first. Compute environments must be in the VALID state before you can associate them with a job queue. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT); EC2 and Fargate compute environments can\'t be mixed.
 <note>
All compute environments that are associated with a job queue must share the same architecture. Batch doesn\'t support mixing compute environment architecture types in a single job queue.
 </note>', 'refs' => [ 'ComputeEnvironmentOrders$member' => NULL, ], ], 'ComputeEnvironmentOrders' => [ 'base' => NULL, 'refs' => [ 'CreateJobQueueRequest$computeEnvironmentOrder' => '
The set of compute environments mapped to a job queue and their order relative to each other. The job scheduler uses this parameter to determine which compute environment runs a specific job. Compute environments must be in the VALID state before you can associate them with a job queue. You can associate up to three compute environments with a job queue. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT); EC2 and Fargate compute environments can\'t be mixed.
 <note>
All compute environments that are associated with a job queue must share the same architecture. Batch doesn\'t support mixing compute environment architecture types in a single job queue.
 </note>', 'JobQueueDetail$computeEnvironmentOrder' => '
The compute environments that are attached to the job queue and the order that job placement is preferred. Compute environments are selected for job placement in ascending order.
', 'UpdateJobQueueRequest$computeEnvironmentOrder' => '
Details the set of compute environments mapped to a job queue and their order relative to each other. This is one of the parameters used by the job scheduler to determine which compute environment runs a given job. Compute environments must be in the VALID state before you can associate them with a job queue. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT). EC2 and Fargate compute environments can\'t be mixed.
 <note>
All compute environments that are associated with a job queue must share the same architecture. Batch doesn\'t support mixing compute environment architecture types in a single job queue.
 </note>', ], ], 'ComputeResource' => [ 'base' => '
An object that represents an Batch compute resource. For more information, see Compute environments in the Batch User Guide.
', 'refs' => [ 'ComputeEnvironmentDetail$computeResources' => '
The compute resources defined for the compute environment. For more information, see Compute environments in the Batch User Guide.
', 'CreateComputeEnvironmentRequest$computeResources' => '
Details about the compute resources managed by the compute environment. This parameter is required for managed compute environments. For more information, see Compute Environments in the Batch User Guide.
', ], ], 'ComputeResourceUpdate' => [ 'base' => '
An object that represents the attributes of a compute environment that can be updated. For more information, see Updating compute environments in the Batch User Guide.
', 'refs' => [ 'UpdateComputeEnvironmentRequest$computeResources' => '
Details of the compute resources managed by the compute environment. Required for a managed compute environment. For more information, see Compute Environments in the Batch User Guide.
', ], ], 'ContainerDetail' => [ 'base' => '
An object that represents the details of a container that\'s part of a job.
', 'refs' => [ 'JobDetail$container' => '
An object that represents the details for the container that\'s associated with the job.
', ], ], 'ContainerOverrides' => [ 'base' => '
The overrides that should be sent to a container.
', 'refs' => [ 'NodePropertyOverride$containerOverrides' => '
The overrides that are sent to a node range.
', 'SubmitJobRequest$containerOverrides' => '
An object with various properties that override the defaults for the job definition that specify the name of a container in the specified job definition and the overrides it should receive. You can override the default command for a container, which is specified in the job definition or the Docker image, with a command override. You can also override existing environment variables on a container or add new environment variables to it with an environment override.
', ], ], 'ContainerProperties' => [ 'base' => '
Container properties are used for Amazon ECS based job definitions. These properties to describe the container that\'s launched as part of a job.
', 'refs' => [ 'JobDefinition$containerProperties' => '
An object with various properties specific to Amazon ECS based jobs. Valid values are containerProperties, eksProperties, and nodeProperties. Only one can be specified.
', 'NodeRangeProperty$container' => '
The container details for the node range.
', 'RegisterJobDefinitionRequest$containerProperties' => '
An object with various properties specific to Amazon ECS based single-node container-based jobs. If the job definition\'s type parameter is container, then you must specify either containerProperties or nodeProperties. This must not be specified for Amazon EKS based job definitions.
 <note>
If the job runs on Fargate resources, then you must not specify nodeProperties; use only containerProperties.
 </note>', ], ], 'ContainerSummary' => [ 'base' => '
An object that represents summary details of a container within a job.
', 'refs' => [ 'JobSummary$container' => '
An object that represents the details of the container that\'s associated with the job.
', ], ], 'CreateComputeEnvironmentRequest' => [ 'base' => '
Contains the parameters for CreateComputeEnvironment.
', 'refs' => [], ], 'CreateComputeEnvironmentResponse' => [ 'base' => NULL, 'refs' => [], ], 'CreateJobQueueRequest' => [ 'base' => '
Contains the parameters for CreateJobQueue.
', 'refs' => [], ], 'CreateJobQueueResponse' => [ 'base' => NULL, 'refs' => [], ], 'CreateSchedulingPolicyRequest' => [ 'base' => '
Contains the parameters for CreateSchedulingPolicy.
', 'refs' => [], ], 'CreateSchedulingPolicyResponse' => [ 'base' => NULL, 'refs' => [], ], 'DeleteComputeEnvironmentRequest' => [ 'base' => '
Contains the parameters for DeleteComputeEnvironment.
', 'refs' => [], ], 'DeleteComputeEnvironmentResponse' => [ 'base' => NULL, 'refs' => [], ], 'DeleteJobQueueRequest' => [ 'base' => '
Contains the parameters for DeleteJobQueue.
', 'refs' => [], ], 'DeleteJobQueueResponse' => [ 'base' => NULL, 'refs' => [], ], 'DeleteSchedulingPolicyRequest' => [ 'base' => '
Contains the parameters for DeleteSchedulingPolicy.
', 'refs' => [], ], 'DeleteSchedulingPolicyResponse' => [ 'base' => NULL, 'refs' => [], ], 'DeregisterJobDefinitionRequest' => [ 'base' => NULL, 'refs' => [], ], 'DeregisterJobDefinitionResponse' => [ 'base' => NULL, 'refs' => [], ], 'DescribeComputeEnvironmentsRequest' => [ 'base' => '
Contains the parameters for DescribeComputeEnvironments.
', 'refs' => [], ], 'DescribeComputeEnvironmentsResponse' => [ 'base' => NULL, 'refs' => [], ], 'DescribeJobDefinitionsRequest' => [ 'base' => '
Contains the parameters for DescribeJobDefinitions.
', 'refs' => [], ], 'DescribeJobDefinitionsResponse' => [ 'base' => NULL, 'refs' => [], ], 'DescribeJobQueuesRequest' => [ 'base' => '
Contains the parameters for DescribeJobQueues.
', 'refs' => [], ], 'DescribeJobQueuesResponse' => [ 'base' => NULL, 'refs' => [], ], 'DescribeJobsRequest' => [ 'base' => '
Contains the parameters for DescribeJobs.
', 'refs' => [], ], 'DescribeJobsResponse' => [ 'base' => NULL, 'refs' => [], ], 'DescribeSchedulingPoliciesRequest' => [ 'base' => '
Contains the parameters for DescribeSchedulingPolicies.
', 'refs' => [], ], 'DescribeSchedulingPoliciesResponse' => [ 'base' => NULL, 'refs' => [], ], 'Device' => [ 'base' => '
An object that represents a container instance host device.
 <note>
This object isn\'t applicable to jobs that are running on Fargate resources and shouldn\'t be provided.
 </note>', 'refs' => [ 'DevicesList$member' => NULL, ], ], 'DeviceCgroupPermission' => [ 'base' => NULL, 'refs' => [ 'DeviceCgroupPermissions$member' => NULL, ], ], 'DeviceCgroupPermissions' => [ 'base' => NULL, 'refs' => [ 'Device$permissions' => '
The explicit permissions to provide to the container for the device. By default, the container has permissions for read, write, and mknod for the device.
', ], ], 'DevicesList' => [ 'base' => NULL, 'refs' => [ 'LinuxParameters$devices' => '
Any of the host devices to expose to the container. This parameter maps to Devices in the Create a container section of the Docker Remote API and the --device option to docker run.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t provide it for these jobs.
 </note>', ], ], 'EFSAuthorizationConfig' => [ 'base' => '
The authorization configuration details for the Amazon EFS file system.
', 'refs' => [ 'EFSVolumeConfiguration$authorizationConfig' => '
The authorization configuration details for the Amazon EFS file system.
', ], ], 'EFSAuthorizationConfigIAM' => [ 'base' => NULL, 'refs' => [ 'EFSAuthorizationConfig$iam' => '
Whether or not to use the Batch job IAM role defined in a job definition when mounting the Amazon EFS file system. If enabled, transit encryption must be enabled in the EFSVolumeConfiguration. If this parameter is omitted, the default value of DISABLED is used. For more information, see Using Amazon EFS access points in the Batch User Guide. EFS IAM authorization requires that TransitEncryption be ENABLED and that a JobRoleArn is specified.
', ], ], 'EFSTransitEncryption' => [ 'base' => NULL, 'refs' => [ 'EFSVolumeConfiguration$transitEncryption' => '
Determines whether to enable encryption for Amazon EFS data in transit between the Amazon ECS host and the Amazon EFS server. Transit encryption must be enabled if Amazon EFS IAM authorization is used. If this parameter is omitted, the default value of DISABLED is used. For more information, see Encrypting data in transit in the Amazon Elastic File System User Guide.
', ], ], 'EFSVolumeConfiguration' => [ 'base' => '
This is used when you\'re using an Amazon Elastic File System file system for job storage. For more information, see Amazon EFS Volumes in the Batch User Guide.
', 'refs' => [ 'Volume$efsVolumeConfiguration' => '
This parameter is specified when you\'re using an Amazon Elastic File System file system for job storage. Jobs that are running on Fargate resources must specify a platformVersion of at least 1.4.0.
', ], ], 'Ec2Configuration' => [ 'base' => '
Provides information used to select Amazon Machine Images (AMIs) for instances in the compute environment. If Ec2Configuration isn\'t specified, the default is ECS_AL2 (Amazon Linux 2).
 <note>
This object isn\'t applicable to jobs that are running on Fargate resources.
 </note>', 'refs' => [ 'Ec2ConfigurationList$member' => NULL, ], ], 'Ec2ConfigurationList' => [ 'base' => NULL, 'refs' => [ 'ComputeResource$ec2Configuration' => '
Provides information that\'s used to select Amazon Machine Images (AMIs) for EC2 instances in the compute environment. If Ec2Configuration isn\'t specified, the default is ECS_AL2.

One or two values can be provided.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResourceUpdate$ec2Configuration' => '
Provides information used to select Amazon Machine Images (AMIs) for EC2 instances in the compute environment. If Ec2Configuration isn\'t specified, the default is ECS_AL2.

When updating a compute environment, changing this setting requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide. To remove the EC2 configuration and any custom AMI ID specified in imageIdOverride, set this value to an empty string.

One or two values can be provided.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', ], ], 'EksAttemptContainerDetail' => [ 'base' => '
An object that represents the details for an attempt for a job attempt that an Amazon EKS container runs.
', 'refs' => [ 'EksAttemptContainerDetails$member' => NULL, ], ], 'EksAttemptContainerDetails' => [ 'base' => NULL, 'refs' => [ 'EksAttemptDetail$containers' => '
The details for the final status of the containers for this job attempt.
', ], ], 'EksAttemptDetail' => [ 'base' => '
An object that represents the details of a job attempt for a job attempt by an Amazon EKS container.
', 'refs' => [ 'EksAttemptDetails$member' => NULL, ], ], 'EksAttemptDetails' => [ 'base' => NULL, 'refs' => [ 'JobDetail$eksAttempts' => '
A list of job attempts that are associated with this job.
', ], ], 'EksConfiguration' => [ 'base' => '
Configuration for the Amazon EKS cluster that supports the Batch compute environment. The cluster must exist before the compute environment can be created.
', 'refs' => [ 'ComputeEnvironmentDetail$eksConfiguration' => '
The configuration for the Amazon EKS cluster that supports the Batch compute environment. Only specify this parameter if the containerOrchestrationType is EKS.
', 'CreateComputeEnvironmentRequest$eksConfiguration' => '
The details for the Amazon EKS cluster that supports the compute environment.
', ], ], 'EksContainer' => [ 'base' => '
EKS container properties are used in job definitions for Amazon EKS based job definitions to describe the properties for a container node in the pod that\'s launched as part of a job. This can\'t be specified for Amazon ECS based job definitions.
', 'refs' => [ 'EksContainers$member' => NULL, ], ], 'EksContainerDetail' => [ 'base' => '
The details for container properties that are returned by DescribeJobs for jobs that use Amazon EKS.
', 'refs' => [ 'EksContainerDetails$member' => NULL, ], ], 'EksContainerDetails' => [ 'base' => NULL, 'refs' => [ 'EksPodPropertiesDetail$containers' => '
The properties of the container that\'s used on the Amazon EKS pod.
', ], ], 'EksContainerEnvironmentVariable' => [ 'base' => '
An environment variable.
', 'refs' => [ 'EksContainerEnvironmentVariables$member' => NULL, ], ], 'EksContainerEnvironmentVariables' => [ 'base' => NULL, 'refs' => [ 'EksContainer$env' => '
The environment variables to pass to a container.
 <note>
Environment variables cannot start with "AWS_BATCH". This naming convention is reserved for variables that Batch sets.
 </note>', 'EksContainerDetail$env' => '
The environment variables to pass to a container.
 <note>
Environment variables cannot start with "AWS_BATCH". This naming convention is reserved for variables that Batch sets.
 </note>', 'EksContainerOverride$env' => '
The environment variables to send to the container. You can add new environment variables, which are added to the container at launch. Or, you can override the existing environment variables from the Docker image or the job definition.
 <note>
Environment variables cannot start with "AWS_BATCH". This naming convention is reserved for variables that Batch sets.
 </note>', ], ], 'EksContainerOverride' => [ 'base' => '
Object representing any Kubernetes overrides to a job definition that\'s used in a SubmitJob API operation.
', 'refs' => [ 'EksContainerOverrideList$member' => NULL, ], ], 'EksContainerOverrideList' => [ 'base' => NULL, 'refs' => [ 'EksPodPropertiesOverride$containers' => '
The overrides for the container that\'s used on the Amazon EKS pod.
', ], ], 'EksContainerResourceRequirements' => [ 'base' => '
The type and amount of resources to assign to a container. The supported resources include memory, cpu, and nvidia.com/gpu. For more information, see Resource management for pods and containers in the Kubernetes documentation.
', 'refs' => [ 'EksContainer$resources' => '
The type and amount of resources to assign to a container. The supported resources include memory, cpu, and nvidia.com/gpu. For more information, see Resource management for pods and containers in the Kubernetes documentation.
', 'EksContainerDetail$resources' => '
The type and amount of resources to assign to a container. The supported resources include memory, cpu, and nvidia.com/gpu. For more information, see Resource management for pods and containers in the Kubernetes documentation.
', 'EksContainerOverride$resources' => '
The type and amount of resources to assign to a container. These override the settings in the job definition. The supported resources include memory, cpu, and nvidia.com/gpu. For more information, see Resource management for pods and containers in the Kubernetes documentation.
', ], ], 'EksContainerSecurityContext' => [ 'base' => '
The security context for a job. For more information, see Configure a security context for a pod or container in the Kubernetes documentation.
', 'refs' => [ 'EksContainer$securityContext' => '
The security context for a job. For more information, see Configure a security context for a pod or container in the Kubernetes documentation.
', 'EksContainerDetail$securityContext' => '
The security context for a job. For more information, see Configure a security context for a pod or container in the Kubernetes documentation.
', ], ], 'EksContainerVolumeMount' => [ 'base' => '
The volume mounts for a container for an Amazon EKS job. For more information about volumes and volume mounts in Kubernetes, see Volumes in the Kubernetes documentation.
', 'refs' => [ 'EksContainerVolumeMounts$member' => NULL, ], ], 'EksContainerVolumeMounts' => [ 'base' => NULL, 'refs' => [ 'EksContainer$volumeMounts' => '
The volume mounts for the container. Batch supports emptyDir, hostPath, and secret volume types. For more information about volumes and volume mounts in Kubernetes, see Volumes in the Kubernetes documentation.
', 'EksContainerDetail$volumeMounts' => '
The volume mounts for the container. Batch supports emptyDir, hostPath, and secret volume types. For more information about volumes and volume mounts in Kubernetes, see Volumes in the Kubernetes documentation.
', ], ], 'EksContainers' => [ 'base' => NULL, 'refs' => [ 'EksPodProperties$containers' => '
The properties of the container that\'s used on the Amazon EKS pod.
', ], ], 'EksEmptyDir' => [ 'base' => '
Specifies the configuration of a Kubernetes emptyDir volume. An emptyDir volume is first created when a pod is assigned to a node. It exists as long as that pod is running on that node. The emptyDir volume is initially empty. All containers in the pod can read and write the files in the emptyDir volume. However, the emptyDir volume can be mounted at the same or different paths in each container. When a pod is removed from a node for any reason, the data in the emptyDir is deleted permanently. For more information, see emptyDir in the Kubernetes documentation.
', 'refs' => [ 'EksVolume$emptyDir' => '
Specifies the configuration of a Kubernetes emptyDir volume. For more information, see emptyDir in the Kubernetes documentation.
', ], ], 'EksHostPath' => [ 'base' => '
Specifies the configuration of a Kubernetes hostPath volume. A hostPath volume mounts an existing file or directory from the host node\'s filesystem into your pod. For more information, see hostPath in the Kubernetes documentation.
', 'refs' => [ 'EksVolume$hostPath' => '
Specifies the configuration of a Kubernetes hostPath volume. For more information, see hostPath in the Kubernetes documentation.
', ], ], 'EksLabelsMap' => [ 'base' => NULL, 'refs' => [ 'EksMetadata$labels' => '
Key-value pairs used to identify, sort, and organize cube resources. Can contain up to 63 uppercase letters, lowercase letters, numbers, hyphens (-), and underscores (_). Labels can be added or modified at any time. Each resource can have multiple labels, but each key must be unique for a given object.
', ], ], 'EksLimits' => [ 'base' => NULL, 'refs' => [ 'EksContainerResourceRequirements$limits' => '
The type and quantity of the resources to reserve for the container. The values vary based on the name that\'s specified. Resources can be requested using either the limits or the requests objects.

memory

The memory hard limit (in MiB) for the container, using whole integers, with a "Mi" suffix. If your container attempts to exceed the memory specified, the container is terminated. You must specify at least 4 MiB of memory for a job. memory can be specified in limits, requests, or both. If memory is specified in both places, then the value that\'s specified in limits must be equal to the value that\'s specified in requests.
 <note>
To maximize your resource utilization, provide your jobs with as much memory as possible for the specific instance type that you are using. To learn how, see Memory management in the Batch User Guide.
 </note>

cpu

The number of CPUs that\'s reserved for the container. Values must be an even multiple of 0.25. cpu can be specified in limits, requests, or both. If cpu is specified in both places, then the value that\'s specified in limits must be at least as large as the value that\'s specified in requests.

nvidia.com/gpu

The number of GPUs that\'s reserved for the container. Values must be a whole integer. memory can be specified in limits, requests, or both. If memory is specified in both places, then the value that\'s specified in limits must be equal to the value that\'s specified in requests.

', ], ], 'EksMetadata' => [ 'base' => '
Describes and uniquely identifies Kubernetes resources. For example, the compute environment that a pod runs in or the jobID for a job running in the pod. For more information, see Understanding Kubernetes Objects in the Kubernetes documentation.
', 'refs' => [ 'EksPodProperties$metadata' => '
Metadata about the Kubernetes pod. For more information, see Understanding Kubernetes Objects in the Kubernetes documentation.
', 'EksPodPropertiesDetail$metadata' => NULL, 'EksPodPropertiesOverride$metadata' => '
Metadata about the overrides for the container that\'s used on the Amazon EKS pod.
', ], ], 'EksPodProperties' => [ 'base' => '
The properties for the pod.
', 'refs' => [ 'EksProperties$podProperties' => '
The properties for the Kubernetes pod resources of a job.
', ], ], 'EksPodPropertiesDetail' => [ 'base' => '
The details for the pod.
', 'refs' => [ 'EksPropertiesDetail$podProperties' => '
The properties for the Kubernetes pod resources of a job.
', ], ], 'EksPodPropertiesOverride' => [ 'base' => '
An object that contains overrides for the Kubernetes pod properties of a job.
', 'refs' => [ 'EksPropertiesOverride$podProperties' => '
The overrides for the Kubernetes pod resources of a job.
', ], ], 'EksProperties' => [ 'base' => '
An object that contains the properties for the Kubernetes resources of a job.
', 'refs' => [ 'JobDefinition$eksProperties' => '
An object with various properties that are specific to Amazon EKS based jobs. Valid values are containerProperties, eksProperties, and nodeProperties. Only one can be specified.
', 'RegisterJobDefinitionRequest$eksProperties' => '
An object with various properties that are specific to Amazon EKS based jobs. This must not be specified for Amazon ECS based job definitions.
', ], ], 'EksPropertiesDetail' => [ 'base' => '
An object that contains the details for the Kubernetes resources of a job.
', 'refs' => [ 'JobDetail$eksProperties' => '
An object with various properties that are specific to Amazon EKS based jobs. Only one of container, eksProperties, or nodeDetails is specified.
', ], ], 'EksPropertiesOverride' => [ 'base' => '
An object that contains overrides for the Kubernetes resources of a job.
', 'refs' => [ 'SubmitJobRequest$eksPropertiesOverride' => '
An object that can only be specified for jobs that are run on Amazon EKS resources with various properties that override defaults for the job definition.
', ], ], 'EksRequests' => [ 'base' => NULL, 'refs' => [ 'EksContainerResourceRequirements$requests' => '
The type and quantity of the resources to request for the container. The values vary based on the name that\'s specified. Resources can be requested by using either the limits or the requests objects.

memory

The memory hard limit (in MiB) for the container, using whole integers, with a "Mi" suffix. If your container attempts to exceed the memory specified, the container is terminated. You must specify at least 4 MiB of memory for a job. memory can be specified in limits, requests, or both. If memory is specified in both, then the value that\'s specified in limits must be equal to the value that\'s specified in requests.
 <note>
If you\'re trying to maximize your resource utilization by providing your jobs as much memory as possible for a particular instance type, see Memory management in the Batch User Guide.
 </note>

cpu

The number of CPUs that are reserved for the container. Values must be an even multiple of 0.25. cpu can be specified in limits, requests, or both. If cpu is specified in both, then the value that\'s specified in limits must be at least as large as the value that\'s specified in requests.

nvidia.com/gpu

The number of GPUs that are reserved for the container. Values must be a whole integer. nvidia.com/gpu can be specified in limits, requests, or both. If nvidia.com/gpu is specified in both, then the value that\'s specified in limits must be equal to the value that\'s specified in requests.

', ], ], 'EksSecret' => [ 'base' => '
Specifies the configuration of a Kubernetes secret volume. For more information, see secret in the Kubernetes documentation.
', 'refs' => [ 'EksVolume$secret' => '
Specifies the configuration of a Kubernetes secret volume. For more information, see secret in the Kubernetes documentation.
', ], ], 'EksVolume' => [ 'base' => '
Specifies an Amazon EKS volume for a job definition.
', 'refs' => [ 'EksVolumes$member' => NULL, ], ], 'EksVolumes' => [ 'base' => NULL, 'refs' => [ 'EksPodProperties$volumes' => '
Specifies the volumes for a job definition that uses Amazon EKS resources.
', 'EksPodPropertiesDetail$volumes' => '
Specifies the volumes for a job definition using Amazon EKS resources.
', ], ], 'EnvironmentVariables' => [ 'base' => NULL, 'refs' => [ 'ContainerDetail$environment' => '
The environment variables to pass to a container.
 <note>
Environment variables cannot start with "AWS_BATCH". This naming convention is reserved for variables that Batch sets.
 </note>', 'ContainerOverrides$environment' => '
The environment variables to send to the container. You can add new environment variables, which are added to the container at launch, or you can override the existing environment variables from the Docker image or the job definition.
 <note>
Environment variables cannot start with "AWS_BATCH". This naming convention is reserved for variables that Batch sets.
 </note>', 'ContainerProperties$environment' => '
The environment variables to pass to a container. This parameter maps to Env in the Create a container section of the Docker Remote API and the --env option to docker run.
 <important>
We don\'t recommend using plaintext environment variables for sensitive information, such as credential data.
 </important> <note>
Environment variables cannot start with "AWS_BATCH". This naming convention is reserved for variables that Batch sets.
 </note>', ], ], 'EphemeralStorage' => [ 'base' => '
The amount of ephemeral storage to allocate for the task. This parameter is used to expand the total amount of ephemeral storage available, beyond the default amount, for tasks hosted on Fargate.
', 'refs' => [ 'ContainerDetail$ephemeralStorage' => '
The amount of ephemeral storage allocated for the task. This parameter is used to expand the total amount of ephemeral storage available, beyond the default amount, for tasks hosted on Fargate.
', 'ContainerProperties$ephemeralStorage' => '
The amount of ephemeral storage to allocate for the task. This parameter is used to expand the total amount of ephemeral storage available, beyond the default amount, for tasks hosted on Fargate.
', ], ], 'EvaluateOnExit' => [ 'base' => '
Specifies an array of up to 5 conditions to be met, and an action to take (RETRY or EXIT) if all conditions are met. If none of the EvaluateOnExit conditions in a RetryStrategy match, then the job is retried.
', 'refs' => [ 'EvaluateOnExitList$member' => NULL, ], ], 'EvaluateOnExitList' => [ 'base' => NULL, 'refs' => [ 'RetryStrategy$evaluateOnExit' => '
Array of up to 5 objects that specify the conditions where jobs are retried or failed. If this parameter is specified, then the attempts parameter must also be specified. If none of the listed conditions match, then the job is retried.
', ], ], 'FairsharePolicy' => [ 'base' => '
The fair share policy for a scheduling policy.
', 'refs' => [ 'CreateSchedulingPolicyRequest$fairsharePolicy' => '
The fair share policy of the scheduling policy.
', 'SchedulingPolicyDetail$fairsharePolicy' => '
The fair share policy for the scheduling policy.
', 'UpdateSchedulingPolicyRequest$fairsharePolicy' => '
The fair share policy.
', ], ], 'FargatePlatformConfiguration' => [ 'base' => '
The platform configuration for jobs that are running on Fargate resources. Jobs that run on EC2 resources must not specify this parameter.
', 'refs' => [ 'ContainerDetail$fargatePlatformConfiguration' => '
The platform configuration for jobs that are running on Fargate resources. Jobs that are running on EC2 resources must not specify this parameter.
', 'ContainerProperties$fargatePlatformConfiguration' => '
The platform configuration for jobs that are running on Fargate resources. Jobs that are running on EC2 resources must not specify this parameter.
', ], ], 'Float' => [ 'base' => NULL, 'refs' => [ 'ShareAttributes$weightFactor' => '
The weight factor for the fair share identifier. The default value is 1.0. A lower value has a higher priority for compute resources. For example, jobs that use a share identifier with a weight factor of 0.125 (1/8) get 8 times the compute resources of jobs that use a share identifier with a weight factor of 1.

The smallest supported value is 0.0001, and the largest supported value is 999.9999.
', ], ], 'Host' => [ 'base' => '
Determine whether your data volume persists on the host container instance and where it\'s stored. If this parameter is empty, then the Docker daemon assigns a host path for your data volume. However, the data isn\'t guaranteed to persist after the containers that are associated with it stop running.
', 'refs' => [ 'Volume$host' => '
The contents of the host parameter determine whether your data volume persists on the host container instance and where it\'s stored. If the host parameter is empty, then the Docker daemon assigns a host path for your data volume. However, the data isn\'t guaranteed to persist after the containers that are associated with it stop running.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources and shouldn\'t be provided.
 </note>', ], ], 'ImageIdOverride' => [ 'base' => NULL, 'refs' => [ 'Ec2Configuration$imageIdOverride' => '
The AMI ID used for instances launched in the compute environment that match the image type. This setting overrides the imageId set in the computeResource object.
 <note>
The AMI that you choose for a compute environment must match the architecture of the instance types that you intend to use for that compute environment. For example, if your compute environment uses A1 instance types, the compute resource AMI that you choose must support ARM instances. Amazon ECS vends both x86 and ARM versions of the Amazon ECS-optimized Amazon Linux 2 AMI. For more information, see Amazon ECS-optimized Amazon Linux 2 AMI in the Amazon Elastic Container Service Developer Guide.
 </note>', ], ], 'ImageType' => [ 'base' => NULL, 'refs' => [ 'Ec2Configuration$imageType' => '
The image type to match with the instance type to select an AMI. The supported values are different for ECS and EKS resources.

ECS

If the imageIdOverride parameter isn\'t specified, then a recent Amazon ECS-optimized Amazon Linux 2 AMI (ECS_AL2) is used. If a new image type is specified in an update, but neither an imageId nor a imageIdOverride parameter is specified, then the latest Amazon ECS optimized AMI for that image type that\'s supported by Batch is used.

ECS_AL2

 Amazon Linux 2: Default for all non-GPU instance families.

ECS_AL2_NVIDIA

 Amazon Linux 2 (GPU): Default for all GPU instance families (for example P4 and G4) and can be used for all non Amazon Web Services Graviton-based instance types.

ECS_AL1

 Amazon Linux. Amazon Linux has reached the end-of-life of standard support. For more information, see Amazon Linux AMI.

EKS

If the imageIdOverride parameter isn\'t specified, then a recent Amazon EKS-optimized Amazon Linux AMI (EKS_AL2) is used. If a new image type is specified in an update, but neither an imageId nor a imageIdOverride parameter is specified, then the latest Amazon EKS optimized AMI for that image type that Batch supports is used.

EKS_AL2

 Amazon Linux 2: Default for all non-GPU instance families.

EKS_AL2_NVIDIA

 Amazon Linux 2 (accelerated): Default for all GPU instance families (for example, P4 and G4) and can be used for all non Amazon Web Services Graviton-based instance types.

', ], ], 'Integer' => [ 'base' => NULL, 'refs' => [ 'ArrayJobStatusSummary$value' => NULL, 'ArrayProperties$size' => '
The size of the array job.
', 'ArrayPropertiesDetail$size' => '
The size of the array job. This parameter is returned for parent array jobs.
', 'ArrayPropertiesDetail$index' => '
The job index within the array that\'s associated with this job. This parameter is returned for array job children.
', 'ArrayPropertiesSummary$size' => '
The size of the array job. This parameter is returned for parent array jobs.
', 'ArrayPropertiesSummary$index' => '
The job index within the array that\'s associated with this job. This parameter is returned for children of array jobs.
', 'AttemptContainerDetail$exitCode' => '
The exit code for the job attempt. A non-zero exit code is considered failed.
', 'ComputeEnvironmentDetail$unmanagedvCpus' => '
The maximum number of VCPUs expected to be used for an unmanaged compute environment.
', 'ComputeEnvironmentOrder$order' => '
The order of the compute environment. Compute environments are tried in ascending order. For example, if two compute environments are associated with a job queue, the compute environment with a lower order integer value is tried for job placement first.
', 'ComputeResource$minvCpus' => '
The minimum number of Amazon EC2 vCPUs that an environment should maintain (even if the compute environment is DISABLED).
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResource$maxvCpus' => '
The maximum number of Amazon EC2 vCPUs that a compute environment can reach.
 <note>
With both BEST_FIT_PROGRESSIVE and SPOT_CAPACITY_OPTIMIZED allocation strategies using On-Demand or Spot Instances, and the BEST_FIT strategy using Spot Instances, Batch might need to exceed maxvCpus to meet your capacity requirements. In this event, Batch never exceeds maxvCpus by more than a single instance. For example, no more than a single instance from among those specified in your compute environment is allocated.
 </note>', 'ComputeResource$desiredvCpus' => '
The desired number of Amazon EC2 vCPUS in the compute environment. Batch modifies this value between the minimum and maximum values based on job queue demand.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResource$bidPercentage' => '
The maximum percentage that a Spot Instance price can be when compared with the On-Demand price for that instance type before instances are launched. For example, if your maximum percentage is 20%, then the Spot price must be less than 20% of the current On-Demand price for that Amazon EC2 instance. You always pay the lowest (market) price and never more than your maximum percentage. If you leave this field empty, the default value is 100% of the On-Demand price. For most use cases, we recommend leaving this field empty.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResourceUpdate$minvCpus' => '
The minimum number of Amazon EC2 vCPUs that an environment should maintain (even if the compute environment is DISABLED).
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResourceUpdate$maxvCpus' => '
The maximum number of Amazon EC2 vCPUs that an environment can reach.
 <note>
With both BEST_FIT_PROGRESSIVE and SPOT_CAPACITY_OPTIMIZED allocation strategies using On-Demand or Spot Instances, and the BEST_FIT strategy using Spot Instances, Batch might need to exceed maxvCpus to meet your capacity requirements. In this event, Batch never exceeds maxvCpus by more than a single instance. That is, no more than a single instance from among those specified in your compute environment.
 </note>', 'ComputeResourceUpdate$desiredvCpus' => '
The desired number of Amazon EC2 vCPUS in the compute environment. Batch modifies this value between the minimum and maximum values based on job queue demand.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note> <note>
Batch doesn\'t support changing the desired number of vCPUs of an existing compute environment. Don\'t specify this parameter for compute environments using Amazon EKS clusters.
 </note> <note>
When you update the desiredvCpus setting, the value must be between the minvCpus and maxvCpus values.

Additionally, the updated desiredvCpus value must be greater than or equal to the current desiredvCpus value. For more information, see Troubleshooting Batch in the Batch User Guide.
 </note>', 'ComputeResourceUpdate$bidPercentage' => '
The maximum percentage that a Spot Instance price can be when compared with the On-Demand price for that instance type before instances are launched. For example, if your maximum percentage is 20%, the Spot price must be less than 20% of the current On-Demand price for that Amazon EC2 instance. You always pay the lowest (market) price and never more than your maximum percentage. For most use cases, we recommend leaving this field empty.

When updating a compute environment, changing the bid percentage requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ContainerDetail$vcpus' => '
The number of vCPUs reserved for the container. For jobs that run on EC2 resources, you can specify the vCPU requirement for the job using resourceRequirements, but you can\'t specify the vCPU requirements in both the vcpus and resourceRequirements object. This parameter maps to CpuShares in the Create a container section of the Docker Remote API and the --cpu-shares option to docker run. Each vCPU is equivalent to 1,024 CPU shares. You must specify at least one vCPU. This is required but can be specified in several places. It must be specified for each node at least once.
 <note>
This parameter isn\'t applicable to jobs that run on Fargate resources. For jobs that run on Fargate resources, you must specify the vCPU requirement for the job using resourceRequirements.
 </note>', 'ContainerDetail$memory' => '
For jobs running on EC2 resources that didn\'t specify memory requirements using resourceRequirements, the number of MiB of memory reserved for the job. For other jobs, including all run on Fargate resources, see resourceRequirements.
', 'ContainerDetail$exitCode' => '
The exit code to return upon completion.
', 'ContainerOverrides$vcpus' => '
This parameter is deprecated, use resourceRequirements to override the vcpus parameter that\'s set in the job definition. It\'s not supported for jobs running on Fargate resources. For jobs that run on EC2 resources, it overrides the vcpus parameter set in the job definition, but doesn\'t override any vCPU requirement specified in the resourceRequirements structure in the job definition. To override vCPU requirements that are specified in the resourceRequirements structure in the job definition, resourceRequirements must be specified in the SubmitJob request, with type set to VCPU and value set to the new value. For more information, see Can\'t override job definition resource requirements in the Batch User Guide.
', 'ContainerOverrides$memory' => '
This parameter is deprecated, use resourceRequirements to override the memory requirements specified in the job definition. It\'s not supported for jobs running on Fargate resources. For jobs that run on EC2 resources, it overrides the memory parameter set in the job definition, but doesn\'t override any memory requirement that\'s specified in the resourceRequirements structure in the job definition. To override memory requirements that are specified in the resourceRequirements structure in the job definition, resourceRequirements must be specified in the SubmitJob request, with type set to MEMORY and value set to the new value. For more information, see Can\'t override job definition resource requirements in the Batch User Guide.
', 'ContainerProperties$vcpus' => '
This parameter is deprecated, use resourceRequirements to specify the vCPU requirements for the job definition. It\'s not supported for jobs running on Fargate resources. For jobs running on EC2 resources, it specifies the number of vCPUs reserved for the job.

Each vCPU is equivalent to 1,024 CPU shares. This parameter maps to CpuShares in the Create a container section of the Docker Remote API and the --cpu-shares option to docker run. The number of vCPUs must be specified but can be specified in several places. You must specify it at least once for each node.
', 'ContainerProperties$memory' => '
This parameter is deprecated, use resourceRequirements to specify the memory requirements for the job definition. It\'s not supported for jobs running on Fargate resources. For jobs that run on EC2 resources, it specifies the memory hard limit (in MiB) for a container. If your container attempts to exceed the specified number, it\'s terminated. You must specify at least 4 MiB of memory for a job using this parameter. The memory hard limit can be specified in several places. It must be specified for each node at least once.
', 'ContainerSummary$exitCode' => '
The exit code to return upon completion.
', 'CreateComputeEnvironmentRequest$unmanagedvCpus' => '
The maximum number of vCPUs for an unmanaged compute environment. This parameter is only used for fair share scheduling to reserve vCPU capacity for new share identifiers. If this parameter isn\'t provided for a fair share job queue, no vCPU capacity is reserved.
 <note>
This parameter is only supported when the type parameter is set to UNMANAGED.
 </note>', 'CreateJobQueueRequest$priority' => '
The priority of the job queue. Job queues with a higher priority (or a higher integer value for the priority parameter) are evaluated first when associated with the same compute environment. Priority is determined in descending order. For example, a job queue with a priority value of 10 is given scheduling preference over a job queue with a priority value of 1. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT); EC2 and Fargate compute environments can\'t be mixed.
', 'DescribeComputeEnvironmentsRequest$maxResults' => '
The maximum number of cluster results returned by DescribeComputeEnvironments in paginated output. When this parameter is used, DescribeComputeEnvironments only returns maxResults results in a single page along with a nextToken response element. The remaining results of the initial request can be seen by sending another DescribeComputeEnvironments request with the returned nextToken value. This value can be between 1 and 100. If this parameter isn\'t used, then DescribeComputeEnvironments returns up to 100 results and a nextToken value if applicable.
', 'DescribeJobDefinitionsRequest$maxResults' => '
The maximum number of results returned by DescribeJobDefinitions in paginated output. When this parameter is used, DescribeJobDefinitions only returns maxResults results in a single page and a nextToken response element. The remaining results of the initial request can be seen by sending another DescribeJobDefinitions request with the returned nextToken value. This value can be between 1 and 100. If this parameter isn\'t used, then DescribeJobDefinitions returns up to 100 results and a nextToken value if applicable.
', 'DescribeJobQueuesRequest$maxResults' => '
The maximum number of results returned by DescribeJobQueues in paginated output. When this parameter is used, DescribeJobQueues only returns maxResults results in a single page and a nextToken response element. The remaining results of the initial request can be seen by sending another DescribeJobQueues request with the returned nextToken value. This value can be between 1 and 100. If this parameter isn\'t used, then DescribeJobQueues returns up to 100 results and a nextToken value if applicable.
', 'EFSVolumeConfiguration$transitEncryptionPort' => '
The port to use when sending encrypted data between the Amazon ECS host and the Amazon EFS server. If you don\'t specify a transit encryption port, it uses the port selection strategy that the Amazon EFS mount helper uses. The value must be between 0 and 65,535. For more information, see EFS mount helper in the Amazon Elastic File System User Guide.
', 'EksAttemptContainerDetail$exitCode' => '
The exit code for the job attempt. A non-zero exit code is considered failed.
', 'EksContainerDetail$exitCode' => '
The exit code for the job attempt. A non-zero exit code is considered failed.
', 'EphemeralStorage$sizeInGiB' => '
The total amount, in GiB, of ephemeral storage to set for the task. The minimum supported value is 21 GiB and the maximum supported value is 200 GiB.
', 'FairsharePolicy$shareDecaySeconds' => '
The amount of time (in seconds) to use to calculate a fair share percentage for each fair share identifier in use. A value of zero (0) indicates that only current usage is measured. The decay allows for more recently run jobs to have more weight than jobs that ran earlier. The maximum supported value is 604800 (1 week).
', 'FairsharePolicy$computeReservation' => '
A value used to reserve some of the available maximum vCPU for fair share identifiers that aren\'t already used.

The reserved ratio is (computeReservation/100)^ActiveFairShares  where  ActiveFairShares  is the number of active fair share identifiers.

For example, a computeReservation value of 50 indicates that Batchreserves 50% of the maximum available vCPU if there\'s only one fair share identifier. It reserves 25% if there are two fair share identifiers. It reserves 12.5% if there are three fair share identifiers. A computeReservation value of 25 indicates that Batch should reserve 25% of the maximum available vCPU if there\'s only one fair share identifier, 6.25% if there are two fair share identifiers, and 1.56% if there are three fair share identifiers.

The minimum value is 0 and the maximum value is 99.
', 'JobDefinition$revision' => '
The revision of the job definition.
', 'JobDefinition$schedulingPriority' => '
The scheduling priority of the job definition. This only affects jobs in job queues with a fair share policy. Jobs with a higher scheduling priority are scheduled before jobs with a lower scheduling priority.
', 'JobDetail$schedulingPriority' => '
The scheduling policy of the job definition. This only affects jobs in job queues with a fair share policy. Jobs with a higher scheduling priority are scheduled before jobs with a lower scheduling priority.
', 'JobQueueDetail$priority' => '
The priority of the job queue. Job queues with a higher priority (or a higher integer value for the priority parameter) are evaluated first when associated with the same compute environment. Priority is determined in descending order. For example, a job queue with a priority value of 10 is given scheduling preference over a job queue with a priority value of 1. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT). EC2 and Fargate compute environments can\'t be mixed.
', 'JobTimeout$attemptDurationSeconds' => '
The job timeout time (in seconds) that\'s measured from the job attempt\'s startedAt timestamp. After this time passes, Batch terminates your jobs if they aren\'t finished. The minimum value for the timeout is 60 seconds.

For array jobs, the timeout applies to the child jobs, not to the parent array job.

For multi-node parallel (MNP) jobs, the timeout applies to the whole job, not to the individual nodes.
', 'LinuxParameters$sharedMemorySize' => '
The value for the size (in MiB) of the /dev/shm volume. This parameter maps to the --shm-size option to docker run.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t provide it for these jobs.
 </note>', 'LinuxParameters$maxSwap' => '
The total amount of swap memory (in MiB) a container can use. This parameter is translated to the --memory-swap option to docker run where the value is the sum of the container memory plus the maxSwap value. For more information, see  --memory-swap details in the Docker documentation.

If a maxSwap value of 0 is specified, the container doesn\'t use swap. Accepted values are 0 or any positive integer. If the maxSwap parameter is omitted, the container doesn\'t use the swap configuration for the container instance that it\'s running on. A maxSwap value must be set for the swappiness parameter to be used.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t provide it for these jobs.
 </note>', 'LinuxParameters$swappiness' => '
You can use this parameter to tune a container\'s memory swappiness behavior. A swappiness value of 0 causes swapping to not occur unless absolutely necessary. A swappiness value of 100 causes pages to be swapped aggressively. Valid values are whole numbers between 0 and 100. If the swappiness parameter isn\'t specified, a default value of 60 is used. If a value isn\'t specified for maxSwap, then this parameter is ignored. If maxSwap is set to 0, the container doesn\'t use swap. This parameter maps to the --memory-swappiness option to docker run.

Consider the following when you use a per-container swap configuration.

Swap space must be enabled and allocated on the container instance for the containers to use.
 <note>
By default, the Amazon ECS optimized AMIs don\'t have swap enabled. You must enable swap on the instance to use this feature. For more information, see Instance store swap volumes in the Amazon EC2 User Guide for Linux Instances or How do I allocate memory to work as swap space in an Amazon EC2 instance by using a swap file?
 </note>

The swap space parameters are only supported for job definitions using EC2 resources.

If the maxSwap and swappiness parameters are omitted from a job definition, each container has a default swappiness value of 60. Moreover, the total swap usage is limited to two times the memory reservation of the container.

 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t provide it for these jobs.
 </note>', 'ListJobsRequest$maxResults' => '
The maximum number of results returned by ListJobs in paginated output. When this parameter is used, ListJobs only returns maxResults results in a single page and a nextToken response element. The remaining results of the initial request can be seen by sending another ListJobs request with the returned nextToken value. This value can be between 1 and 100. If this parameter isn\'t used, then ListJobs returns up to 100 results and a nextToken value if applicable.
', 'ListSchedulingPoliciesRequest$maxResults' => '
The maximum number of results that\'s returned by ListSchedulingPolicies in paginated output. When this parameter is used, ListSchedulingPolicies only returns maxResults results in a single page and a nextToken response element. You can see the remaining results of the initial request by sending another ListSchedulingPolicies request with the returned nextToken value. This value can be between 1 and 100. If this parameter isn\'t used, ListSchedulingPolicies returns up to 100 results and a nextToken value if applicable.
', 'NodeDetails$nodeIndex' => '
The node index for the node. Node index numbering starts at zero. This index is also available on the node with the AWS_BATCH_JOB_NODE_INDEX environment variable.
', 'NodeOverrides$numNodes' => '
The number of nodes to use with a multi-node parallel job. This value overrides the number of nodes that are specified in the job definition. To use this override, you must meet the following conditions:

There must be at least one node range in your job definition that has an open upper boundary, such as : or n:.

The lower boundary of the node range that\'s specified in the job definition must be fewer than the number of nodes specified in the override.

The main node index that\'s specified in the job definition must be fewer than the number of nodes specified in the override.

', 'NodeProperties$numNodes' => '
The number of nodes that are associated with a multi-node parallel job.
', 'NodeProperties$mainNode' => '
Specifies the node index for the main node of a multi-node parallel job. This node index value must be fewer than the number of nodes.
', 'NodePropertiesSummary$numNodes' => '
The number of nodes that are associated with a multi-node parallel job.
', 'NodePropertiesSummary$nodeIndex' => '
The node index for the node. Node index numbering begins at zero. This index is also available on the node with the AWS_BATCH_JOB_NODE_INDEX environment variable.
', 'RegisterJobDefinitionRequest$schedulingPriority' => '
The scheduling priority for jobs that are submitted with this job definition. This only affects jobs in job queues with a fair share policy. Jobs with a higher scheduling priority are scheduled before jobs with a lower scheduling priority.

The minimum supported value is 0 and the maximum supported value is 9999.
', 'RegisterJobDefinitionResponse$revision' => '
The revision of the job definition.
', 'RetryStrategy$attempts' => '
The number of times to move a job to the RUNNABLE status. You can specify between 1 and 10 attempts. If the value of attempts is greater than one, the job is retried on failure the same number of attempts as the value.
', 'SubmitJobRequest$schedulingPriorityOverride' => '
The scheduling priority for the job. This only affects jobs in job queues with a fair share policy. Jobs with a higher scheduling priority are scheduled before jobs with a lower scheduling priority. This overrides any scheduling priority in the job definition.

The minimum supported value is 0 and the maximum supported value is 9999.
', 'Tmpfs$size' => '
The size (in MiB) of the tmpfs volume.
', 'Ulimit$hardLimit' => '
The hard limit for the ulimit type.
', 'Ulimit$softLimit' => '
The soft limit for the ulimit type.
', 'UpdateComputeEnvironmentRequest$unmanagedvCpus' => '
The maximum number of vCPUs expected to be used for an unmanaged compute environment. Don\'t specify this parameter for a managed compute environment. This parameter is only used for fair share scheduling to reserve vCPU capacity for new share identifiers. If this parameter isn\'t provided for a fair share job queue, no vCPU capacity is reserved.
', 'UpdateJobQueueRequest$priority' => '
The priority of the job queue. Job queues with a higher priority (or a higher integer value for the priority parameter) are evaluated first when associated with the same compute environment. Priority is determined in descending order. For example, a job queue with a priority value of 10 is given scheduling preference over a job queue with a priority value of 1. All of the compute environments must be either EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT). EC2 and Fargate compute environments can\'t be mixed.
', ], ], 'JQState' => [ 'base' => NULL, 'refs' => [ 'CreateJobQueueRequest$state' => '
The state of the job queue. If the job queue state is ENABLED, it is able to accept jobs. If the job queue state is DISABLED, new jobs can\'t be added to the queue, but jobs already in the queue can finish.
', 'JobQueueDetail$state' => '
Describes the ability of the queue to accept new jobs. If the job queue state is ENABLED, it can accept jobs. If the job queue state is DISABLED, new jobs can\'t be added to the queue, but jobs already in the queue can finish.
', 'UpdateJobQueueRequest$state' => '
Describes the queue\'s ability to accept new jobs. If the job queue state is ENABLED, it can accept jobs. If the job queue state is DISABLED, new jobs can\'t be added to the queue, but jobs already in the queue can finish.
', ], ], 'JQStatus' => [ 'base' => NULL, 'refs' => [ 'JobQueueDetail$status' => '
The status of the job queue (for example, CREATING or VALID).
', ], ], 'JobDefinition' => [ 'base' => '
An object that represents an Batch job definition.
', 'refs' => [ 'JobDefinitionList$member' => NULL, ], ], 'JobDefinitionList' => [ 'base' => NULL, 'refs' => [ 'DescribeJobDefinitionsResponse$jobDefinitions' => '
The list of job definitions.
', ], ], 'JobDefinitionType' => [ 'base' => NULL, 'refs' => [ 'RegisterJobDefinitionRequest$type' => '
The type of job definition. For more information about multi-node parallel jobs, see Creating a multi-node parallel job definition in the Batch User Guide.
 <note>
If the job is run on Fargate resources, then multinode isn\'t supported.
 </note>', ], ], 'JobDependency' => [ 'base' => '
An object that represents an Batch job dependency.
', 'refs' => [ 'JobDependencyList$member' => NULL, ], ], 'JobDependencyList' => [ 'base' => NULL, 'refs' => [ 'JobDetail$dependsOn' => '
A list of job IDs that this job depends on.
', 'SubmitJobRequest$dependsOn' => '
A list of dependencies for the job. A job can depend upon a maximum of 20 jobs. You can specify a SEQUENTIAL type dependency without specifying a job ID for array jobs so that each child array job completes sequentially, starting at index 0. You can also specify an N_TO_N type dependency with a job ID for array jobs. In that case, each index child of this job must wait for the corresponding index child of each dependency to complete before it can begin.
', ], ], 'JobDetail' => [ 'base' => '
An object that represents an Batch job.
', 'refs' => [ 'JobDetailList$member' => NULL, ], ], 'JobDetailList' => [ 'base' => NULL, 'refs' => [ 'DescribeJobsResponse$jobs' => '
The list of jobs.
', ], ], 'JobExecutionTimeoutMinutes' => [ 'base' => NULL, 'refs' => [ 'UpdatePolicy$jobExecutionTimeoutMinutes' => '
Specifies the job timeout (in minutes) when the compute environment infrastructure is updated. The default value is 30.
', ], ], 'JobQueueDetail' => [ 'base' => '
An object that represents the details for an Batch job queue.
', 'refs' => [ 'JobQueueDetailList$member' => NULL, ], ], 'JobQueueDetailList' => [ 'base' => NULL, 'refs' => [ 'DescribeJobQueuesResponse$jobQueues' => '
The list of job queues.
', ], ], 'JobStatus' => [ 'base' => NULL, 'refs' => [ 'JobDetail$status' => '
The current status for the job.
 <note>
If your jobs don\'t progress to STARTING, see Jobs stuck in RUNNABLE status in the troubleshooting section of the Batch User Guide.
 </note>', 'JobSummary$status' => '
The current status for the job.
', 'ListJobsRequest$jobStatus' => '
The job status used to filter jobs in the specified queue. If the filters parameter is specified, the jobStatus parameter is ignored and jobs with any status are returned. If you don\'t specify a status, only RUNNING jobs are returned.
', ], ], 'JobSummary' => [ 'base' => '
An object that represents summary details of a job.
', 'refs' => [ 'JobSummaryList$member' => NULL, ], ], 'JobSummaryList' => [ 'base' => NULL, 'refs' => [ 'ListJobsResponse$jobSummaryList' => '
A list of job summaries that match the request.
', ], ], 'JobTimeout' => [ 'base' => '
An object that represents a job timeout configuration.
', 'refs' => [ 'JobDefinition$timeout' => '
The timeout time for jobs that are submitted with this job definition. After the amount of time you specify passes, Batch terminates your jobs if they aren\'t finished.
', 'JobDetail$timeout' => '
The timeout configuration for the job.
', 'RegisterJobDefinitionRequest$timeout' => '
The timeout configuration for jobs that are submitted with this job definition, after which Batch terminates your jobs if they have not finished. If a job is terminated due to a timeout, it isn\'t retried. The minimum value for the timeout is 60 seconds. Any timeout configuration that\'s specified during a SubmitJob operation overrides the timeout configuration defined here. For more information, see Job Timeouts in the Batch User Guide.
', 'SubmitJobRequest$timeout' => '
The timeout configuration for this SubmitJob operation. You can specify a timeout duration after which Batch terminates your jobs if they haven\'t finished. If a job is terminated due to a timeout, it isn\'t retried. The minimum value for the timeout is 60 seconds. This configuration overrides any timeout configuration specified in the job definition. For array jobs, child jobs have the same timeout configuration as the parent job. For more information, see Job Timeouts in the Amazon Elastic Container Service Developer Guide.
', ], ], 'KeyValuePair' => [ 'base' => '
A key-value pair object.
', 'refs' => [ 'EnvironmentVariables$member' => NULL, ], ], 'KeyValuesPair' => [ 'base' => '
A filter name and value pair that\'s used to return a more specific list of results from a ListJobs API operation.
', 'refs' => [ 'ListJobsFilterList$member' => NULL, ], ], 'KubernetesVersion' => [ 'base' => NULL, 'refs' => [ 'Ec2Configuration$imageKubernetesVersion' => '
The Kubernetes version for the compute environment. If you don\'t specify a value, the latest version that Batch supports is used.
', ], ], 'LaunchTemplateSpecification' => [ 'base' => '
An object that represents a launch template that\'s associated with a compute resource. You must specify either the launch template ID or launch template name in the request, but not both.

If security groups are specified using both the securityGroupIds parameter of CreateComputeEnvironment and the launch template, the values in the securityGroupIds parameter of CreateComputeEnvironment will be used.
 <note>
This object isn\'t applicable to jobs that are running on Fargate resources.
 </note>', 'refs' => [ 'ComputeResource$launchTemplate' => '
The launch template to use for your compute resources. Any other compute resource parameters that you specify in a CreateComputeEnvironment API operation override the same parameters in the launch template. You must specify either the launch template ID or launch template name in the request, but not both. For more information, see Launch template support in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResourceUpdate$launchTemplate' => '
The updated launch template to use for your compute resources. You must specify either the launch template ID or launch template name in the request, but not both. For more information, see Launch template support in the Batch User Guide. To remove the custom launch template and use the default launch template, set launchTemplateId or launchTemplateName member of the launch template specification to an empty string. Removing the launch template from a compute environment will not remove the AMI specified in the launch template. In order to update the AMI specified in a launch template, the updateToLatestImageVersion parameter must be set to true.

When updating a compute environment, changing the launch template requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', ], ], 'LinuxParameters' => [ 'base' => '
Linux-specific modifications that are applied to the container, such as details for device mappings.
', 'refs' => [ 'ContainerDetail$linuxParameters' => '
Linux-specific modifications that are applied to the container, such as details for device mappings.
', 'ContainerProperties$linuxParameters' => '
Linux-specific modifications that are applied to the container, such as details for device mappings.
', ], ], 'ListJobsFilterList' => [ 'base' => NULL, 'refs' => [ 'ListJobsRequest$filters' => '
The filter to apply to the query. Only one filter can be used at a time. When the filter is used, jobStatus is ignored. The filter doesn\'t apply to child jobs in an array or multi-node parallel (MNP) jobs. The results are sorted by the createdAt field, with the most recent jobs being first.

JOB_NAME

The value of the filter is a case-insensitive match for the job name. If the value ends with an asterisk (*), the filter matches any job name that begins with the string before the \'*\'. This corresponds to the jobName value. For example, test1 matches both Test1 and test1, and test1* matches both test1 and Test10. When the JOB_NAME filter is used, the results are grouped by the job name and version.

JOB_DEFINITION

The value for the filter is the name or Amazon Resource Name (ARN) of the job definition. This corresponds to the jobDefinition value. The value is case sensitive. When the value for the filter is the job definition name, the results include all the jobs that used any revision of that job definition name. If the value ends with an asterisk (*), the filter matches any job definition name that begins with the string before the \'*\'. For example, jd1 matches only jd1, and jd1* matches both jd1 and jd1A. The version of the job definition that\'s used doesn\'t affect the sort order. When the JOB_DEFINITION filter is used and the ARN is used (which is in the form arn:${Partition}:batch:${Region}:${Account}:job-definition/${JobDefinitionName}:${Revision}), the results include jobs that used the specified revision of the job definition. Asterisk (*) isn\'t supported when the ARN is used.

BEFORE_CREATED_AT

The value for the filter is the time that\'s before the job was created. This corresponds to the createdAt value. The value is a string representation of the number of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.

AFTER_CREATED_AT

The value for the filter is the time that\'s after the job was created. This corresponds to the createdAt value. The value is a string representation of the number of milliseconds since 00:00:00 UTC (midnight) on January 1, 1970.

', ], ], 'ListJobsRequest' => [ 'base' => '
Contains the parameters for ListJobs.
', 'refs' => [], ], 'ListJobsResponse' => [ 'base' => NULL, 'refs' => [], ], 'ListSchedulingPoliciesRequest' => [ 'base' => '
Contains the parameters for ListSchedulingPolicies.
', 'refs' => [], ], 'ListSchedulingPoliciesResponse' => [ 'base' => NULL, 'refs' => [], ], 'ListTagsForResourceRequest' => [ 'base' => '
Contains the parameters for ListTagsForResource.
', 'refs' => [], ], 'ListTagsForResourceResponse' => [ 'base' => NULL, 'refs' => [], ], 'LogConfiguration' => [ 'base' => '
Log configuration options to send to a custom log driver for the container.
', 'refs' => [ 'ContainerDetail$logConfiguration' => '
The log configuration specification for the container.

This parameter maps to LogConfig in the Create a container section of the Docker Remote API and the --log-driver option to docker run. By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a different logging driver than the Docker daemon by specifying a log driver with this parameter in the container definition. To use a different logging driver for a container, the log system must be configured properly on the container instance. Or, alternatively, it must be configured on a different log server for remote logging options. For more information on the options for different supported log drivers, see Configure logging drivers in the Docker documentation.
 <note>
Batch currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type). Additional log drivers might be available in future releases of the Amazon ECS container agent.
 </note>
This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version | grep "Server API version"
 <note>
The Amazon ECS container agent running on a container instance must register the logging drivers available on that instance with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide.
 </note>', 'ContainerProperties$logConfiguration' => '
The log configuration specification for the container.

This parameter maps to LogConfig in the Create a container section of the Docker Remote API and the --log-driver option to docker run. By default, containers use the same logging driver that the Docker daemon uses. However the container might use a different logging driver than the Docker daemon by specifying a log driver with this parameter in the container definition. To use a different logging driver for a container, the log system must be configured properly on the container instance (or on a different log server for remote logging options). For more information on the options for different supported log drivers, see Configure logging drivers in the Docker documentation.
 <note>
Batch currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type).
 </note>
This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version | grep "Server API version"
 <note>
The Amazon ECS container agent running on a container instance must register the logging drivers available on that instance with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the Amazon Elastic Container Service Developer Guide.
 </note>', ], ], 'LogConfigurationOptionsMap' => [ 'base' => NULL, 'refs' => [ 'LogConfiguration$options' => '
The configuration options to send to the log driver. This parameter requires version 1.19 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version | grep "Server API version"
', ], ], 'LogDriver' => [ 'base' => NULL, 'refs' => [ 'LogConfiguration$logDriver' => '
The log driver to use for the container. The valid values that are listed for this parameter are log drivers that the Amazon ECS container agent can communicate with by default.

The supported log drivers are awslogs, fluentd, gelf, json-file, journald, logentries, syslog, and splunk.
 <note>
Jobs that are running on Fargate resources are restricted to the awslogs and splunk log drivers.
 </note>

awslogs

Specifies the Amazon CloudWatch Logs logging driver. For more information, see Using the awslogs log driver in the Batch User Guide and Amazon CloudWatch Logs logging driver in the Docker documentation.

fluentd

Specifies the Fluentd logging driver. For more information including usage and options, see Fluentd logging driver in the Docker documentation.

gelf

Specifies the Graylog Extended Format (GELF) logging driver. For more information including usage and options, see Graylog Extended Format logging driver in the Docker documentation.

journald

Specifies the journald logging driver. For more information including usage and options, see Journald logging driver in the Docker documentation.

json-file

Specifies the JSON file logging driver. For more information including usage and options, see JSON File logging driver in the Docker documentation.

splunk

Specifies the Splunk logging driver. For more information including usage and options, see Splunk logging driver in the Docker documentation.

syslog

Specifies the syslog logging driver. For more information including usage and options, see Syslog logging driver in the Docker documentation.

 <note>
If you have a custom driver that\'s not listed earlier that you want to work with the Amazon ECS container agent, you can fork the Amazon ECS container agent project that\'s available on GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that you want to have included. However, Amazon Web Services doesn\'t currently support running modified copies of this software.
 </note>
This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version | grep "Server API version"
', ], ], 'Long' => [ 'base' => NULL, 'refs' => [ 'AttemptDetail$startedAt' => '
The Unix timestamp (in milliseconds) for when the attempt was started (when the attempt transitioned from the STARTING state to the RUNNING state).
', 'AttemptDetail$stoppedAt' => '
The Unix timestamp (in milliseconds) for when the attempt was stopped (when the attempt transitioned from the RUNNING state to a terminal state, such as SUCCEEDED or FAILED).
', 'EksAttemptDetail$startedAt' => '
The Unix timestamp (in milliseconds) for when the attempt was started (when the attempt transitioned from the STARTING state to the RUNNING state).
', 'EksAttemptDetail$stoppedAt' => '
The Unix timestamp (in milliseconds) for when the attempt was stopped. This happens when the attempt transitioned from the RUNNING state to a terminal state, such as SUCCEEDED or FAILED.
', 'EksContainerSecurityContext$runAsUser' => '
When this parameter is specified, the container is run as the specified user ID (uid). If this parameter isn\'t specified, the default is the user that\'s specified in the image metadata. This parameter maps to RunAsUser and MustRanAs policy in the Users and groups pod security policies in the Kubernetes documentation.
', 'EksContainerSecurityContext$runAsGroup' => '
When this parameter is specified, the container is run as the specified group ID (gid). If this parameter isn\'t specified, the default is the group that\'s specified in the image metadata. This parameter maps to RunAsGroup and MustRunAs policy in the Users and groups pod security policies in the Kubernetes documentation.
', 'JobDetail$createdAt' => '
The Unix timestamp (in milliseconds) for when the job was created. For non-array jobs and parent array jobs, this is when the job entered the SUBMITTED state. This is specifically at the time SubmitJob was called. For array child jobs, this is when the child job was spawned by its parent and entered the PENDING state.
', 'JobDetail$startedAt' => '
The Unix timestamp (in milliseconds) for when the job was started. More specifically, it\'s when the job transitioned from the STARTING state to the RUNNING state. This parameter isn\'t provided for child jobs of array jobs or multi-node parallel jobs.
', 'JobDetail$stoppedAt' => '
The Unix timestamp (in milliseconds) for when the job was stopped. More specifically, it\'s when the job transitioned from the RUNNING state to a terminal state, such as SUCCEEDED or FAILED.
', 'JobSummary$createdAt' => '
The Unix timestamp (in milliseconds) for when the job was created. For non-array jobs and parent array jobs, this is when the job entered the SUBMITTED state (at the time SubmitJob was called). For array child jobs, this is when the child job was spawned by its parent and entered the PENDING state.
', 'JobSummary$startedAt' => '
The Unix timestamp for when the job was started. More specifically, it\'s when the job transitioned from the STARTING state to the RUNNING state.
', 'JobSummary$stoppedAt' => '
The Unix timestamp for when the job was stopped. More specifically, it\'s when the job transitioned from the RUNNING state to a terminal state, such as SUCCEEDED or FAILED.
', ], ], 'MountPoint' => [ 'base' => '
Details for a Docker volume mount point that\'s used in a job\'s container properties. This parameter maps to Volumes in the Create a container section of the Docker Remote API and the --volume option to docker run.
', 'refs' => [ 'MountPoints$member' => NULL, ], ], 'MountPoints' => [ 'base' => NULL, 'refs' => [ 'ContainerDetail$mountPoints' => '
The mount points for data volumes in your container.
', 'ContainerProperties$mountPoints' => '
The mount points for data volumes in your container. This parameter maps to Volumes in the Create a container section of the Docker Remote API and the --volume option to docker run.
', ], ], 'NetworkConfiguration' => [ 'base' => '
The network configuration for jobs that are running on Fargate resources. Jobs that are running on EC2 resources must not specify this parameter.
', 'refs' => [ 'ContainerDetail$networkConfiguration' => '
The network configuration for jobs that are running on Fargate resources. Jobs that are running on EC2 resources must not specify this parameter.
', 'ContainerProperties$networkConfiguration' => '
The network configuration for jobs that are running on Fargate resources. Jobs that are running on EC2 resources must not specify this parameter.
', ], ], 'NetworkInterface' => [ 'base' => '
An object that represents the elastic network interface for a multi-node parallel job node.
', 'refs' => [ 'NetworkInterfaceList$member' => NULL, ], ], 'NetworkInterfaceList' => [ 'base' => NULL, 'refs' => [ 'AttemptContainerDetail$networkInterfaces' => '
The network interfaces that are associated with the job attempt.
', 'ContainerDetail$networkInterfaces' => '
The network interfaces that are associated with the job.
', ], ], 'NodeDetails' => [ 'base' => '
An object that represents the details of a multi-node parallel job node.
', 'refs' => [ 'JobDetail$nodeDetails' => '
An object that represents the details of a node that\'s associated with a multi-node parallel job.
', ], ], 'NodeOverrides' => [ 'base' => '
An object that represents any node overrides to a job definition that\'s used in a SubmitJob API operation.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t provide it for these jobs. Rather, use containerOverrides instead.
 </note>', 'refs' => [ 'SubmitJobRequest$nodeOverrides' => '
A list of node overrides in JSON format that specify the node range to target and the container overrides for that node range.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources; use containerOverrides instead.
 </note>', ], ], 'NodeProperties' => [ 'base' => '
An object that represents the node properties of a multi-node parallel job.
 <note>
Node properties can\'t be specified for Amazon EKS based job definitions.
 </note>', 'refs' => [ 'JobDefinition$nodeProperties' => '
An object with various properties that are specific to multi-node parallel jobs. Valid values are containerProperties, eksProperties, and nodeProperties. Only one can be specified.
 <note>
If the job runs on Fargate resources, don\'t specify nodeProperties. Use containerProperties instead.
 </note>', 'JobDetail$nodeProperties' => '
An object that represents the node properties of a multi-node parallel job.
 <note>
This isn\'t applicable to jobs that are running on Fargate resources.
 </note>', 'RegisterJobDefinitionRequest$nodeProperties' => '
An object with various properties specific to multi-node parallel jobs. If you specify node properties for a job, it becomes a multi-node parallel job. For more information, see Multi-node Parallel Jobs in the Batch User Guide. If the job definition\'s type parameter is container, then you must specify either containerProperties or nodeProperties.
 <note>
If the job runs on Fargate resources, then you must not specify nodeProperties; use containerProperties instead.
 </note> <note>
If the job runs on Amazon EKS resources, then you must not specify nodeProperties.
 </note>', ], ], 'NodePropertiesSummary' => [ 'base' => '
An object that represents the properties of a node that\'s associated with a multi-node parallel job.
', 'refs' => [ 'JobSummary$nodeProperties' => '
The node properties for a single node in a job summary list.
 <note>
This isn\'t applicable to jobs that are running on Fargate resources.
 </note>', ], ], 'NodePropertyOverride' => [ 'base' => '
The object that represents any node overrides to a job definition that\'s used in a SubmitJob API operation.
', 'refs' => [ 'NodePropertyOverrides$member' => NULL, ], ], 'NodePropertyOverrides' => [ 'base' => NULL, 'refs' => [ 'NodeOverrides$nodePropertyOverrides' => '
The node property overrides for the job.
', ], ], 'NodeRangeProperties' => [ 'base' => NULL, 'refs' => [ 'NodeProperties$nodeRangeProperties' => '
A list of node ranges and their properties that are associated with a multi-node parallel job.
', ], ], 'NodeRangeProperty' => [ 'base' => '
An object that represents the properties of the node range for a multi-node parallel job.
', 'refs' => [ 'NodeRangeProperties$member' => NULL, ], ], 'OrchestrationType' => [ 'base' => NULL, 'refs' => [ 'ComputeEnvironmentDetail$containerOrchestrationType' => '
The orchestration type of the compute environment. The valid values are ECS (default) or EKS.
', 'JobDefinition$containerOrchestrationType' => '
The orchestration type of the compute environment. The valid values are ECS (default) or EKS.
', ], ], 'ParametersMap' => [ 'base' => NULL, 'refs' => [ 'JobDefinition$parameters' => '
Default parameters or parameter substitution placeholders that are set in the job definition. Parameters are specified as a key-value pair mapping. Parameters in a SubmitJob request override any corresponding parameter defaults from the job definition. For more information about specifying parameters, see Job definition parameters in the Batch User Guide.
', 'JobDetail$parameters' => '
Additional parameters that are passed to the job that replace parameter substitution placeholders or override any corresponding parameter defaults from the job definition.
', 'RegisterJobDefinitionRequest$parameters' => '
Default parameter substitution placeholders to set in the job definition. Parameters are specified as a key-value pair mapping. Parameters in a SubmitJob request override any corresponding parameter defaults from the job definition.
', 'SubmitJobRequest$parameters' => '
Additional parameters passed to the job that replace parameter substitution placeholders that are set in the job definition. Parameters are specified as a key and value pair mapping. Parameters in a SubmitJob request override any corresponding parameter defaults from the job definition.
', ], ], 'PlatformCapability' => [ 'base' => NULL, 'refs' => [ 'PlatformCapabilityList$member' => NULL, ], ], 'PlatformCapabilityList' => [ 'base' => NULL, 'refs' => [ 'JobDefinition$platformCapabilities' => '
The platform capabilities required by the job definition. If no value is specified, it defaults to EC2. Jobs run on Fargate resources specify FARGATE.
', 'JobDetail$platformCapabilities' => '
The platform capabilities required by the job definition. If no value is specified, it defaults to EC2. Jobs run on Fargate resources specify FARGATE.
', 'RegisterJobDefinitionRequest$platformCapabilities' => '
The platform capabilities required by the job definition. If no value is specified, it defaults to EC2. To run the job on Fargate resources, specify FARGATE.
 <note>
If the job runs on Amazon EKS resources, then you must not specify platformCapabilities.
 </note>', ], ], 'Quantity' => [ 'base' => NULL, 'refs' => [ 'EksEmptyDir$sizeLimit' => '
The maximum size of the volume. By default, there\'s no maximum size defined.
', 'EksLimits$value' => NULL, 'EksRequests$value' => NULL, ], ], 'RegisterJobDefinitionRequest' => [ 'base' => '
Contains the parameters for RegisterJobDefinition.
', 'refs' => [], ], 'RegisterJobDefinitionResponse' => [ 'base' => NULL, 'refs' => [], ], 'ResourceRequirement' => [ 'base' => '
The type and amount of a resource to assign to a container. The supported resources include GPU, MEMORY, and VCPU.
', 'refs' => [ 'ResourceRequirements$member' => NULL, ], ], 'ResourceRequirements' => [ 'base' => NULL, 'refs' => [ 'ContainerDetail$resourceRequirements' => '
The type and amount of resources to assign to a container. The supported resources include GPU, MEMORY, and VCPU.
', 'ContainerOverrides$resourceRequirements' => '
The type and amount of resources to assign to a container. This overrides the settings in the job definition. The supported resources include GPU, MEMORY, and VCPU.
', 'ContainerProperties$resourceRequirements' => '
The type and amount of resources to assign to a container. The supported resources include GPU, MEMORY, and VCPU.
', ], ], 'ResourceType' => [ 'base' => NULL, 'refs' => [ 'ResourceRequirement$type' => '
The type of resource to assign to a container. The supported resources include GPU, MEMORY, and VCPU.
', ], ], 'RetryAction' => [ 'base' => NULL, 'refs' => [ 'EvaluateOnExit$action' => '
Specifies the action to take if all of the specified conditions (onStatusReason, onReason, and onExitCode) are met. The values aren\'t case sensitive.
', ], ], 'RetryStrategy' => [ 'base' => '
The retry strategy that\'s associated with a job. For more information, see Automated job retries in the Batch User Guide.
', 'refs' => [ 'JobDefinition$retryStrategy' => '
The retry strategy to use for failed jobs that are submitted with this job definition.
', 'JobDetail$retryStrategy' => '
The retry strategy to use for this job if an attempt fails.
', 'RegisterJobDefinitionRequest$retryStrategy' => '
The retry strategy to use for failed jobs that are submitted with this job definition. Any retry strategy that\'s specified during a SubmitJob operation overrides the retry strategy defined here. If a job is terminated due to a timeout, it isn\'t retried.
', 'SubmitJobRequest$retryStrategy' => '
The retry strategy to use for failed jobs from this SubmitJob operation. When a retry strategy is specified here, it overrides the retry strategy defined in the job definition.
', ], ], 'SchedulingPolicyDetail' => [ 'base' => '
An object that represents a scheduling policy.
', 'refs' => [ 'SchedulingPolicyDetailList$member' => NULL, ], ], 'SchedulingPolicyDetailList' => [ 'base' => NULL, 'refs' => [ 'DescribeSchedulingPoliciesResponse$schedulingPolicies' => '
The list of scheduling policies.
', ], ], 'SchedulingPolicyListingDetail' => [ 'base' => '
An object that contains the details of a scheduling policy that\'s returned in a ListSchedulingPolicy action.
', 'refs' => [ 'SchedulingPolicyListingDetailList$member' => NULL, ], ], 'SchedulingPolicyListingDetailList' => [ 'base' => NULL, 'refs' => [ 'ListSchedulingPoliciesResponse$schedulingPolicies' => '
A list of scheduling policies that match the request.
', ], ], 'Secret' => [ 'base' => '
An object that represents the secret to expose to your container. Secrets can be exposed to a container in the following ways:

To inject sensitive data into your containers as environment variables, use the secrets container definition parameter.

To reference sensitive information in the log configuration of a container, use the secretOptions container definition parameter.

For more information, see Specifying sensitive data in the Batch User Guide.
', 'refs' => [ 'SecretList$member' => NULL, ], ], 'SecretList' => [ 'base' => NULL, 'refs' => [ 'ContainerDetail$secrets' => '
The secrets to pass to the container. For more information, see Specifying sensitive data in the Batch User Guide.
', 'ContainerProperties$secrets' => '
The secrets for the container. For more information, see Specifying sensitive data in the Batch User Guide.
', 'LogConfiguration$secretOptions' => '
The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the Batch User Guide.
', ], ], 'ServerException' => [ 'base' => '
These errors are usually caused by a server issue.
', 'refs' => [], ], 'ShareAttributes' => [ 'base' => '
Specifies the weights for the fair share identifiers for the fair share policy. Fair share identifiers that aren\'t included have a default weight of 1.0.
', 'refs' => [ 'ShareAttributesList$member' => NULL, ], ], 'ShareAttributesList' => [ 'base' => NULL, 'refs' => [ 'FairsharePolicy$shareDistribution' => '
An array of SharedIdentifier objects that contain the weights for the fair share identifiers for the fair share policy. Fair share identifiers that aren\'t included have a default weight of 1.0.
', ], ], 'String' => [ 'base' => NULL, 'refs' => [ 'ArrayJobStatusSummary$key' => NULL, 'AttemptContainerDetail$containerInstanceArn' => '
The Amazon Resource Name (ARN) of the Amazon ECS container instance that hosts the job attempt.
', 'AttemptContainerDetail$taskArn' => '
The Amazon Resource Name (ARN) of the Amazon ECS task that\'s associated with the job attempt. Each container attempt receives a task ARN when they reach the STARTING status.
', 'AttemptContainerDetail$reason' => '
A short (255 max characters) human-readable string to provide additional details for a running or stopped container.
', 'AttemptContainerDetail$logStreamName' => '
The name of the CloudWatch Logs log stream that\'s associated with the container. The log group for Batch jobs is /aws/batch/job. Each container attempt receives a log stream name when they reach the RUNNING status.
', 'AttemptDetail$statusReason' => '
A short, human-readable string to provide additional details for the current status of the job attempt.
', 'CancelJobRequest$jobId' => '
The Batch job ID of the job to cancel.
', 'CancelJobRequest$reason' => '
A message to attach to the job that explains the reason for canceling it. This message is returned by future DescribeJobs operations on the job. This message is also recorded in the Batch activity logs.
', 'ClientException$message' => NULL, 'ComputeEnvironmentDetail$computeEnvironmentName' => '
The name of the compute environment. It can be up to 128 characters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_).
', 'ComputeEnvironmentDetail$computeEnvironmentArn' => '
The Amazon Resource Name (ARN) of the compute environment.
', 'ComputeEnvironmentDetail$ecsClusterArn' => '
The Amazon Resource Name (ARN) of the underlying Amazon ECS cluster that the compute environment uses.
', 'ComputeEnvironmentDetail$statusReason' => '
A short, human-readable string to provide additional details for the current status of the compute environment.
', 'ComputeEnvironmentDetail$serviceRole' => '
The service role that\'s associated with the compute environment that allows Batch to make calls to Amazon Web Services API operations on your behalf. For more information, see Batch service IAM role in the Batch User Guide.
', 'ComputeEnvironmentDetail$uuid' => '
Unique identifier for the compute environment.
', 'ComputeEnvironmentOrder$computeEnvironment' => '
The Amazon Resource Name (ARN) of the compute environment.
', 'ComputeResource$imageId' => '
The Amazon Machine Image (AMI) ID used for instances launched in the compute environment. This parameter is overridden by the imageIdOverride member of the Ec2Configuration structure.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note> <note>
The AMI that you choose for a compute environment must match the architecture of the instance types that you intend to use for that compute environment. For example, if your compute environment uses A1 instance types, the compute resource AMI that you choose must support ARM instances. Amazon ECS vends both x86 and ARM versions of the Amazon ECS-optimized Amazon Linux 2 AMI. For more information, see Amazon ECS-optimized Amazon Linux 2 AMI in the Amazon Elastic Container Service Developer Guide.
 </note>', 'ComputeResource$ec2KeyPair' => '
The Amazon EC2 key pair that\'s used for instances launched in the compute environment. You can use this key pair to log in to your instances with SSH.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResource$instanceRole' => '
The Amazon ECS instance profile applied to Amazon EC2 instances in a compute environment. You can specify the short name or full Amazon Resource Name (ARN) of an instance profile. For example,  ecsInstanceRole  or arn:aws:iam::<aws_account_id>:instance-profile/ecsInstanceRole . For more information, see Amazon ECS instance role in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResource$placementGroup' => '
The Amazon EC2 placement group to associate with your compute resources. If you intend to submit multi-node parallel jobs to your compute environment, you should consider creating a cluster placement group and associate it with your compute resources. This keeps your multi-node parallel job on a logical grouping of instances within a single Availability Zone with high network flow potential. For more information, see Placement groups in the Amazon EC2 User Guide for Linux Instances.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResource$spotIamFleetRole' => '
The Amazon Resource Name (ARN) of the Amazon EC2 Spot Fleet IAM role applied to a SPOT compute environment. This role is required if the allocation strategy set to BEST_FIT or if the allocation strategy isn\'t specified. For more information, see Amazon EC2 spot fleet role in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note> <important>
To tag your Spot Instances on creation, the Spot Fleet IAM role specified here must use the newer AmazonEC2SpotFleetTaggingRole managed policy. The previously recommended AmazonEC2SpotFleetRole managed policy doesn\'t have the required permissions to tag Spot Instances. For more information, see Spot instances not tagged on creation in the Batch User Guide.
 </important>', 'ComputeResourceUpdate$ec2KeyPair' => '
The Amazon EC2 key pair that\'s used for instances launched in the compute environment. You can use this key pair to log in to your instances with SSH. To remove the Amazon EC2 key pair, set this value to an empty string.

When updating a compute environment, changing the EC2 key pair requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResourceUpdate$instanceRole' => '
The Amazon ECS instance profile applied to Amazon EC2 instances in a compute environment. You can specify the short name or full Amazon Resource Name (ARN) of an instance profile. For example,  ecsInstanceRole  or arn:aws:iam::<aws_account_id>:instance-profile/ecsInstanceRole . For more information, see Amazon ECS instance role in the Batch User Guide.

When updating a compute environment, changing this setting requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResourceUpdate$placementGroup' => '
The Amazon EC2 placement group to associate with your compute resources. If you intend to submit multi-node parallel jobs to your compute environment, you should consider creating a cluster placement group and associate it with your compute resources. This keeps your multi-node parallel job on a logical grouping of instances within a single Availability Zone with high network flow potential. For more information, see Placement groups in the Amazon EC2 User Guide for Linux Instances.

When updating a compute environment, changing the placement group requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResourceUpdate$imageId' => '
The Amazon Machine Image (AMI) ID used for instances launched in the compute environment. This parameter is overridden by the imageIdOverride member of the Ec2Configuration structure. To remove the custom AMI ID and use the default AMI ID, set this value to an empty string.

When updating a compute environment, changing the AMI ID requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note> <note>
The AMI that you choose for a compute environment must match the architecture of the instance types that you intend to use for that compute environment. For example, if your compute environment uses A1 instance types, the compute resource AMI that you choose must support ARM instances. Amazon ECS vends both x86 and ARM versions of the Amazon ECS-optimized Amazon Linux 2 AMI. For more information, see Amazon ECS-optimized Amazon Linux 2 AMI in the Amazon Elastic Container Service Developer Guide.
 </note>', 'ContainerDetail$image' => '
The image used to start the container.
', 'ContainerDetail$jobRoleArn' => '
The Amazon Resource Name (ARN) that\'s associated with the job when run.
', 'ContainerDetail$executionRoleArn' => '
The Amazon Resource Name (ARN) of the execution role that Batch can assume. For more information, see Batch execution IAM role in the Batch User Guide.
', 'ContainerDetail$user' => '
The user name to use inside the container. This parameter maps to User in the Create a container section of the Docker Remote API and the --user option to docker run.
', 'ContainerDetail$reason' => '
A short (255 max characters) human-readable string to provide additional details for a running or stopped container.
', 'ContainerDetail$containerInstanceArn' => '
The Amazon Resource Name (ARN) of the container instance that the container is running on.
', 'ContainerDetail$taskArn' => '
The Amazon Resource Name (ARN) of the Amazon ECS task that\'s associated with the container job. Each container attempt receives a task ARN when they reach the STARTING status.
', 'ContainerDetail$logStreamName' => '
The name of the Amazon CloudWatch Logs log stream that\'s associated with the container. The log group for Batch jobs is /aws/batch/job. Each container attempt receives a log stream name when they reach the RUNNING status.
', 'ContainerDetail$instanceType' => '
The instance type of the underlying host infrastructure of a multi-node parallel job.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources.
 </note>', 'ContainerOverrides$instanceType' => '
The instance type to use for a multi-node parallel job.
 <note>
This parameter isn\'t applicable to single-node container jobs or jobs that run on Fargate resources, and shouldn\'t be provided.
 </note>', 'ContainerProperties$image' => '
The image used to start a container. This string is passed directly to the Docker daemon. Images in the Docker Hub registry are available by default. Other repositories are specified with  repository-url/image:tag . It can be 255 characters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), underscores (_), colons (:), periods (.), forward slashes (/), and number signs (#). This parameter maps to Image in the Create a container section of the Docker Remote API and the IMAGE parameter of docker run.
 <note>
Docker image architecture must match the processor architecture of the compute resources that they\'re scheduled on. For example, ARM-based Docker images can only run on ARM-based compute resources.
 </note>

Images in Amazon ECR Public repositories use the full registry/repository[:tag] or registry/repository[@digest] naming conventions. For example, public.ecr.aws/registry_alias/my-web-app:latest .

Images in Amazon ECR repositories use the full registry and repository URI (for example, 123456789012.dkr.ecr.<region-name>.amazonaws.com/<repository-name>).

Images in official repositories on Docker Hub use a single name (for example, ubuntu or mongo).

Images in other repositories on Docker Hub are qualified with an organization name (for example, amazon/amazon-ecs-agent).

Images in other online repositories are qualified further by a domain name (for example, quay.io/assemblyline/ubuntu).

', 'ContainerProperties$jobRoleArn' => '
The Amazon Resource Name (ARN) of the IAM role that the container can assume for Amazon Web Services permissions. For more information, see IAM roles for tasks in the Amazon Elastic Container Service Developer Guide.
', 'ContainerProperties$executionRoleArn' => '
The Amazon Resource Name (ARN) of the execution role that Batch can assume. For jobs that run on Fargate resources, you must provide an execution role. For more information, see Batch execution IAM role in the Batch User Guide.
', 'ContainerProperties$user' => '
The user name to use inside the container. This parameter maps to User in the Create a container section of the Docker Remote API and the --user option to docker run.
', 'ContainerProperties$instanceType' => '
The instance type to use for a multi-node parallel job. All node groups in a multi-node parallel job must use the same instance type.
 <note>
This parameter isn\'t applicable to single-node container jobs or jobs that run on Fargate resources, and shouldn\'t be provided.
 </note>', 'ContainerSummary$reason' => '
A short (255 max characters) human-readable string to provide additional details for a running or stopped container.
', 'CreateComputeEnvironmentRequest$computeEnvironmentName' => '
The name for your compute environment. It can be up to 128 characters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_).
', 'CreateComputeEnvironmentRequest$serviceRole' => '
The full Amazon Resource Name (ARN) of the IAM role that allows Batch to make calls to other Amazon Web Services services on your behalf. For more information, see Batch service IAM role in the Batch User Guide.
 <important>
If your account already created the Batch service-linked role, that role is used by default for your compute environment unless you specify a different role here. If the Batch service-linked role doesn\'t exist in your account, and no role is specified here, the service attempts to create the Batch service-linked role in your account.
 </important>
If your specified role has a path other than /, then you must specify either the full role ARN (recommended) or prefix the role name with the path. For example, if a role with the name bar has a path of /foo/, specify /foo/bar as the role name. For more information, see Friendly names and paths in the IAM User Guide.
 <note>
Depending on how you created your Batch service role, its ARN might contain the service-role path prefix. When you only specify the name of the service role, Batch assumes that your ARN doesn\'t use the service-role path prefix. Because of this, we recommend that you specify the full ARN of your service role when you create compute environments.
 </note>', 'CreateComputeEnvironmentResponse$computeEnvironmentName' => '
The name of the compute environment. It can be up to 128 characters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_).
', 'CreateComputeEnvironmentResponse$computeEnvironmentArn' => '
The Amazon Resource Name (ARN) of the compute environment.
', 'CreateJobQueueRequest$jobQueueName' => '
The name of the job queue. It can be up to 128 letters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_).
', 'CreateJobQueueRequest$schedulingPolicyArn' => '
The Amazon Resource Name (ARN) of the fair share scheduling policy. If this parameter is specified, the job queue uses a fair share scheduling policy. If this parameter isn\'t specified, the job queue uses a first in, first out (FIFO) scheduling policy. After a job queue is created, you can replace but can\'t remove the fair share scheduling policy. The format is aws:Partition:batch:Region:Account:scheduling-policy/Name . An example is aws:aws:batch:us-west-2:123456789012:scheduling-policy/MySchedulingPolicy.
', 'CreateJobQueueResponse$jobQueueName' => '
The name of the job queue.
', 'CreateJobQueueResponse$jobQueueArn' => '
The Amazon Resource Name (ARN) of the job queue.
', 'CreateSchedulingPolicyRequest$name' => '
The name of the scheduling policy. It can be up to 128 letters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_).
', 'CreateSchedulingPolicyResponse$name' => '
The name of the scheduling policy.
', 'CreateSchedulingPolicyResponse$arn' => '
The Amazon Resource Name (ARN) of the scheduling policy. The format is aws:Partition:batch:Region:Account:scheduling-policy/Name . For example, aws:aws:batch:us-west-2:123456789012:scheduling-policy/MySchedulingPolicy.
', 'DeleteComputeEnvironmentRequest$computeEnvironment' => '
The name or Amazon Resource Name (ARN) of the compute environment to delete.
', 'DeleteJobQueueRequest$jobQueue' => '
The short name or full Amazon Resource Name (ARN) of the queue to delete.
', 'DeleteSchedulingPolicyRequest$arn' => '
The Amazon Resource Name (ARN) of the scheduling policy to delete.
', 'DeregisterJobDefinitionRequest$jobDefinition' => '
The name and revision (name:revision) or full Amazon Resource Name (ARN) of the job definition to deregister.
', 'DescribeComputeEnvironmentsRequest$nextToken' => '
The nextToken value returned from a previous paginated DescribeComputeEnvironments request where maxResults was used and the results exceeded the value of that parameter. Pagination continues from the end of the previous results that returned the nextToken value. This value is null when there are no more results to return.
 <note>
Treat this token as an opaque identifier that\'s only used to retrieve the next items in a list and not for other programmatic purposes.
 </note>', 'DescribeComputeEnvironmentsResponse$nextToken' => '
The nextToken value to include in a future DescribeComputeEnvironments request. When the results of a DescribeComputeEnvironments request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
', 'DescribeJobDefinitionsRequest$jobDefinitionName' => '
The name of the job definition to describe.
', 'DescribeJobDefinitionsRequest$status' => '
The status used to filter job definitions.
', 'DescribeJobDefinitionsRequest$nextToken' => '
The nextToken value returned from a previous paginated DescribeJobDefinitions request where maxResults was used and the results exceeded the value of that parameter. Pagination continues from the end of the previous results that returned the nextToken value. This value is null when there are no more results to return.
 <note>
Treat this token as an opaque identifier that\'s only used to retrieve the next items in a list and not for other programmatic purposes.
 </note>', 'DescribeJobDefinitionsResponse$nextToken' => '
The nextToken value to include in a future DescribeJobDefinitions request. When the results of a DescribeJobDefinitions request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
', 'DescribeJobQueuesRequest$nextToken' => '
The nextToken value returned from a previous paginated DescribeJobQueues request where maxResults was used and the results exceeded the value of that parameter. Pagination continues from the end of the previous results that returned the nextToken value. This value is null when there are no more results to return.
 <note>
Treat this token as an opaque identifier that\'s only used to retrieve the next items in a list and not for other programmatic purposes.
 </note>', 'DescribeJobQueuesResponse$nextToken' => '
The nextToken value to include in a future DescribeJobQueues request. When the results of a DescribeJobQueues request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
', 'Device$hostPath' => '
The path for the device on the host container instance.
', 'Device$containerPath' => '
The path inside the container that\'s used to expose the host device. By default, the hostPath value is used.
', 'EFSAuthorizationConfig$accessPointId' => '
The Amazon EFS access point ID to use. If an access point is specified, the root directory value specified in the EFSVolumeConfiguration must either be omitted or set to / which enforces the path set on the EFS access point. If an access point is used, transit encryption must be enabled in the EFSVolumeConfiguration. For more information, see Working with Amazon EFS access points in the Amazon Elastic File System User Guide.
', 'EFSVolumeConfiguration$fileSystemId' => '
The Amazon EFS file system ID to use.
', 'EFSVolumeConfiguration$rootDirectory' => '
The directory within the Amazon EFS file system to mount as the root directory inside the host. If this parameter is omitted, the root of the Amazon EFS volume is used instead. Specifying / has the same effect as omitting this parameter. The maximum length is 4,096 characters.
 <important>
If an EFS access point is specified in the authorizationConfig, the root directory parameter must either be omitted or set to /, which enforces the path set on the Amazon EFS access point.
 </important>', 'EksAttemptContainerDetail$reason' => '
A short (255 max characters) human-readable string to provide additional details for a running or stopped container.
', 'EksAttemptDetail$podName' => '
The name of the pod for this job attempt.
', 'EksAttemptDetail$nodeName' => '
The name of the node for this job attempt.
', 'EksAttemptDetail$statusReason' => '
A short, human-readable string to provide additional details for the current status of the job attempt.
', 'EksConfiguration$eksClusterArn' => '
The Amazon Resource Name (ARN) of the Amazon EKS cluster. An example is arn:aws:eks:us-east-1:123456789012:cluster/ClusterForBatch .
', 'EksConfiguration$kubernetesNamespace' => '
The namespace of the Amazon EKS cluster. Batch manages pods in this namespace. The value can\'t left empty or null. It must be fewer than 64 characters long, can\'t be set to default, can\'t start with "kube-," and must match this regular expression: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$. For more information, see Namespaces in the Kubernetes documentation.
', 'EksContainer$name' => '
The name of the container. If the name isn\'t specified, the default name "Default" is used. Each container in a pod must have a unique name.
', 'EksContainer$image' => '
The Docker image used to start the container.
', 'EksContainer$imagePullPolicy' => '
The image pull policy for the container. Supported values are Always, IfNotPresent, and Never. This parameter defaults to IfNotPresent. However, if the :latest tag is specified, it defaults to Always. For more information, see Updating images in the Kubernetes documentation.
', 'EksContainerDetail$name' => '
The name of the container. If the name isn\'t specified, the default name "Default" is used. Each container in a pod must have a unique name.
', 'EksContainerDetail$image' => '
The Docker image used to start the container.
', 'EksContainerDetail$imagePullPolicy' => '
The image pull policy for the container. Supported values are Always, IfNotPresent, and Never. This parameter defaults to Always if the :latest tag is specified, IfNotPresent otherwise. For more information, see Updating images in the Kubernetes documentation.
', 'EksContainerDetail$reason' => '
A short human-readable string to provide additional details for a running or stopped container. It can be up to 255 characters long.
', 'EksContainerEnvironmentVariable$name' => '
The name of the environment variable.
', 'EksContainerEnvironmentVariable$value' => '
The value of the environment variable.
', 'EksContainerOverride$image' => '
The override of the Docker image that\'s used to start the container.
', 'EksContainerVolumeMount$name' => '
The name the volume mount. This must match the name of one of the volumes in the pod.
', 'EksContainerVolumeMount$mountPath' => '
The path on the container where the volume is mounted.
', 'EksEmptyDir$medium' => '
The medium to store the volume. The default value is an empty string, which uses the storage of the node.

""

 (Default) Use the disk storage of the node.

"Memory"

Use the tmpfs volume that\'s backed by the RAM of the node. Contents of the volume are lost when the node reboots, and any storage on the volume counts against the container\'s memory limit.

', 'EksHostPath$path' => '
The path of the file or directory on the host to mount into containers on the pod.
', 'EksLabelsMap$key' => NULL, 'EksLabelsMap$value' => NULL, 'EksLimits$key' => NULL, 'EksPodProperties$serviceAccountName' => '
The name of the service account that\'s used to run the pod. For more information, see Kubernetes service accounts and Configure a Kubernetes service account to assume an IAM role in the Amazon EKS User Guide and Configure service accounts for pods in the Kubernetes documentation.
', 'EksPodProperties$dnsPolicy' => '
The DNS policy for the pod. The default value is ClusterFirst. If the hostNetwork parameter is not specified, the default is ClusterFirstWithHostNet. ClusterFirst indicates that any DNS query that does not match the configured cluster domain suffix is forwarded to the upstream nameserver inherited from the node. For more information, see Pod\'s DNS policy in the Kubernetes documentation.

Valid values: Default | ClusterFirst | ClusterFirstWithHostNet
', 'EksPodPropertiesDetail$serviceAccountName' => '
The name of the service account that\'s used to run the pod. For more information, see Kubernetes service accounts and Configure a Kubernetes service account to assume an IAM role in the Amazon EKS User Guide and Configure service accounts for pods in the Kubernetes documentation.
', 'EksPodPropertiesDetail$dnsPolicy' => '
The DNS policy for the pod. The default value is ClusterFirst. If the hostNetwork parameter is not specified, the default is ClusterFirstWithHostNet. ClusterFirst indicates that any DNS query that does not match the configured cluster domain suffix is forwarded to the upstream nameserver inherited from the node. If no value was specified for dnsPolicy in the RegisterJobDefinition API operation, then no value will be returned for dnsPolicy by either of DescribeJobDefinitions or DescribeJobs API operations. The pod spec setting will contain either ClusterFirst or ClusterFirstWithHostNet, depending on the value of the hostNetwork parameter. For more information, see Pod\'s DNS policy in the Kubernetes documentation.

Valid values: Default | ClusterFirst | ClusterFirstWithHostNet
', 'EksPodPropertiesDetail$podName' => '
The name of the pod for this job.
', 'EksPodPropertiesDetail$nodeName' => '
The name of the node for this job.
', 'EksRequests$key' => NULL, 'EksSecret$secretName' => '
The name of the secret. The name must be allowed as a DNS subdomain name. For more information, see DNS subdomain names in the Kubernetes documentation.
', 'EksVolume$name' => '
The name of the volume. The name must be allowed as a DNS subdomain name. For more information, see DNS subdomain names in the Kubernetes documentation.
', 'EvaluateOnExit$onStatusReason' => '
Contains a glob pattern to match against the StatusReason returned for a job. The pattern can contain up to 512 characters. It can contain letters, numbers, periods (.), colons (:), and white spaces (including spaces or tabs). It can optionally end with an asterisk (*) so that only the start of the string needs to be an exact match.
', 'EvaluateOnExit$onReason' => '
Contains a glob pattern to match against the Reason returned for a job. The pattern can contain up to 512 characters. It can contain letters, numbers, periods (.), colons (:), and white space (including spaces and tabs). It can optionally end with an asterisk (*) so that only the start of the string needs to be an exact match.
', 'EvaluateOnExit$onExitCode' => '
Contains a glob pattern to match against the decimal representation of the ExitCode returned for a job. The pattern can be up to 512 characters long. It can contain only numbers, and can end with an asterisk (*) so that only the start of the string needs to be an exact match.

The string can contain up to 512 characters.
', 'FargatePlatformConfiguration$platformVersion' => '
The Fargate platform version where the jobs are running. A platform version is specified only for jobs that are running on Fargate resources. If one isn\'t specified, the LATEST platform version is used by default. This uses a recent, approved version of the Fargate platform for compute resources. For more information, see Fargate platform versions in the Amazon Elastic Container Service Developer Guide.
', 'Host$sourcePath' => '
The path on the host container instance that\'s presented to the container. If this parameter is empty, then the Docker daemon has assigned a host path for you. If this parameter contains a file location, then the data volume persists at the specified location on the host container instance until you delete it manually. If the source path location doesn\'t exist on the host container instance, the Docker daemon creates it. If the location does exist, the contents of the source path folder are exported.
 <note>
This parameter isn\'t applicable to jobs that run on Fargate resources. Don\'t provide this for these jobs.
 </note>', 'JobDefinition$jobDefinitionName' => '
The name of the job definition.
', 'JobDefinition$jobDefinitionArn' => '
The Amazon Resource Name (ARN) for the job definition.
', 'JobDefinition$status' => '
The status of the job definition.
', 'JobDefinition$type' => '
The type of job definition. It\'s either container or multinode. If the job is run on Fargate resources, then multinode isn\'t supported. For more information about multi-node parallel jobs, see Creating a multi-node parallel job definition in the Batch User Guide.
', 'JobDependency$jobId' => '
The job ID of the Batch job that\'s associated with this dependency.
', 'JobDetail$jobArn' => '
The Amazon Resource Name (ARN) of the job.
', 'JobDetail$jobName' => '
The job name.
', 'JobDetail$jobId' => '
The job ID.
', 'JobDetail$jobQueue' => '
The Amazon Resource Name (ARN) of the job queue that the job is associated with.
', 'JobDetail$shareIdentifier' => '
The share identifier for the job.
', 'JobDetail$statusReason' => '
A short, human-readable string to provide more details for the current status of the job.
', 'JobDetail$jobDefinition' => '
The Amazon Resource Name (ARN) of the job definition that this job uses.
', 'JobQueueDetail$jobQueueName' => '
The job queue name.
', 'JobQueueDetail$jobQueueArn' => '
The Amazon Resource Name (ARN) of the job queue.
', 'JobQueueDetail$schedulingPolicyArn' => '
The Amazon Resource Name (ARN) of the scheduling policy. The format is aws:Partition:batch:Region:Account:scheduling-policy/Name . For example, aws:aws:batch:us-west-2:123456789012:scheduling-policy/MySchedulingPolicy.
', 'JobQueueDetail$statusReason' => '
A short, human-readable string to provide additional details for the current status of the job queue.
', 'JobSummary$jobArn' => '
The Amazon Resource Name (ARN) of the job.
', 'JobSummary$jobId' => '
The job ID.
', 'JobSummary$jobName' => '
The job name.
', 'JobSummary$statusReason' => '
A short, human-readable string to provide more details for the current status of the job.
', 'JobSummary$jobDefinition' => '
The Amazon Resource Name (ARN) of the job definition.
', 'KeyValuePair$name' => '
The name of the key-value pair. For environment variables, this is the name of the environment variable.
', 'KeyValuePair$value' => '
The value of the key-value pair. For environment variables, this is the value of the environment variable.
', 'KeyValuesPair$name' => '
The name of the filter. Filter names are case sensitive.
', 'LaunchTemplateSpecification$launchTemplateId' => '
The ID of the launch template.
', 'LaunchTemplateSpecification$launchTemplateName' => '
The name of the launch template.
', 'LaunchTemplateSpecification$version' => '
The version number of the launch template, $Latest, or $Default.

If the value is $Latest, the latest version of the launch template is used. If the value is $Default, the default version of the launch template is used.
 <important>
If the AMI ID that\'s used in a compute environment is from the launch template, the AMI isn\'t changed when the compute environment is updated. It\'s only changed if the updateToLatestImageVersion parameter for the compute environment is set to true. During an infrastructure update, if either $Latest or $Default is specified, Batch re-evaluates the launch template version, and it might use a different version of the launch template. This is the case even if the launch template isn\'t specified in the update. When updating a compute environment, changing the launch template requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
 </important>
Default: $Default.
', 'ListJobsRequest$jobQueue' => '
The name or full Amazon Resource Name (ARN) of the job queue used to list jobs.
', 'ListJobsRequest$arrayJobId' => '
The job ID for an array job. Specifying an array job ID with this parameter lists all child jobs from within the specified array.
', 'ListJobsRequest$multiNodeJobId' => '
The job ID for a multi-node parallel job. Specifying a multi-node parallel job ID with this parameter lists all nodes that are associated with the specified job.
', 'ListJobsRequest$nextToken' => '
The nextToken value returned from a previous paginated ListJobs request where maxResults was used and the results exceeded the value of that parameter. Pagination continues from the end of the previous results that returned the nextToken value. This value is null when there are no more results to return.
 <note>
Treat this token as an opaque identifier that\'s only used to retrieve the next items in a list and not for other programmatic purposes.
 </note>', 'ListJobsResponse$nextToken' => '
The nextToken value to include in a future ListJobs request. When the results of a ListJobs request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
', 'ListSchedulingPoliciesRequest$nextToken' => '
The nextToken value that\'s returned from a previous paginated ListSchedulingPolicies request where maxResults was used and the results exceeded the value of that parameter. Pagination continues from the end of the previous results that returned the nextToken value. This value is null when there are no more results to return.
 <note>
Treat this token as an opaque identifier that\'s only used to retrieve the next items in a list and not for other programmatic purposes.
 </note>', 'ListSchedulingPoliciesResponse$nextToken' => '
The nextToken value to include in a future ListSchedulingPolicies request. When the results of a ListSchedulingPolicies request exceed maxResults, this value can be used to retrieve the next page of results. This value is null when there are no more results to return.
', 'ListTagsForResourceRequest$resourceArn' => '
The Amazon Resource Name (ARN) that identifies the resource that tags are listed for. Batch resources that support tags are compute environments, jobs, job definitions, job queues, and scheduling policies. ARNs for child jobs of array and multi-node parallel (MNP) jobs aren\'t supported.
', 'LogConfigurationOptionsMap$key' => NULL, 'LogConfigurationOptionsMap$value' => NULL, 'MountPoint$containerPath' => '
The path on the container where the host volume is mounted.
', 'MountPoint$sourceVolume' => '
The name of the volume to mount.
', 'NetworkInterface$attachmentId' => '
The attachment ID for the network interface.
', 'NetworkInterface$ipv6Address' => '
The private IPv6 address for the network interface.
', 'NetworkInterface$privateIpv4Address' => '
The private IPv4 address for the network interface.
', 'NodePropertyOverride$targetNodes' => '
The range of nodes, using node index values, that\'s used to override. A range of 0:3 indicates nodes with index values of 0 through 3. If the starting range value is omitted (:n), then 0 is used to start the range. If the ending range value is omitted (n:), then the highest possible node index is used to end the range.
', 'NodeRangeProperty$targetNodes' => '
The range of nodes, using node index values. A range of 0:3 indicates nodes with index values of 0 through 3. If the starting range value is omitted (:n), then 0 is used to start the range. If the ending range value is omitted (n:), then the highest possible node index is used to end the range. Your accumulative node ranges must account for all nodes (0:n). You can nest node ranges (for example, 0:10 and 4:5). In this case, the 4:5 range properties override the 0:10 properties.
', 'ParametersMap$key' => NULL, 'ParametersMap$value' => NULL, 'RegisterJobDefinitionRequest$jobDefinitionName' => '
The name of the job definition to register. It can be up to 128 letters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_).
', 'RegisterJobDefinitionResponse$jobDefinitionName' => '
The name of the job definition.
', 'RegisterJobDefinitionResponse$jobDefinitionArn' => '
The Amazon Resource Name (ARN) of the job definition.
', 'ResourceRequirement$value' => '
The quantity of the specified resource to reserve for the container. The values vary based on the type specified.

type="GPU"

The number of physical GPUs to reserve for the container. Make sure that the number of GPUs reserved for all containers in a job doesn\'t exceed the number of available GPUs on the compute resource that the job is launched on.
 <note>
GPUs aren\'t available for jobs that are running on Fargate resources.
 </note>

type="MEMORY"

The memory hard limit (in MiB) present to the container. This parameter is supported for jobs that are running on EC2 resources. If your container attempts to exceed the memory specified, the container is terminated. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run. You must specify at least 4 MiB of memory for a job. This is required but can be specified in several places for multi-node parallel (MNP) jobs. It must be specified for each node at least once. This parameter maps to Memory in the Create a container section of the Docker Remote API and the --memory option to docker run.
 <note>
If you\'re trying to maximize your resource utilization by providing your jobs as much memory as possible for a particular instance type, see Memory management in the Batch User Guide.
 </note>
For jobs that are running on Fargate resources, then value is the hard limit (in MiB), and must match one of the supported values and the VCPU values must be one of the values supported for that memory value.

value = 512

 VCPU = 0.25

value = 1024

 VCPU = 0.25 or 0.5

value = 2048

 VCPU = 0.25, 0.5, or 1

value = 3072

 VCPU = 0.5, or 1

value = 4096

 VCPU = 0.5, 1, or 2

value = 5120, 6144, or 7168

 VCPU = 1 or 2

value = 8192

 VCPU = 1, 2, or 4

value = 9216, 10240, 11264, 12288, 13312, 14336, or 15360

 VCPU = 2 or 4

value = 16384

 VCPU = 2, 4, or 8

value = 17408, 18432, 19456, 21504, 22528, 23552, 25600, 26624, 27648, 29696, or 30720

 VCPU = 4

value = 20480, 24576, or 28672

 VCPU = 4 or 8

value = 36864, 45056, 53248, or 61440

 VCPU = 8

value = 32768, 40960, 49152, or 57344

 VCPU = 8 or 16

value = 65536, 73728, 81920, 90112, 98304, 106496, 114688, or 122880

 VCPU = 16

type="VCPU"

The number of vCPUs reserved for the container. This parameter maps to CpuShares in the Create a container section of the Docker Remote API and the --cpu-shares option to docker run. Each vCPU is equivalent to 1,024 CPU shares. For EC2 resources, you must specify at least one vCPU. This is required but can be specified in several places; it must be specified for each node at least once.

The default for the Fargate On-Demand vCPU resource count quota is 6 vCPUs. For more information about Fargate quotas, see Fargate quotas in the Amazon Web Services General Reference.

For jobs that are running on Fargate resources, then value must match one of the supported values and the MEMORY values must be one of the values supported for that VCPU value. The supported values are 0.25, 0.5, 1, 2, 4, 8, and 16

value = 0.25

 MEMORY = 512, 1024, or 2048

value = 0.5

 MEMORY = 1024, 2048, 3072, or 4096

value = 1

 MEMORY = 2048, 3072, 4096, 5120, 6144, 7168, or 8192

value = 2

 MEMORY = 4096, 5120, 6144, 7168, 8192, 9216, 10240, 11264, 12288, 13312, 14336, 15360, or 16384

value = 4

 MEMORY = 8192, 9216, 10240, 11264, 12288, 13312, 14336, 15360, 16384, 17408, 18432, 19456, 20480, 21504, 22528, 23552, 24576, 25600, 26624, 27648, 28672, 29696, or 30720

value = 8

 MEMORY = 16384, 20480, 24576, 28672, 32768, 36864, 40960, 45056, 49152, 53248, 57344, or 61440

value = 16

 MEMORY = 32768, 40960, 49152, 57344, 65536, 73728, 81920, 90112, 98304, 106496, 114688, or 122880

', 'SchedulingPolicyDetail$name' => '
The name of the scheduling policy.
', 'SchedulingPolicyDetail$arn' => '
The Amazon Resource Name (ARN) of the scheduling policy. An example is arn:aws:batch:us-east-1:123456789012:scheduling-policy/HighPriority .
', 'SchedulingPolicyListingDetail$arn' => '
Amazon Resource Name (ARN) of the scheduling policy.
', 'Secret$name' => '
The name of the secret.
', 'Secret$valueFrom' => '
The secret to expose to the container. The supported values are either the full Amazon Resource Name (ARN) of the Secrets Manager secret or the full ARN of the parameter in the Amazon Web Services Systems Manager Parameter Store.
 <note>
If the Amazon Web Services Systems Manager Parameter Store parameter exists in the same Region as the job you\'re launching, then you can use either the full Amazon Resource Name (ARN) or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
 </note>', 'ServerException$message' => NULL, 'ShareAttributes$shareIdentifier' => '
A fair share identifier or fair share identifier prefix. If the string ends with an asterisk (*), this entry specifies the weight factor to use for fair share identifiers that start with that prefix. The list of fair share identifiers in a fair share policy can\'t overlap. For example, you can\'t have one that specifies a shareIdentifier of UserA* and another that specifies a shareIdentifier of UserA-1.

There can be no more than 500 fair share identifiers active in a job queue.

The string is limited to 255 alphanumeric characters, and can be followed by an asterisk (*).
', 'StringList$member' => NULL, 'SubmitJobRequest$jobName' => '
The name of the job. It can be up to 128 letters long. The first character must be alphanumeric, can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_).
', 'SubmitJobRequest$jobQueue' => '
The job queue where the job is submitted. You can specify either the name or the Amazon Resource Name (ARN) of the queue.
', 'SubmitJobRequest$shareIdentifier' => '
The share identifier for the job. If the job queue doesn\'t have a scheduling policy, then this parameter must not be specified. If the job queue has a scheduling policy, then this parameter must be specified.
', 'SubmitJobRequest$jobDefinition' => '
The job definition used by this job. This value can be one of definition-name, definition-name:revision, or the Amazon Resource Name (ARN) for the job definition, with or without the revision (arn:aws:batch:region:account:job-definition/definition-name:revision , or arn:aws:batch:region:account:job-definition/definition-name ).

If the revision is not specified, then the latest active revision is used.
', 'SubmitJobResponse$jobArn' => '
The Amazon Resource Name (ARN) for the job.
', 'SubmitJobResponse$jobName' => '
The name of the job.
', 'SubmitJobResponse$jobId' => '
The unique identifier for the job.
', 'TagResourceRequest$resourceArn' => '
The Amazon Resource Name (ARN) of the resource that tags are added to. Batch resources that support tags are compute environments, jobs, job definitions, job queues, and scheduling policies. ARNs for child jobs of array and multi-node parallel (MNP) jobs aren\'t supported.
', 'TagsMap$key' => NULL, 'TagsMap$value' => NULL, 'TerminateJobRequest$jobId' => '
The Batch job ID of the job to terminate.
', 'TerminateJobRequest$reason' => '
A message to attach to the job that explains the reason for canceling it. This message is returned by future DescribeJobs operations on the job. This message is also recorded in the Batch activity logs.
', 'Tmpfs$containerPath' => '
The absolute file path in the container where the tmpfs volume is mounted.
', 'Ulimit$name' => '
The type of the ulimit.
', 'UntagResourceRequest$resourceArn' => '
The Amazon Resource Name (ARN) of the resource from which to delete tags. Batch resources that support tags are compute environments, jobs, job definitions, job queues, and scheduling policies. ARNs for child jobs of array and multi-node parallel (MNP) jobs aren\'t supported.
', 'UpdateComputeEnvironmentRequest$computeEnvironment' => '
The name or full Amazon Resource Name (ARN) of the compute environment to update.
', 'UpdateComputeEnvironmentRequest$serviceRole' => '
The full Amazon Resource Name (ARN) of the IAM role that allows Batch to make calls to other Amazon Web Services services on your behalf. For more information, see Batch service IAM role in the Batch User Guide.
 <important>
If the compute environment has a service-linked role, it can\'t be changed to use a regular IAM role. Likewise, if the compute environment has a regular IAM role, it can\'t be changed to use a service-linked role. To update the parameters for the compute environment that require an infrastructure update to change, the AWSServiceRoleForBatch service-linked role must be used. For more information, see Updating compute environments in the Batch User Guide.
 </important>
If your specified role has a path other than /, then you must either specify the full role ARN (recommended) or prefix the role name with the path.
 <note>
Depending on how you created your Batch service role, its ARN might contain the service-role path prefix. When you only specify the name of the service role, Batch assumes that your ARN doesn\'t use the service-role path prefix. Because of this, we recommend that you specify the full ARN of your service role when you create compute environments.
 </note>', 'UpdateComputeEnvironmentResponse$computeEnvironmentName' => '
The name of the compute environment. It can be up to 128 characters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_).
', 'UpdateComputeEnvironmentResponse$computeEnvironmentArn' => '
The Amazon Resource Name (ARN) of the compute environment.
', 'UpdateJobQueueRequest$jobQueue' => '
The name or the Amazon Resource Name (ARN) of the job queue.
', 'UpdateJobQueueRequest$schedulingPolicyArn' => '
Amazon Resource Name (ARN) of the fair share scheduling policy. Once a job queue is created, the fair share scheduling policy can be replaced but not removed. The format is aws:Partition:batch:Region:Account:scheduling-policy/Name . For example, aws:aws:batch:us-west-2:123456789012:scheduling-policy/MySchedulingPolicy.
', 'UpdateJobQueueResponse$jobQueueName' => '
The name of the job queue.
', 'UpdateJobQueueResponse$jobQueueArn' => '
The Amazon Resource Name (ARN) of the job queue.
', 'UpdateSchedulingPolicyRequest$arn' => '
The Amazon Resource Name (ARN) of the scheduling policy to update.
', 'Volume$name' => '
The name of the volume. It can be up to 255 characters long. It can contain uppercase and lowercase letters, numbers, hyphens (-), and underscores (_). This name is referenced in the sourceVolume parameter of container definition mountPoints.
', ], ], 'StringList' => [ 'base' => NULL, 'refs' => [ 'ComputeResource$instanceTypes' => '
The instances types that can be launched. You can specify instance families to launch any instance type within those families (for example, c5 or p3), or you can specify specific sizes within a family (such as c5.8xlarge). You can also choose optimal to select instance types (from the C4, M4, and R4 instance families) that match the demand of your job queues.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note> <note>
When you create a compute environment, the instance types that you select for the compute environment must share the same architecture. For example, you can\'t mix x86 and ARM instances in the same compute environment.
 </note> <note>
Currently, optimal uses instance types from the C4, M4, and R4 instance families. In Regions that don\'t have instance types from those instance families, instance types from the C5, M5, and R5 instance families are used.
 </note>', 'ComputeResource$subnets' => '
The VPC subnets where the compute resources are launched. These subnets must be within the same VPC. Fargate compute resources can contain up to 16 subnets. For more information, see VPCs and subnets in the Amazon VPC User Guide.
 <note>
Batch on Amazon EC2 and Batch on Amazon EKS support Local Zones. For more information, see  Local Zones in the Amazon EC2 User Guide for Linux Instances, Amazon EKS and Amazon Web Services Local Zones in the Amazon EKS User Guide and  Amazon ECS clusters in Local Zones, Wavelength Zones, and Amazon Web Services Outposts in the Amazon ECS Developer Guide.

Batch on Fargate doesn\'t currently support Local Zones.
 </note>', 'ComputeResource$securityGroupIds' => '
The Amazon EC2 security groups that are associated with instances launched in the compute environment. One or more security groups must be specified, either in securityGroupIds or using a launch template referenced in launchTemplate. This parameter is required for jobs that are running on Fargate resources and must contain at least one security group. Fargate doesn\'t support launch templates. If security groups are specified using both securityGroupIds and launchTemplate, the values in securityGroupIds are used.
', 'ComputeResourceUpdate$subnets' => '
The VPC subnets where the compute resources are launched. Fargate compute resources can contain up to 16 subnets. For Fargate compute resources, providing an empty list will be handled as if this parameter wasn\'t specified and no change is made. For EC2 compute resources, providing an empty list removes the VPC subnets from the compute resource. For more information, see VPCs and subnets in the Amazon VPC User Guide.

When updating a compute environment, changing the VPC subnets requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
 <note>
Batch on Amazon EC2 and Batch on Amazon EKS support Local Zones. For more information, see  Local Zones in the Amazon EC2 User Guide for Linux Instances, Amazon EKS and Amazon Web Services Local Zones in the Amazon EKS User Guide and  Amazon ECS clusters in Local Zones, Wavelength Zones, and Amazon Web Services Outposts in the Amazon ECS Developer Guide.

Batch on Fargate doesn\'t currently support Local Zones.
 </note>', 'ComputeResourceUpdate$securityGroupIds' => '
The Amazon EC2 security groups that are associated with instances launched in the compute environment. This parameter is required for Fargate compute resources, where it can contain up to 5 security groups. For Fargate compute resources, providing an empty list is handled as if this parameter wasn\'t specified and no change is made. For EC2 compute resources, providing an empty list removes the security groups from the compute resource.

When updating a compute environment, changing the EC2 security groups requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
', 'ComputeResourceUpdate$instanceTypes' => '
The instances types that can be launched. You can specify instance families to launch any instance type within those families (for example, c5 or p3), or you can specify specific sizes within a family (such as c5.8xlarge). You can also choose optimal to select instance types (from the C4, M4, and R4 instance families) that match the demand of your job queues.

When updating a compute environment, changing this setting requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note> <note>
When you create a compute environment, the instance types that you select for the compute environment must share the same architecture. For example, you can\'t mix x86 and ARM instances in the same compute environment.
 </note> <note>
Currently, optimal uses instance types from the C4, M4, and R4 instance families. In Regions that don\'t have instance types from those instance families, instance types from the C5, M5, and R5 instance families are used.
 </note>', 'ContainerDetail$command' => '
The command that\'s passed to the container.
', 'ContainerOverrides$command' => '
The command to send to the container that overrides the default command from the Docker image or the job definition.
', 'ContainerProperties$command' => '
The command that\'s passed to the container. This parameter maps to Cmd in the Create a container section of the Docker Remote API and the COMMAND parameter to docker run. For more information, see https://docs.docker.com/engine/reference/builder/#cmd.
', 'DescribeComputeEnvironmentsRequest$computeEnvironments' => '
A list of up to 100 compute environment names or full Amazon Resource Name (ARN) entries.
', 'DescribeJobDefinitionsRequest$jobDefinitions' => '
A list of up to 100 job definitions. Each entry in the list can either be an ARN in the format arn:aws:batch:${Region}:${Account}:job-definition/${JobDefinitionName}:${Revision} or a short version using the form ${JobDefinitionName}:${Revision}.
', 'DescribeJobQueuesRequest$jobQueues' => '
A list of up to 100 queue names or full queue Amazon Resource Name (ARN) entries.
', 'DescribeJobsRequest$jobs' => '
A list of up to 100 job IDs.
', 'DescribeSchedulingPoliciesRequest$arns' => '
A list of up to 100 scheduling policy Amazon Resource Name (ARN) entries.
', 'EksContainer$command' => '
The entrypoint for the container. This isn\'t run within a shell. If this isn\'t specified, the ENTRYPOINT of the container image is used. Environment variable references are expanded using the container\'s environment.

If the referenced environment variable doesn\'t exist, the reference in the command isn\'t changed. For example, if the reference is to "$(NAME1)" and the NAME1 environment variable doesn\'t exist, the command string will remain "$(NAME1)." $$ is replaced with $ and the resulting string isn\'t expanded. For example, $$(VAR_NAME) will be passed as $(VAR_NAME) whether or not the VAR_NAME environment variable exists. The entrypoint can\'t be updated. For more information, see ENTRYPOINT in the Dockerfile reference and Define a command and arguments for a container and Entrypoint in the Kubernetes documentation.
', 'EksContainer$args' => '
An array of arguments to the entrypoint. If this isn\'t specified, the CMD of the container image is used. This corresponds to the args member in the Entrypoint portion of the Pod in Kubernetes. Environment variable references are expanded using the container\'s environment.

If the referenced environment variable doesn\'t exist, the reference in the command isn\'t changed. For example, if the reference is to "$(NAME1)" and the NAME1 environment variable doesn\'t exist, the command string will remain "$(NAME1)." $$ is replaced with $, and the resulting string isn\'t expanded. For example, $$(VAR_NAME) is passed as $(VAR_NAME) whether or not the VAR_NAME environment variable exists. For more information, see CMD in the Dockerfile reference and Define a command and arguments for a pod in the Kubernetes documentation.
', 'EksContainerDetail$command' => '
The entrypoint for the container. For more information, see Entrypoint in the Kubernetes documentation.
', 'EksContainerDetail$args' => '
An array of arguments to the entrypoint. If this isn\'t specified, the CMD of the container image is used. This corresponds to the args member in the Entrypoint portion of the Pod in Kubernetes. Environment variable references are expanded using the container\'s environment.

If the referenced environment variable doesn\'t exist, the reference in the command isn\'t changed. For example, if the reference is to "$(NAME1)" and the NAME1 environment variable doesn\'t exist, the command string will remain "$(NAME1)". $$ is replaced with $ and the resulting string isn\'t expanded. For example, $$(VAR_NAME) is passed as $(VAR_NAME) whether or not the VAR_NAME environment variable exists. For more information, see CMD in the Dockerfile reference and Define a command and arguments for a pod in the Kubernetes documentation.
', 'EksContainerOverride$command' => '
The command to send to the container that overrides the default command from the Docker image or the job definition.
', 'EksContainerOverride$args' => '
The arguments to the entrypoint to send to the container that overrides the default arguments from the Docker image or the job definition. For more information, see CMD in the Dockerfile reference and Define a command an arguments for a pod in the Kubernetes documentation.
', 'KeyValuesPair$values' => '
The filter values.
', 'Tmpfs$mountOptions' => '
The list of tmpfs volume mount options.

Valid values: "defaults" | "ro" | "rw" | "suid" | "nosuid" | "dev" | "nodev" | "exec" | "noexec" | "sync" | "async" | "dirsync" | "remount" | "mand" | "nomand" | "atime" | "noatime" | "diratime" | "nodiratime" | "bind" | "rbind" | "unbindable" | "runbindable" | "private" | "rprivate" | "shared" | "rshared" | "slave" | "rslave" | "relatime" | "norelatime" | "strictatime" | "nostrictatime" | "mode" | "uid" | "gid" | "nr_inodes" | "nr_blocks" | "mpol"
', ], ], 'SubmitJobRequest' => [ 'base' => '
Contains the parameters for SubmitJob.
', 'refs' => [], ], 'SubmitJobResponse' => [ 'base' => NULL, 'refs' => [], ], 'TagKey' => [ 'base' => NULL, 'refs' => [ 'TagKeysList$member' => NULL, 'TagrisTagsMap$key' => NULL, ], ], 'TagKeysList' => [ 'base' => NULL, 'refs' => [ 'UntagResourceRequest$tagKeys' => '
The keys of the tags to be removed.
', ], ], 'TagResourceRequest' => [ 'base' => '
Contains the parameters for TagResource.
', 'refs' => [], ], 'TagResourceResponse' => [ 'base' => NULL, 'refs' => [], ], 'TagValue' => [ 'base' => NULL, 'refs' => [ 'TagrisTagsMap$value' => NULL, ], ], 'TagrisTagsMap' => [ 'base' => NULL, 'refs' => [ 'ComputeEnvironmentDetail$tags' => '
The tags applied to the compute environment.
', 'CreateComputeEnvironmentRequest$tags' => '
The tags that you apply to the compute environment to help you categorize and organize your resources. Each tag consists of a key and an optional value. For more information, see Tagging Amazon Web Services Resources in Amazon Web Services General Reference.

These tags can be updated or removed using the TagResource and UntagResource API operations. These tags don\'t propagate to the underlying compute resources.
', 'CreateJobQueueRequest$tags' => '
The tags that you apply to the job queue to help you categorize and organize your resources. Each tag consists of a key and an optional value. For more information, see Tagging your Batch resources in Batch User Guide.
', 'CreateSchedulingPolicyRequest$tags' => '
The tags that you apply to the scheduling policy to help you categorize and organize your resources. Each tag consists of a key and an optional value. For more information, see Tagging Amazon Web Services Resources in Amazon Web Services General Reference.

These tags can be updated or removed using the TagResource and UntagResource API operations.
', 'JobDefinition$tags' => '
The tags that are applied to the job definition.
', 'JobDetail$tags' => '
The tags that are applied to the job.
', 'JobQueueDetail$tags' => '
The tags that are applied to the job queue. For more information, see Tagging your Batch resources in Batch User Guide.
', 'ListTagsForResourceResponse$tags' => '
The tags for the resource.
', 'RegisterJobDefinitionRequest$tags' => '
The tags that you apply to the job definition to help you categorize and organize your resources. Each tag consists of a key and an optional value. For more information, see Tagging Amazon Web Services Resources in Batch User Guide.
', 'SchedulingPolicyDetail$tags' => '
The tags that you apply to the scheduling policy to categorize and organize your resources. Each tag consists of a key and an optional value. For more information, see Tagging Amazon Web Services resources in Amazon Web Services General Reference.
', 'SubmitJobRequest$tags' => '
The tags that you apply to the job request to help you categorize and organize your resources. Each tag consists of a key and an optional value. For more information, see Tagging Amazon Web Services Resources in Amazon Web Services General Reference.
', 'TagResourceRequest$tags' => '
The tags that you apply to the resource to help you categorize and organize your resources. Each tag consists of a key and an optional value. For more information, see Tagging Amazon Web Services Resources in Amazon Web Services General Reference.
', ], ], 'TagsMap' => [ 'base' => NULL, 'refs' => [ 'ComputeResource$tags' => '
Key-value pair tags to be applied to EC2 resources that are launched in the compute environment. For Batch, these take the form of "String1": "String2", where String1 is the tag key and String2 is the tag value-for example, { "Name": "Batch Instance - C4OnDemand" }. This is helpful for recognizing your Batch instances in the Amazon EC2 console. Updating these tags requires an infrastructure update to the compute environment. For more information, see Updating compute environments in the Batch User Guide. These tags aren\'t seen when using the Batch ListTagsForResource API operation.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', 'ComputeResourceUpdate$tags' => '
Key-value pair tags to be applied to EC2 resources that are launched in the compute environment. For Batch, these take the form of "String1": "String2", where String1 is the tag key and String2 is the tag value-for example, { "Name": "Batch Instance - C4OnDemand" }. This is helpful for recognizing your Batch instances in the Amazon EC2 console. These tags aren\'t seen when using the Batch ListTagsForResource API operation.

When updating a compute environment, changing this setting requires an infrastructure update of the compute environment. For more information, see Updating compute environments in the Batch User Guide.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t specify it.
 </note>', ], ], 'TerminateJobRequest' => [ 'base' => '
Contains the parameters for TerminateJob.
', 'refs' => [], ], 'TerminateJobResponse' => [ 'base' => NULL, 'refs' => [], ], 'Tmpfs' => [ 'base' => '
The container path, mount options, and size of the tmpfs mount.
 <note>
This object isn\'t applicable to jobs that are running on Fargate resources.
 </note>', 'refs' => [ 'TmpfsList$member' => NULL, ], ], 'TmpfsList' => [ 'base' => NULL, 'refs' => [ 'LinuxParameters$tmpfs' => '
The container path, mount options, and size (in MiB) of the tmpfs mount. This parameter maps to the --tmpfs option to docker run.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources. Don\'t provide this parameter for this resource type.
 </note>', ], ], 'Ulimit' => [ 'base' => '
The ulimit settings to pass to the container.
 <note>
This object isn\'t applicable to jobs that are running on Fargate resources.
 </note>', 'refs' => [ 'Ulimits$member' => NULL, ], ], 'Ulimits' => [ 'base' => NULL, 'refs' => [ 'ContainerDetail$ulimits' => '
A list of ulimit values to set in the container. This parameter maps to Ulimits in the Create a container section of the Docker Remote API and the --ulimit option to docker run.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources.
 </note>', 'ContainerProperties$ulimits' => '
A list of ulimits to set in the container. This parameter maps to Ulimits in the Create a container section of the Docker Remote API and the --ulimit option to docker run.
 <note>
This parameter isn\'t applicable to jobs that are running on Fargate resources and shouldn\'t be provided.
 </note>', ], ], 'UntagResourceRequest' => [ 'base' => '
Contains the parameters for UntagResource.
', 'refs' => [], ], 'UntagResourceResponse' => [ 'base' => NULL, 'refs' => [], ], 'UpdateComputeEnvironmentRequest' => [ 'base' => '
Contains the parameters for UpdateComputeEnvironment.
', 'refs' => [], ], 'UpdateComputeEnvironmentResponse' => [ 'base' => NULL, 'refs' => [], ], 'UpdateJobQueueRequest' => [ 'base' => '
Contains the parameters for UpdateJobQueue.
', 'refs' => [], ], 'UpdateJobQueueResponse' => [ 'base' => NULL, 'refs' => [], ], 'UpdatePolicy' => [ 'base' => '
Specifies the infrastructure update policy for the compute environment. For more information about infrastructure updates, see Updating compute environments in the Batch User Guide.
', 'refs' => [ 'ComputeEnvironmentDetail$updatePolicy' => '
Specifies the infrastructure update policy for the compute environment. For more information about infrastructure updates, see Updating compute environments in the Batch User Guide.
', 'UpdateComputeEnvironmentRequest$updatePolicy' => '
Specifies the updated infrastructure update policy for the compute environment. For more information about infrastructure updates, see Updating compute environments in the Batch User Guide.
', ], ], 'UpdateSchedulingPolicyRequest' => [ 'base' => '
Contains the parameters for UpdateSchedulingPolicy.
', 'refs' => [], ], 'UpdateSchedulingPolicyResponse' => [ 'base' => NULL, 'refs' => [], ], 'Volume' => [ 'base' => '
A data volume that\'s used in a job\'s container properties.
', 'refs' => [ 'Volumes$member' => NULL, ], ], 'Volumes' => [ 'base' => NULL, 'refs' => [ 'ContainerDetail$volumes' => '
A list of volumes that are associated with the job.
', 'ContainerProperties$volumes' => '
A list of data volumes used in a job.
', ], ], ],];