docs-2.json

{
  "version": "2.0",
  "service": "<p>AWS Batch enables you to run batch computing workloads on the AWS Cloud. Batch computing is a common way for developers, scientists, and engineers to access large amounts of compute resources, and AWS Batch removes the undifferentiated heavy lifting of configuring and managing the required infrastructure. AWS Batch will be familiar to users of traditional batch computing software. This service can efficiently provision resources in response to jobs submitted in order to eliminate capacity constraints, reduce compute costs, and deliver results quickly.</p> <p>As a fully managed service, AWS Batch enables developers, scientists, and engineers to run batch computing workloads of any scale. AWS Batch automatically provisions compute resources and optimizes the workload distribution based on the quantity and scale of the workloads. With AWS Batch, there is no need to install or manage batch computing software, which allows you to focus on analyzing results and solving problems. AWS Batch reduces operational complexities, saves time, and reduces costs, which makes it easy for developers, scientists, and engineers to run their batch jobs in the AWS Cloud.</p>",
  "operations": {
    "CancelJob": "<p>Cancels a job in an AWS Batch job queue. Jobs that are in the <code>SUBMITTED</code>, <code>PENDING</code>, or <code>RUNNABLE</code> state are cancelled. Jobs that have progressed to <code>STARTING</code> or <code>RUNNING</code> are not cancelled (but the API operation still succeeds, even if no job is cancelled); these jobs must be terminated with the <a>TerminateJob</a> operation.</p>",
    "CreateComputeEnvironment": "<p>Creates an AWS Batch compute environment. You can create <code>MANAGED</code> or <code>UNMANAGED</code> compute environments.</p> <p>In a managed compute environment, AWS Batch manages the capacity and instance types of the compute resources within the environment. This is based on the compute resource specification that you define or the <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html\">launch template</a> that you specify when you create the compute environment. You can choose to use Amazon EC2 On-Demand Instances or Spot Instances in your managed compute environment. You can optionally set a maximum price so that Spot Instances only launch when the Spot Instance price is below a specified percentage of the On-Demand price.</p> <note> <p>Multi-node parallel jobs are not supported on Spot Instances.</p> </note> <p>In an unmanaged compute environment, you can manage your own compute resources. This provides more compute resource configuration options, such as using a custom AMI, but you must ensure that your AMI meets the Amazon ECS container instance AMI specification. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container_instance_AMIs.html\">Container Instance AMIs</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. After you have created your unmanaged compute environment, you can use the <a>DescribeComputeEnvironments</a> operation to find the Amazon ECS cluster that is associated with it. Then, manually launch your container instances into that Amazon ECS cluster. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/launch_container_instance.html\">Launching an Amazon ECS Container Instance</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <note> <p>AWS Batch does not upgrade the AMIs in a compute environment after it is created (for example, when a newer version of the Amazon ECS-optimized AMI is available). You are responsible for the management of the guest operating system (including updates and security patches) and any additional application software or utilities that you install on the compute resources. To use a new AMI for your AWS Batch jobs:</p> <ol> <li> <p>Create a new compute environment with the new AMI.</p> </li> <li> <p>Add the compute environment to an existing job queue.</p> </li> <li> <p>Remove the old compute environment from your job queue.</p> </li> <li> <p>Delete the old compute environment.</p> </li> </ol> </note>",
    "CreateJobQueue": "<p>Creates an AWS Batch job queue. When you create a job queue, you associate one or more compute environments to the queue and assign an order of preference for the compute environments.</p> <p>You also set a priority to the job queue that determines the order in which the AWS Batch scheduler places jobs onto its associated compute environments. For example, if a compute environment is associated with more than one job queue, the job queue with a higher priority is given preference for scheduling jobs to that compute environment.</p>",
    "DeleteComputeEnvironment": "<p>Deletes an AWS Batch compute environment.</p> <p>Before you can delete a compute environment, you must set its state to <code>DISABLED</code> with the <a>UpdateComputeEnvironment</a> API operation and disassociate it from any job queues with the <a>UpdateJobQueue</a> API operation.</p>",
    "DeleteJobQueue": "<p>Deletes the specified job queue. You must first disable submissions for a queue with the <a>UpdateJobQueue</a> operation. All jobs in the queue are terminated when you delete a job queue.</p> <p>It is not necessary to disassociate compute environments from a queue before submitting a <code>DeleteJobQueue</code> request.</p>",
    "DeregisterJobDefinition": "<p>Deregisters an AWS Batch job definition.</p>",
    "DescribeComputeEnvironments": "<p>Describes one or more of your compute environments.</p> <p>If you are using an unmanaged compute environment, you can use the <code>DescribeComputeEnvironment</code> operation to determine the <code>ecsClusterArn</code> that you should launch your Amazon ECS container instances into.</p>",
    "DescribeJobDefinitions": "<p>Describes a list of job definitions. You can specify a <code>status</code> (such as <code>ACTIVE</code>) to only return job definitions that match that status.</p>",
    "DescribeJobQueues": "<p>Describes one or more of your job queues.</p>",
    "DescribeJobs": "<p>Describes a list of AWS Batch jobs.</p>",
    "ListJobs": "<p>Returns a list of AWS Batch jobs.</p> <p>You must specify only one of the following:</p> <ul> <li> <p>a job queue ID to return a list of jobs in that job queue</p> </li> <li> <p>a multi-node parallel job ID to return a list of that job's nodes</p> </li> <li> <p>an array job ID to return a list of that job's children</p> </li> </ul> <p>You can filter the results by job status with the <code>jobStatus</code> parameter. If you do not specify a status, only <code>RUNNING</code> jobs are returned.</p>",
    "RegisterJobDefinition": "<p>Registers an AWS Batch job definition.</p>",
    "SubmitJob": "<p>Submits an AWS Batch job from a job definition. Parameters specified during <a>SubmitJob</a> override parameters defined in the job definition.</p>",
    "TerminateJob": "<p>Terminates a job in a job queue. Jobs that are in the <code>STARTING</code> or <code>RUNNING</code> state are terminated, which causes them to transition to <code>FAILED</code>. Jobs that have not progressed to the <code>STARTING</code> state are cancelled.</p>",
    "UpdateComputeEnvironment": "<p>Updates an AWS Batch compute environment.</p>",
    "UpdateJobQueue": "<p>Updates a job queue.</p>"
  },
  "shapes": {
    "ArrayJobDependency": {
      "base": null,
      "refs": {
        "JobDependency$type": "<p>The type of the job dependency.</p>"
      }
    },
    "ArrayJobStatusSummary": {
      "base": null,
      "refs": {
        "ArrayPropertiesDetail$statusSummary": "<p>A summary of the number of array job children in each available job status. This parameter is returned for parent array jobs.</p>"
      }
    },
    "ArrayProperties": {
      "base": "<p>An object representing an AWS Batch array job.</p>",
      "refs": {
        "SubmitJobRequest$arrayProperties": "<p>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 <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/array_jobs.html\">Array Jobs</a> in the <i>AWS Batch User Guide</i>.</p>"
      }
    },
    "ArrayPropertiesDetail": {
      "base": "<p>An object representing the array properties of a job.</p>",
      "refs": {
        "JobDetail$arrayProperties": "<p>The array properties of the job, if it is an array job.</p>"
      }
    },
    "ArrayPropertiesSummary": {
      "base": "<p>An object representing the array properties of a job.</p>",
      "refs": {
        "JobSummary$arrayProperties": "<p>The array properties of the job, if it is an array job.</p>"
      }
    },
    "AttemptContainerDetail": {
      "base": "<p>An object representing the details of a container that is part of a job attempt.</p>",
      "refs": {
        "AttemptDetail$container": "<p>Details about the container in this job attempt.</p>"
      }
    },
    "AttemptDetail": {
      "base": "<p>An object representing a job attempt.</p>",
      "refs": {
        "AttemptDetails$member": null
      }
    },
    "AttemptDetails": {
      "base": null,
      "refs": {
        "JobDetail$attempts": "<p>A list of job attempts associated with this job.</p>"
      }
    },
    "Boolean": {
      "base": null,
      "refs": {
        "ContainerDetail$readonlyRootFilesystem": "<p>When this parameter is true, the container is given read-only access to its root file system.</p>",
        "ContainerDetail$privileged": "<p>When this parameter is true, the container is given elevated privileges on the host container instance (similar to the <code>root</code> user).</p>",
        "ContainerProperties$readonlyRootFilesystem": "<p>When this parameter is true, the container is given read-only access to its root file system. This parameter maps to <code>ReadonlyRootfs</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>--read-only</code> option to <code>docker run</code>.</p>",
        "ContainerProperties$privileged": "<p>When this parameter is true, the container is given elevated privileges on the host container instance (similar to the <code>root</code> user). This parameter maps to <code>Privileged</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>--privileged</code> option to <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>.</p>",
        "MountPoint$readOnly": "<p>If this value is <code>true</code>, the container has read-only access to the volume; otherwise, the container can write to the volume. The default value is <code>false</code>.</p>",
        "NodeDetails$isMainNode": "<p>Specifies whether the current node is the main node for a multi-node parallel job.</p>",
        "NodePropertiesSummary$isMainNode": "<p>Specifies whether the current node is the main node for a multi-node parallel job.</p>"
      }
    },
    "CEState": {
      "base": null,
      "refs": {
        "ComputeEnvironmentDetail$state": "<p>The state of the compute environment. The valid values are <code>ENABLED</code> or <code>DISABLED</code>.</p> <p>If the state is <code>ENABLED</code>, then the AWS 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.</p> <p>If the state is <code>DISABLED</code>, then the AWS Batch scheduler does not attempt to place jobs within the environment. Jobs in a <code>STARTING</code> or <code>RUNNING</code> state continue to progress normally. Managed compute environments in the <code>DISABLED</code> state do not scale out. However, they scale in to <code>minvCpus</code> value after instances become idle.</p>",
        "CreateComputeEnvironmentRequest$state": "<p>The state of the compute environment. If the state is <code>ENABLED</code>, then the compute environment accepts jobs from a queue and can scale out automatically based on queues.</p>",
        "UpdateComputeEnvironmentRequest$state": "<p>The state of the compute environment. Compute environments in the <code>ENABLED</code> state can accept jobs from a queue and scale in or out automatically based on the workload demand of its associated queues.</p>"
      }
    },
    "CEStatus": {
      "base": null,
      "refs": {
        "ComputeEnvironmentDetail$status": "<p>The current status of the compute environment (for example, <code>CREATING</code> or <code>VALID</code>).</p>"
      }
    },
    "CEType": {
      "base": null,
      "refs": {
        "ComputeEnvironmentDetail$type": "<p>The type of the compute environment.</p>",
        "CreateComputeEnvironmentRequest$type": "<p>The type of the compute environment. For more information, see <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/compute_environments.html\">Compute Environments</a> in the <i>AWS Batch User Guide</i>.</p>"
      }
    },
    "CRAllocationStrategy": {
      "base": null,
      "refs": {
        "ComputeResource$allocationStrategy": "<p>The allocation strategy to use for the compute resource in case not enough instances of the best fitting instance type can be allocated. This could be due to availability of the instance type in the region or <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html\">Amazon EC2 service limits</a>. If this is not specified, the default is <code>BEST_FIT</code>, which will use only the best fitting instance type, waiting for additional capacity if it's not available. This allocation strategy keeps costs lower but can limit scaling. <code>BEST_FIT_PROGRESSIVE</code> will select an additional instance type that is large enough to meet the requirements of the jobs in the queue, with a preference for an instance type with a lower cost. <code>SPOT_CAPACITY_OPTIMIZED</code> is only available for Spot Instance compute resources and will select an additional instance type that is large enough to meet the requirements of the jobs in the queue, with a preference for an instance type that is less likely to be interrupted.</p>"
      }
    },
    "CRType": {
      "base": null,
      "refs": {
        "ComputeResource$type": "<p>The type of compute environment: <code>EC2</code> or <code>SPOT</code>.</p>"
      }
    },
    "CancelJobRequest": {
      "base": null,
      "refs": {
      }
    },
    "CancelJobResponse": {
      "base": null,
      "refs": {
      }
    },
    "ClientException": {
      "base": "<p>These errors are usually caused by a client action, such as using an action or resource on behalf of a user that doesn't have permissions to use the action or resource, or specifying an identifier that is not valid.</p>",
      "refs": {
      }
    },
    "ComputeEnvironmentDetail": {
      "base": "<p>An object representing an AWS Batch compute environment.</p>",
      "refs": {
        "ComputeEnvironmentDetailList$member": null
      }
    },
    "ComputeEnvironmentDetailList": {
      "base": null,
      "refs": {
        "DescribeComputeEnvironmentsResponse$computeEnvironments": "<p>The list of compute environments.</p>"
      }
    },
    "ComputeEnvironmentOrder": {
      "base": "<p>The order in which compute environments are tried 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.</p>",
      "refs": {
        "ComputeEnvironmentOrders$member": null
      }
    },
    "ComputeEnvironmentOrders": {
      "base": null,
      "refs": {
        "CreateJobQueueRequest$computeEnvironmentOrder": "<p>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 should execute a given job. Compute environments must be in the <code>VALID</code> state before you can associate them with a job queue. You can associate up to three compute environments with a job queue.</p>",
        "JobQueueDetail$computeEnvironmentOrder": "<p>The compute environments that are attached to the job queue and the order in which job placement is preferred. Compute environments are selected for job placement in ascending order.</p>",
        "UpdateJobQueueRequest$computeEnvironmentOrder": "<p>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 should execute a given job.</p>"
      }
    },
    "ComputeResource": {
      "base": "<p>An object representing an AWS Batch compute resource.</p>",
      "refs": {
        "ComputeEnvironmentDetail$computeResources": "<p>The compute resources defined for the compute environment.</p>",
        "CreateComputeEnvironmentRequest$computeResources": "<p>Details of the compute resources managed by the compute environment. This parameter is required for managed compute environments. For more information, see <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/compute_environments.html\">Compute Environments</a> in the <i>AWS Batch User Guide</i>.</p>"
      }
    },
    "ComputeResourceUpdate": {
      "base": "<p>An object representing the attributes of a compute environment that can be updated.</p>",
      "refs": {
        "UpdateComputeEnvironmentRequest$computeResources": "<p>Details of the compute resources managed by the compute environment. Required for a managed compute environment.</p>"
      }
    },
    "ContainerDetail": {
      "base": "<p>An object representing the details of a container that is part of a job.</p>",
      "refs": {
        "JobDetail$container": "<p>An object representing the details of the container that is associated with the job.</p>"
      }
    },
    "ContainerOverrides": {
      "base": "<p>The overrides that should be sent to a container.</p>",
      "refs": {
        "NodePropertyOverride$containerOverrides": "<p>The overrides that should be sent to a node range.</p>",
        "SubmitJobRequest$containerOverrides": "<p>A list of container overrides in JSON format 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 (that is specified in the job definition or the Docker image) with a <code>command</code> override. You can also override existing environment variables (that are specified in the job definition or Docker image) on a container or add new environment variables to it with an <code>environment</code> override.</p>"
      }
    },
    "ContainerProperties": {
      "base": "<p>Container properties are used in job definitions to describe the container that is launched as part of a job.</p>",
      "refs": {
        "JobDefinition$containerProperties": "<p>An object with various properties specific to container-based jobs.</p>",
        "NodeRangeProperty$container": "<p>The container details for the node range.</p>",
        "RegisterJobDefinitionRequest$containerProperties": "<p>An object with various properties specific to single-node container-based jobs. If the job definition's <code>type</code> parameter is <code>container</code>, then you must specify either <code>containerProperties</code> or <code>nodeProperties</code>.</p>"
      }
    },
    "ContainerSummary": {
      "base": "<p>An object representing summary details of a container within a job.</p>",
      "refs": {
        "JobSummary$container": "<p>An object representing the details of the container that is associated with the job.</p>"
      }
    },
    "CreateComputeEnvironmentRequest": {
      "base": null,
      "refs": {
      }
    },
    "CreateComputeEnvironmentResponse": {
      "base": null,
      "refs": {
      }
    },
    "CreateJobQueueRequest": {
      "base": null,
      "refs": {
      }
    },
    "CreateJobQueueResponse": {
      "base": null,
      "refs": {
      }
    },
    "DeleteComputeEnvironmentRequest": {
      "base": null,
      "refs": {
      }
    },
    "DeleteComputeEnvironmentResponse": {
      "base": null,
      "refs": {
      }
    },
    "DeleteJobQueueRequest": {
      "base": null,
      "refs": {
      }
    },
    "DeleteJobQueueResponse": {
      "base": null,
      "refs": {
      }
    },
    "DeregisterJobDefinitionRequest": {
      "base": null,
      "refs": {
      }
    },
    "DeregisterJobDefinitionResponse": {
      "base": null,
      "refs": {
      }
    },
    "DescribeComputeEnvironmentsRequest": {
      "base": null,
      "refs": {
      }
    },
    "DescribeComputeEnvironmentsResponse": {
      "base": null,
      "refs": {
      }
    },
    "DescribeJobDefinitionsRequest": {
      "base": null,
      "refs": {
      }
    },
    "DescribeJobDefinitionsResponse": {
      "base": null,
      "refs": {
      }
    },
    "DescribeJobQueuesRequest": {
      "base": null,
      "refs": {
      }
    },
    "DescribeJobQueuesResponse": {
      "base": null,
      "refs": {
      }
    },
    "DescribeJobsRequest": {
      "base": null,
      "refs": {
      }
    },
    "DescribeJobsResponse": {
      "base": null,
      "refs": {
      }
    },
    "Device": {
      "base": "<p>An object representing a container instance host device.</p>",
      "refs": {
        "DevicesList$member": null
      }
    },
    "DeviceCgroupPermission": {
      "base": null,
      "refs": {
        "DeviceCgroupPermissions$member": null
      }
    },
    "DeviceCgroupPermissions": {
      "base": null,
      "refs": {
        "Device$permissions": "<p>The explicit permissions to provide to the container for the device. By default, the container has permissions for <code>read</code>, <code>write</code>, and <code>mknod</code> for the device.</p>"
      }
    },
    "DevicesList": {
      "base": null,
      "refs": {
        "LinuxParameters$devices": "<p>Any host devices to expose to the container. This parameter maps to <code>Devices</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>--device</code> option to <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>.</p>"
      }
    },
    "EnvironmentVariables": {
      "base": null,
      "refs": {
        "ContainerDetail$environment": "<p>The environment variables to pass to a container.</p> <note> <p>Environment variables must not start with <code>AWS_BATCH</code>; this naming convention is reserved for variables that are set by the AWS Batch service.</p> </note>",
        "ContainerOverrides$environment": "<p>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.</p> <note> <p>Environment variables must not start with <code>AWS_BATCH</code>; this naming convention is reserved for variables that are set by the AWS Batch service.</p> </note>",
        "ContainerProperties$environment": "<p>The environment variables to pass to a container. This parameter maps to <code>Env</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>--env</code> option to <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>.</p> <important> <p>We do not recommend using plaintext environment variables for sensitive information, such as credential data.</p> </important> <note> <p>Environment variables must not start with <code>AWS_BATCH</code>; this naming convention is reserved for variables that are set by the AWS Batch service.</p> </note>"
      }
    },
    "Host": {
      "base": "<p>Determine whether your data volume persists on the host container instance and where it is stored. If this parameter is empty, then the Docker daemon assigns a host path for your data volume, but the data is not guaranteed to persist after the containers associated with it stop running.</p>",
      "refs": {
        "Volume$host": "<p>The contents of the <code>host</code> parameter determine whether your data volume persists on the host container instance and where it is stored. If the host parameter is empty, then the Docker daemon assigns a host path for your data volume. However, the data is not guaranteed to persist after the containers associated with it stop running.</p>"
      }
    },
    "Integer": {
      "base": null,
      "refs": {
        "ArrayJobStatusSummary$value": null,
        "ArrayProperties$size": "<p>The size of the array job.</p>",
        "ArrayPropertiesDetail$size": "<p>The size of the array job. This parameter is returned for parent array jobs.</p>",
        "ArrayPropertiesDetail$index": "<p>The job index within the array that is associated with this job. This parameter is returned for array job children.</p>",
        "ArrayPropertiesSummary$size": "<p>The size of the array job. This parameter is returned for parent array jobs.</p>",
        "ArrayPropertiesSummary$index": "<p>The job index within the array that is associated with this job. This parameter is returned for children of array jobs.</p>",
        "AttemptContainerDetail$exitCode": "<p>The exit code for the job attempt. A non-zero exit code is considered a failure.</p>",
        "ComputeEnvironmentOrder$order": "<p>The order of the compute environment.</p>",
        "ComputeResource$minvCpus": "<p>The minimum number of Amazon EC2 vCPUs that an environment should maintain (even if the compute environment is <code>DISABLED</code>).</p>",
        "ComputeResource$maxvCpus": "<p>The maximum number of Amazon EC2 vCPUs that an environment can reach.</p>",
        "ComputeResource$desiredvCpus": "<p>The desired number of Amazon EC2 vCPUS in the compute environment.</p>",
        "ComputeResource$bidPercentage": "<p>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 below 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.</p>",
        "ComputeResourceUpdate$minvCpus": "<p>The minimum number of Amazon EC2 vCPUs that an environment should maintain.</p>",
        "ComputeResourceUpdate$maxvCpus": "<p>The maximum number of Amazon EC2 vCPUs that an environment can reach.</p>",
        "ComputeResourceUpdate$desiredvCpus": "<p>The desired number of Amazon EC2 vCPUS in the compute environment.</p>",
        "ContainerDetail$vcpus": "<p>The number of VCPUs allocated for the job.</p>",
        "ContainerDetail$memory": "<p>The number of MiB of memory reserved for the job.</p>",
        "ContainerDetail$exitCode": "<p>The exit code to return upon completion.</p>",
        "ContainerOverrides$vcpus": "<p>The number of vCPUs to reserve for the container. This value overrides the value set in the job definition.</p>",
        "ContainerOverrides$memory": "<p>The number of MiB of memory reserved for the job. This value overrides the value set in the job definition.</p>",
        "ContainerProperties$vcpus": "<p>The number of vCPUs reserved for the container. This parameter maps to <code>CpuShares</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>--cpu-shares</code> option to <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>. Each vCPU is equivalent to 1,024 CPU shares. You must specify at least one vCPU.</p>",
        "ContainerProperties$memory": "<p>The hard limit (in MiB) of memory to present to the container. If your container attempts to exceed the memory specified here, the container is killed. This parameter maps to <code>Memory</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>--memory</code> option to <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>. You must specify at least 4 MiB of memory for a job.</p> <note> <p>If you are trying to maximize your resource utilization by providing your jobs as much memory as possible for a particular instance type, see <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/memory-management.html\">Memory Management</a> in the <i>AWS Batch User Guide</i>.</p> </note>",
        "ContainerSummary$exitCode": "<p>The exit code to return upon completion.</p>",
        "CreateJobQueueRequest$priority": "<p>The priority of the job queue. Job queues with a higher priority (or a higher integer value for the <code>priority</code> 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 <code>10</code> is given scheduling preference over a job queue with a priority value of <code>1</code>.</p>",
        "DescribeComputeEnvironmentsRequest$maxResults": "<p>The maximum number of cluster results returned by <code>DescribeComputeEnvironments</code> in paginated output. When this parameter is used, <code>DescribeComputeEnvironments</code> only returns <code>maxResults</code> results in a single page along with a <code>nextToken</code> response element. The remaining results of the initial request can be seen by sending another <code>DescribeComputeEnvironments</code> request with the returned <code>nextToken</code> value. This value can be between 1 and 100. If this parameter is not used, then <code>DescribeComputeEnvironments</code> returns up to 100 results and a <code>nextToken</code> value if applicable.</p>",
        "DescribeJobDefinitionsRequest$maxResults": "<p>The maximum number of results returned by <code>DescribeJobDefinitions</code> in paginated output. When this parameter is used, <code>DescribeJobDefinitions</code> only returns <code>maxResults</code> results in a single page along with a <code>nextToken</code> response element. The remaining results of the initial request can be seen by sending another <code>DescribeJobDefinitions</code> request with the returned <code>nextToken</code> value. This value can be between 1 and 100. If this parameter is not used, then <code>DescribeJobDefinitions</code> returns up to 100 results and a <code>nextToken</code> value if applicable.</p>",
        "DescribeJobQueuesRequest$maxResults": "<p>The maximum number of results returned by <code>DescribeJobQueues</code> in paginated output. When this parameter is used, <code>DescribeJobQueues</code> only returns <code>maxResults</code> results in a single page along with a <code>nextToken</code> response element. The remaining results of the initial request can be seen by sending another <code>DescribeJobQueues</code> request with the returned <code>nextToken</code> value. This value can be between 1 and 100. If this parameter is not used, then <code>DescribeJobQueues</code> returns up to 100 results and a <code>nextToken</code> value if applicable.</p>",
        "JobDefinition$revision": "<p>The revision of the job definition.</p>",
        "JobQueueDetail$priority": "<p>The priority of the job queue.</p>",
        "JobTimeout$attemptDurationSeconds": "<p>The time duration in seconds (measured from the job attempt's <code>startedAt</code> timestamp) after which AWS Batch terminates your jobs if they have not finished.</p>",
        "ListJobsRequest$maxResults": "<p>The maximum number of results returned by <code>ListJobs</code> in paginated output. When this parameter is used, <code>ListJobs</code> only returns <code>maxResults</code> results in a single page along with a <code>nextToken</code> response element. The remaining results of the initial request can be seen by sending another <code>ListJobs</code> request with the returned <code>nextToken</code> value. This value can be between 1 and 100. If this parameter is not used, then <code>ListJobs</code> returns up to 100 results and a <code>nextToken</code> value if applicable.</p>",
        "NodeDetails$nodeIndex": "<p>The node index for the node. Node index numbering begins at zero. This index is also available on the node with the <code>AWS_BATCH_JOB_NODE_INDEX</code> environment variable.</p>",
        "NodeOverrides$numNodes": "<p>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:</p> <ul> <li> <p>There must be at least one node range in your job definition that has an open upper boundary (such as <code>:</code> or <code>n:</code>).</p> </li> <li> <p>The lower boundary of the node range specified in the job definition must be fewer than the number of nodes specified in the override.</p> </li> <li> <p>The main node index specified in the job definition must be fewer than the number of nodes specified in the override.</p> </li> </ul>",
        "NodeProperties$numNodes": "<p>The number of nodes associated with a multi-node parallel job.</p>",
        "NodeProperties$mainNode": "<p>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.</p>",
        "NodePropertiesSummary$numNodes": "<p>The number of nodes associated with a multi-node parallel job.</p>",
        "NodePropertiesSummary$nodeIndex": "<p>The node index for the node. Node index numbering begins at zero. This index is also available on the node with the <code>AWS_BATCH_JOB_NODE_INDEX</code> environment variable.</p>",
        "RegisterJobDefinitionResponse$revision": "<p>The revision of the job definition.</p>",
        "RetryStrategy$attempts": "<p>The number of times to move a job to the <code>RUNNABLE</code> status. You may specify between 1 and 10 attempts. If the value of <code>attempts</code> is greater than one, the job is retried on failure the same number of attempts as the value.</p>",
        "Ulimit$hardLimit": "<p>The hard limit for the <code>ulimit</code> type.</p>",
        "Ulimit$softLimit": "<p>The soft limit for the <code>ulimit</code> type.</p>",
        "UpdateJobQueueRequest$priority": "<p>The priority of the job queue. Job queues with a higher priority (or a higher integer value for the <code>priority</code> 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 <code>10</code> is given scheduling preference over a job queue with a priority value of <code>1</code>.</p>"
      }
    },
    "JQState": {
      "base": null,
      "refs": {
        "CreateJobQueueRequest$state": "<p>The state of the job queue. If the job queue state is <code>ENABLED</code>, it is able to accept jobs.</p>",
        "JobQueueDetail$state": "<p>Describes the ability of the queue to accept new jobs.</p>",
        "UpdateJobQueueRequest$state": "<p>Describes the queue's ability to accept new jobs.</p>"
      }
    },
    "JQStatus": {
      "base": null,
      "refs": {
        "JobQueueDetail$status": "<p>The status of the job queue (for example, <code>CREATING</code> or <code>VALID</code>).</p>"
      }
    },
    "JobDefinition": {
      "base": "<p>An object representing an AWS Batch job definition.</p>",
      "refs": {
        "JobDefinitionList$member": null
      }
    },
    "JobDefinitionList": {
      "base": null,
      "refs": {
        "DescribeJobDefinitionsResponse$jobDefinitions": "<p>The list of job definitions.</p>"
      }
    },
    "JobDefinitionType": {
      "base": null,
      "refs": {
        "RegisterJobDefinitionRequest$type": "<p>The type of job definition.</p>"
      }
    },
    "JobDependency": {
      "base": "<p>An object representing an AWS Batch job dependency.</p>",
      "refs": {
        "JobDependencyList$member": null
      }
    },
    "JobDependencyList": {
      "base": null,
      "refs": {
        "JobDetail$dependsOn": "<p>A list of job names or IDs on which this job depends.</p>",
        "SubmitJobRequest$dependsOn": "<p>A list of dependencies for the job. A job can depend upon a maximum of 20 jobs. You can specify a <code>SEQUENTIAL</code> 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 <code>N_TO_N</code> 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.</p>"
      }
    },
    "JobDetail": {
      "base": "<p>An object representing an AWS Batch job.</p>",
      "refs": {
        "JobDetailList$member": null
      }
    },
    "JobDetailList": {
      "base": null,
      "refs": {
        "DescribeJobsResponse$jobs": "<p>The list of jobs.</p>"
      }
    },
    "JobQueueDetail": {
      "base": "<p>An object representing the details of an AWS Batch job queue.</p>",
      "refs": {
        "JobQueueDetailList$member": null
      }
    },
    "JobQueueDetailList": {
      "base": null,
      "refs": {
        "DescribeJobQueuesResponse$jobQueues": "<p>The list of job queues.</p>"
      }
    },
    "JobStatus": {
      "base": null,
      "refs": {
        "JobDetail$status": "<p>The current status for the job.</p> <note> <p>If your jobs do not progress to <code>STARTING</code>, see <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/troubleshooting.html#job_stuck_in_runnable\">Jobs Stuck in RUNNABLE Status</a> in the troubleshooting section of the <i>AWS Batch User Guide</i>.</p> </note>",
        "JobSummary$status": "<p>The current status for the job.</p>",
        "ListJobsRequest$jobStatus": "<p>The job status with which to filter jobs in the specified queue. If you do not specify a status, only <code>RUNNING</code> jobs are returned.</p>"
      }
    },
    "JobSummary": {
      "base": "<p>An object representing summary details of a job.</p>",
      "refs": {
        "JobSummaryList$member": null
      }
    },
    "JobSummaryList": {
      "base": null,
      "refs": {
        "ListJobsResponse$jobSummaryList": "<p>A list of job summaries that match the request.</p>"
      }
    },
    "JobTimeout": {
      "base": "<p>An object representing a job timeout configuration.</p>",
      "refs": {
        "JobDefinition$timeout": "<p>The timeout configuration for jobs that are submitted with this job definition. You can specify a timeout duration after which AWS Batch terminates your jobs if they have not finished.</p>",
        "JobDetail$timeout": "<p>The timeout configuration for the job.</p>",
        "RegisterJobDefinitionRequest$timeout": "<p>The timeout configuration for jobs that are submitted with this job definition, after which AWS Batch terminates your jobs if they have not finished. If a job is terminated due to a timeout, it is not retried. The minimum value for the timeout is 60 seconds. Any timeout configuration that is specified during a <a>SubmitJob</a> operation overrides the timeout configuration defined here. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/job_timeouts.html\">Job Timeouts</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>",
        "SubmitJobRequest$timeout": "<p>The timeout configuration for this <a>SubmitJob</a> operation. You can specify a timeout duration after which AWS Batch terminates your jobs if they have not finished. If a job is terminated due to a timeout, it is not 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 <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/job_timeouts.html\">Job Timeouts</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>"
      }
    },
    "KeyValuePair": {
      "base": "<p>A key-value pair object.</p>",
      "refs": {
        "EnvironmentVariables$member": null
      }
    },
    "LaunchTemplateSpecification": {
      "base": "<p>An object representing a launch template associated with a compute resource. You must specify either the launch template ID or launch template name in the request, but not both.</p>",
      "refs": {
        "ComputeResource$launchTemplate": "<p>The launch template to use for your compute resources. Any other compute resource parameters that you specify in a <a>CreateComputeEnvironment</a> 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 <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/launch-templates.html\">Launch Template Support</a> in the <i>AWS Batch User Guide</i>.</p>"
      }
    },
    "LinuxParameters": {
      "base": "<p>Linux-specific modifications that are applied to the container, such as details for device mappings.</p>",
      "refs": {
        "ContainerDetail$linuxParameters": "<p>Linux-specific modifications that are applied to the container, such as details for device mappings.</p>",
        "ContainerProperties$linuxParameters": "<p>Linux-specific modifications that are applied to the container, such as details for device mappings.</p>"
      }
    },
    "ListJobsRequest": {
      "base": null,
      "refs": {
      }
    },
    "ListJobsResponse": {
      "base": null,
      "refs": {
      }
    },
    "Long": {
      "base": null,
      "refs": {
        "AttemptDetail$startedAt": "<p>The Unix timestamp (in seconds and milliseconds) for when the attempt was started (when the attempt transitioned from the <code>STARTING</code> state to the <code>RUNNING</code> state).</p>",
        "AttemptDetail$stoppedAt": "<p>The Unix timestamp (in seconds and milliseconds) for when the attempt was stopped (when the attempt transitioned from the <code>RUNNING</code> state to a terminal state, such as <code>SUCCEEDED</code> or <code>FAILED</code>).</p>",
        "JobDetail$createdAt": "<p>The Unix timestamp (in seconds and milliseconds) for when the job was created. For non-array jobs and parent array jobs, this is when the job entered the <code>SUBMITTED</code> state (at the time <a>SubmitJob</a> was called). For array child jobs, this is when the child job was spawned by its parent and entered the <code>PENDING</code> state.</p>",
        "JobDetail$startedAt": "<p>The Unix timestamp (in seconds and milliseconds) for when the job was started (when the job transitioned from the <code>STARTING</code> state to the <code>RUNNING</code> state).</p>",
        "JobDetail$stoppedAt": "<p>The Unix timestamp (in seconds and milliseconds) for when the job was stopped (when the job transitioned from the <code>RUNNING</code> state to a terminal state, such as <code>SUCCEEDED</code> or <code>FAILED</code>).</p>",
        "JobSummary$createdAt": "<p>The Unix timestamp for when the job was created. For non-array jobs and parent array jobs, this is when the job entered the <code>SUBMITTED</code> state (at the time <a>SubmitJob</a> was called). For array child jobs, this is when the child job was spawned by its parent and entered the <code>PENDING</code> state.</p>",
        "JobSummary$startedAt": "<p>The Unix timestamp for when the job was started (when the job transitioned from the <code>STARTING</code> state to the <code>RUNNING</code> state).</p>",
        "JobSummary$stoppedAt": "<p>The Unix timestamp for when the job was stopped (when the job transitioned from the <code>RUNNING</code> state to a terminal state, such as <code>SUCCEEDED</code> or <code>FAILED</code>).</p>"
      }
    },
    "MountPoint": {
      "base": "<p>Details on a Docker volume mount point that is used in a job's container properties. This parameter maps to <code>Volumes</code> in the <a href=\"https://docs.docker.com/engine/reference/api/docker_remote_api_v1.19/#create-a-container\">Create a container</a> section of the Docker Remote API and the <code>--volume</code> option to docker run.</p>",
      "refs": {
        "MountPoints$member": null
      }
    },
    "MountPoints": {
      "base": null,
      "refs": {
        "ContainerDetail$mountPoints": "<p>The mount points for data volumes in your container.</p>",
        "ContainerProperties$mountPoints": "<p>The mount points for data volumes in your container. This parameter maps to <code>Volumes</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>--volume</code> option to <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>.</p>"
      }
    },
    "NetworkInterface": {
      "base": "<p>An object representing the elastic network interface for a multi-node parallel job node.</p>",
      "refs": {
        "NetworkInterfaceList$member": null
      }
    },
    "NetworkInterfaceList": {
      "base": null,
      "refs": {
        "AttemptContainerDetail$networkInterfaces": "<p>The network interfaces associated with the job attempt.</p>",
        "ContainerDetail$networkInterfaces": "<p>The network interfaces associated with the job.</p>"
      }
    },
    "NodeDetails": {
      "base": "<p>An object representing the details of a multi-node parallel job node.</p>",
      "refs": {
        "JobDetail$nodeDetails": "<p>An object representing the details of a node that is associated with a multi-node parallel job.</p>"
      }
    },
    "NodeOverrides": {
      "base": "<p>Object representing any node overrides to a job definition that is used in a <a>SubmitJob</a> API operation.</p>",
      "refs": {
        "SubmitJobRequest$nodeOverrides": "<p>A list of node overrides in JSON format that specify the node range to target and the container overrides for that node range.</p>"
      }
    },
    "NodeProperties": {
      "base": "<p>An object representing the node properties of a multi-node parallel job.</p>",
      "refs": {
        "JobDefinition$nodeProperties": "<p>An object with various properties specific to multi-node parallel jobs.</p>",
        "JobDetail$nodeProperties": "<p>An object representing the node properties of a multi-node parallel job.</p>",
        "RegisterJobDefinitionRequest$nodeProperties": "<p>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 <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/multi-node-parallel-jobs.html\">Multi-node Parallel Jobs</a> in the <i>AWS Batch User Guide</i>. If the job definition's <code>type</code> parameter is <code>container</code>, then you must specify either <code>containerProperties</code> or <code>nodeProperties</code>.</p>"
      }
    },
    "NodePropertiesSummary": {
      "base": "<p>An object representing the properties of a node that is associated with a multi-node parallel job.</p>",
      "refs": {
        "JobSummary$nodeProperties": "<p>The node properties for a single node in a job summary list.</p>"
      }
    },
    "NodePropertyOverride": {
      "base": "<p>Object representing any node overrides to a job definition that is used in a <a>SubmitJob</a> API operation.</p>",
      "refs": {
        "NodePropertyOverrides$member": null
      }
    },
    "NodePropertyOverrides": {
      "base": null,
      "refs": {
        "NodeOverrides$nodePropertyOverrides": "<p>The node property overrides for the job.</p>"
      }
    },
    "NodeRangeProperties": {
      "base": null,
      "refs": {
        "NodeProperties$nodeRangeProperties": "<p>A list of node ranges and their properties associated with a multi-node parallel job.</p>"
      }
    },
    "NodeRangeProperty": {
      "base": "<p>An object representing the properties of the node range for a multi-node parallel job.</p>",
      "refs": {
        "NodeRangeProperties$member": null
      }
    },
    "ParametersMap": {
      "base": null,
      "refs": {
        "JobDefinition$parameters": "<p>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 <code>SubmitJob</code> request override any corresponding parameter defaults from the job definition. For more information about specifying parameters, see <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/job_definition_parameters.html\">Job Definition Parameters</a> in the <i>AWS Batch User Guide</i>.</p>",
        "JobDetail$parameters": "<p>Additional parameters passed to the job that replace parameter substitution placeholders or override any corresponding parameter defaults from the job definition.</p>",
        "RegisterJobDefinitionRequest$parameters": "<p>Default parameter substitution placeholders to set in the job definition. Parameters are specified as a key-value pair mapping. Parameters in a <code>SubmitJob</code> request override any corresponding parameter defaults from the job definition.</p>",
        "SubmitJobRequest$parameters": "<p>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 <code>SubmitJob</code> request override any corresponding parameter defaults from the job definition.</p>"
      }
    },
    "RegisterJobDefinitionRequest": {
      "base": null,
      "refs": {
      }
    },
    "RegisterJobDefinitionResponse": {
      "base": null,
      "refs": {
      }
    },
    "ResourceRequirement": {
      "base": "<p>The type and amount of a resource to assign to a container. Currently, the only supported resource type is <code>GPU</code>.</p>",
      "refs": {
        "ResourceRequirements$member": null
      }
    },
    "ResourceRequirements": {
      "base": null,
      "refs": {
        "ContainerDetail$resourceRequirements": "<p>The type and amount of a resource to assign to a container. Currently, the only supported resource is <code>GPU</code>.</p>",
        "ContainerOverrides$resourceRequirements": "<p>The type and amount of a resource to assign to a container. This value overrides the value set in the job definition. Currently, the only supported resource is <code>GPU</code>.</p>",
        "ContainerProperties$resourceRequirements": "<p>The type and amount of a resource to assign to a container. Currently, the only supported resource is <code>GPU</code>.</p>"
      }
    },
    "ResourceType": {
      "base": null,
      "refs": {
        "ResourceRequirement$type": "<p>The type of resource to assign to a container. Currently, the only supported resource type is <code>GPU</code>.</p>"
      }
    },
    "RetryStrategy": {
      "base": "<p>The retry strategy associated with a job.</p>",
      "refs": {
        "JobDefinition$retryStrategy": "<p>The retry strategy to use for failed jobs that are submitted with this job definition.</p>",
        "JobDetail$retryStrategy": "<p>The retry strategy to use for this job if an attempt fails.</p>",
        "RegisterJobDefinitionRequest$retryStrategy": "<p>The retry strategy to use for failed jobs that are submitted with this job definition. Any retry strategy that is specified during a <a>SubmitJob</a> operation overrides the retry strategy defined here. If a job is terminated due to a timeout, it is not retried.</p>",
        "SubmitJobRequest$retryStrategy": "<p>The retry strategy to use for failed jobs from this <a>SubmitJob</a> operation. When a retry strategy is specified here, it overrides the retry strategy defined in the job definition.</p>"
      }
    },
    "ServerException": {
      "base": "<p>These errors are usually caused by a server issue.</p>",
      "refs": {
      }
    },
    "String": {
      "base": null,
      "refs": {
        "ArrayJobStatusSummary$key": null,
        "AttemptContainerDetail$containerInstanceArn": "<p>The Amazon Resource Name (ARN) of the Amazon ECS container instance that hosts the job attempt.</p>",
        "AttemptContainerDetail$taskArn": "<p>The Amazon Resource Name (ARN) of the Amazon ECS task that is associated with the job attempt. Each container attempt receives a task ARN when they reach the <code>STARTING</code> status.</p>",
        "AttemptContainerDetail$reason": "<p>A short (255 max characters) human-readable string to provide additional details about a running or stopped container.</p>",
        "AttemptContainerDetail$logStreamName": "<p>The name of the CloudWatch Logs log stream associated with the container. The log group for AWS Batch jobs is <code>/aws/batch/job</code>. Each container attempt receives a log stream name when they reach the <code>RUNNING</code> status.</p>",
        "AttemptDetail$statusReason": "<p>A short, human-readable string to provide additional details about the current status of the job attempt.</p>",
        "CancelJobRequest$jobId": "<p>The AWS Batch job ID of the job to cancel.</p>",
        "CancelJobRequest$reason": "<p>A message to attach to the job that explains the reason for canceling it. This message is returned by future <a>DescribeJobs</a> operations on the job. This message is also recorded in the AWS Batch activity logs.</p>",
        "ClientException$message": null,
        "ComputeEnvironmentDetail$computeEnvironmentName": "<p>The name of the compute environment.</p>",
        "ComputeEnvironmentDetail$computeEnvironmentArn": "<p>The Amazon Resource Name (ARN) of the compute environment.</p>",
        "ComputeEnvironmentDetail$ecsClusterArn": "<p>The Amazon Resource Name (ARN) of the underlying Amazon ECS cluster used by the compute environment.</p>",
        "ComputeEnvironmentDetail$statusReason": "<p>A short, human-readable string to provide additional details about the current status of the compute environment.</p>",
        "ComputeEnvironmentDetail$serviceRole": "<p>The service role associated with the compute environment that allows AWS Batch to make calls to AWS API operations on your behalf.</p>",
        "ComputeEnvironmentOrder$computeEnvironment": "<p>The Amazon Resource Name (ARN) of the compute environment.</p>",
        "ComputeResource$imageId": "<p>The Amazon Machine Image (AMI) ID used for instances launched in the compute environment.</p>",
        "ComputeResource$ec2KeyPair": "<p>The Amazon EC2 key pair that is used for instances launched in the compute environment.</p>",
        "ComputeResource$instanceRole": "<p>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, <code> <i>ecsInstanceRole</i> </code> or <code>arn:aws:iam::<i>&lt;aws_account_id&gt;</i>:instance-profile/<i>ecsInstanceRole</i> </code>. For more information, see <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/instance_IAM_role.html\">Amazon ECS Instance Role</a> in the <i>AWS Batch User Guide</i>.</p>",
        "ComputeResource$placementGroup": "<p>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 <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html\">Placement Groups</a> in the <i>Amazon EC2 User Guide for Linux Instances</i>.</p>",
        "ComputeResource$spotIamFleetRole": "<p>The Amazon Resource Name (ARN) of the Amazon EC2 Spot Fleet IAM role applied to a <code>SPOT</code> compute environment. For more information, see <a href=\"https://docs.aws.amazon.com/batch/latest/userguide/spot_fleet_IAM_role.html\">Amazon EC2 Spot Fleet Role</a> in the <i>AWS Batch User Guide</i>.</p>",
        "ContainerDetail$image": "<p>The image used to start the container.</p>",
        "ContainerDetail$jobRoleArn": "<p>The Amazon Resource Name (ARN) associated with the job upon execution.</p>",
        "ContainerDetail$user": "<p>The user name to use inside the container.</p>",
        "ContainerDetail$reason": "<p>A short (255 max characters) human-readable string to provide additional details about a running or stopped container.</p>",
        "ContainerDetail$containerInstanceArn": "<p>The Amazon Resource Name (ARN) of the container instance on which the container is running.</p>",
        "ContainerDetail$taskArn": "<p>The Amazon Resource Name (ARN) of the Amazon ECS task that is associated with the container job. Each container attempt receives a task ARN when they reach the <code>STARTING</code> status.</p>",
        "ContainerDetail$logStreamName": "<p>The name of the CloudWatch Logs log stream associated with the container. The log group for AWS Batch jobs is <code>/aws/batch/job</code>. Each container attempt receives a log stream name when they reach the <code>RUNNING</code> status.</p>",
        "ContainerDetail$instanceType": "<p>The instance type of the underlying host infrastructure of a multi-node parallel job.</p>",
        "ContainerOverrides$instanceType": "<p>The instance type to use for a multi-node parallel job. This parameter is not valid for single-node container jobs.</p>",
        "ContainerProperties$image": "<p>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 <code> <i>repository-url</i>/<i>image</i>:<i>tag</i> </code>. Up to 255 letters (uppercase and lowercase), numbers, hyphens, underscores, colons, periods, forward slashes, and number signs are allowed. This parameter maps to <code>Image</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>IMAGE</code> parameter of <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>.</p> <ul> <li> <p>Images in Amazon ECR repositories use the full registry and repository URI (for example, <code>012345678910.dkr.ecr.&lt;region-name&gt;.amazonaws.com/&lt;repository-name&gt;</code>).</p> </li> <li> <p>Images in official repositories on Docker Hub use a single name (for example, <code>ubuntu</code> or <code>mongo</code>).</p> </li> <li> <p>Images in other repositories on Docker Hub are qualified with an organization name (for example, <code>amazon/amazon-ecs-agent</code>).</p> </li> <li> <p>Images in other online repositories are qualified further by a domain name (for example, <code>quay.io/assemblyline/ubuntu</code>).</p> </li> </ul>",
        "ContainerProperties$jobRoleArn": "<p>The Amazon Resource Name (ARN) of the IAM role that the container can assume for AWS permissions.</p>",
        "ContainerProperties$user": "<p>The user name to use inside the container. This parameter maps to <code>User</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>--user</code> option to <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>.</p>",
        "ContainerProperties$instanceType": "<p>The instance type to use for a multi-node parallel job. Currently all node groups in a multi-node parallel job must use the same instance type. This parameter is not valid for single-node container jobs.</p>",
        "ContainerSummary$reason": "<p>A short (255 max characters) human-readable string to provide additional details about a running or stopped container.</p>",
        "CreateComputeEnvironmentRequest$computeEnvironmentName": "<p>The name for your compute environment. Up to 128 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed.</p>",
        "CreateComputeEnvironmentRequest$serviceRole": "<p>The full Amazon Resource Name (ARN) of the IAM role that allows AWS Batch to make calls to other AWS services on your behalf.</p> <p>If your specified role has a path other than <code>/</code>, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path.</p> <note> <p>Depending on how you created your AWS Batch service role, its ARN may contain the <code>service-role</code> path prefix. When you only specify the name of the service role, AWS Batch assumes that your ARN does not use the <code>service-role</code> path prefix. Because of this, we recommend that you specify the full ARN of your service role when you create compute environments.</p> </note>",
        "CreateComputeEnvironmentResponse$computeEnvironmentName": "<p>The name of the compute environment.</p>",
        "CreateComputeEnvironmentResponse$computeEnvironmentArn": "<p>The Amazon Resource Name (ARN) of the compute environment.</p>",
        "CreateJobQueueRequest$jobQueueName": "<p>The name of the job queue.</p>",
        "CreateJobQueueResponse$jobQueueName": "<p>The name of the job queue.</p>",
        "CreateJobQueueResponse$jobQueueArn": "<p>The Amazon Resource Name (ARN) of the job queue.</p>",
        "DeleteComputeEnvironmentRequest$computeEnvironment": "<p>The name or Amazon Resource Name (ARN) of the compute environment to delete.</p>",
        "DeleteJobQueueRequest$jobQueue": "<p>The short name or full Amazon Resource Name (ARN) of the queue to delete.</p>",
        "DeregisterJobDefinitionRequest$jobDefinition": "<p>The name and revision (<code>name:revision</code>) or full Amazon Resource Name (ARN) of the job definition to deregister.</p>",
        "DescribeComputeEnvironmentsRequest$nextToken": "<p>The <code>nextToken</code> value returned from a previous paginated <code>DescribeComputeEnvironments</code> request where <code>maxResults</code> was used and the results exceeded the value of that parameter. Pagination continues from the end of the previous results that returned the <code>nextToken</code> value. This value is <code>null</code> when there are no more results to return.</p> <note> <p>This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes.</p> </note>",
        "DescribeComputeEnvironmentsResponse$nextToken": "<p>The <code>nextToken</code> value to include in a future <code>DescribeComputeEnvironments</code> request. When the results of a <code>DescribeJobDefinitions</code> request exceed <code>maxResults</code>, this value can be used to retrieve the next page of results. This value is <code>null</code> when there are no more results to return.</p>",
        "DescribeJobDefinitionsRequest$jobDefinitionName": "<p>The name of the job definition to describe.</p>",
        "DescribeJobDefinitionsRequest$status": "<p>The status with which to filter job definitions.</p>",
        "DescribeJobDefinitionsRequest$nextToken": "<p>The <code>nextToken</code> value returned from a previous paginated <code>DescribeJobDefinitions</code> request where <code>maxResults</code> was used and the results exceeded the value of that parameter. Pagination continues from the end of the previous results that returned the <code>nextToken</code> value. This value is <code>null</code> when there are no more results to return.</p> <note> <p>This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes.</p> </note>",
        "DescribeJobDefinitionsResponse$nextToken": "<p>The <code>nextToken</code> value to include in a future <code>DescribeJobDefinitions</code> request. When the results of a <code>DescribeJobDefinitions</code> request exceed <code>maxResults</code>, this value can be used to retrieve the next page of results. This value is <code>null</code> when there are no more results to return.</p>",
        "DescribeJobQueuesRequest$nextToken": "<p>The <code>nextToken</code> value returned from a previous paginated <code>DescribeJobQueues</code> request where <code>maxResults</code> was used and the results exceeded the value of that parameter. Pagination continues from the end of the previous results that returned the <code>nextToken</code> value. This value is <code>null</code> when there are no more results to return.</p> <note> <p>This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes.</p> </note>",
        "DescribeJobQueuesResponse$nextToken": "<p>The <code>nextToken</code> value to include in a future <code>DescribeJobQueues</code> request. When the results of a <code>DescribeJobQueues</code> request exceed <code>maxResults</code>, this value can be used to retrieve the next page of results. This value is <code>null</code> when there are no more results to return.</p>",
        "Device$hostPath": "<p>The path for the device on the host container instance.</p>",
        "Device$containerPath": "<p>The path inside the container at which to expose the host device. By default the <code>hostPath</code> value is used.</p>",
        "Host$sourcePath": "<p>The path on the host container instance that is 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 does not 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.</p>",
        "JobDefinition$jobDefinitionName": "<p>The name of the job definition.</p>",
        "JobDefinition$jobDefinitionArn": "<p>The Amazon Resource Name (ARN) for the job definition.</p>",
        "JobDefinition$status": "<p>The status of the job definition.</p>",
        "JobDefinition$type": "<p>The type of job definition.</p>",
        "JobDependency$jobId": "<p>The job ID of the AWS Batch job associated with this dependency.</p>",
        "JobDetail$jobName": "<p>The name of the job.</p>",
        "JobDetail$jobId": "<p>The ID for the job.</p>",
        "JobDetail$jobQueue": "<p>The Amazon Resource Name (ARN) of the job queue with which the job is associated.</p>",
        "JobDetail$statusReason": "<p>A short, human-readable string to provide additional details about the current status of the job.</p>",
        "JobDetail$jobDefinition": "<p>The job definition that is used by this job.</p>",
        "JobQueueDetail$jobQueueName": "<p>The name of the job queue.</p>",
        "JobQueueDetail$jobQueueArn": "<p>The Amazon Resource Name (ARN) of the job queue.</p>",
        "JobQueueDetail$statusReason": "<p>A short, human-readable string to provide additional details about the current status of the job queue.</p>",
        "JobSummary$jobId": "<p>The ID of the job.</p>",
        "JobSummary$jobName": "<p>The name of the job.</p>",
        "JobSummary$statusReason": "<p>A short, human-readable string to provide additional details about the current status of the job.</p>",
        "KeyValuePair$name": "<p>The name of the key-value pair. For environment variables, this is the name of the environment variable.</p>",
        "KeyValuePair$value": "<p>The value of the key-value pair. For environment variables, this is the value of the environment variable.</p>",
        "LaunchTemplateSpecification$launchTemplateId": "<p>The ID of the launch template.</p>",
        "LaunchTemplateSpecification$launchTemplateName": "<p>The name of the launch template.</p>",
        "LaunchTemplateSpecification$version": "<p>The version number of the launch template.</p> <p>Default: The default version of the launch template.</p>",
        "ListJobsRequest$jobQueue": "<p>The name or full Amazon Resource Name (ARN) of the job queue with which to list jobs.</p>",
        "ListJobsRequest$arrayJobId": "<p>The job ID for an array job. Specifying an array job ID with this parameter lists all child jobs from within the specified array.</p>",
        "ListJobsRequest$multiNodeJobId": "<p>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.</p>",
        "ListJobsRequest$nextToken": "<p>The <code>nextToken</code> value returned from a previous paginated <code>ListJobs</code> request where <code>maxResults</code> was used and the results exceeded the value of that parameter. Pagination continues from the end of the previous results that returned the <code>nextToken</code> value. This value is <code>null</code> when there are no more results to return.</p> <note> <p>This token should be treated as an opaque identifier that is only used to retrieve the next items in a list and not for other programmatic purposes.</p> </note>",
        "ListJobsResponse$nextToken": "<p>The <code>nextToken</code> value to include in a future <code>ListJobs</code> request. When the results of a <code>ListJobs</code> request exceed <code>maxResults</code>, this value can be used to retrieve the next page of results. This value is <code>null</code> when there are no more results to return.</p>",
        "MountPoint$containerPath": "<p>The path on the container at which to mount the host volume.</p>",
        "MountPoint$sourceVolume": "<p>The name of the volume to mount.</p>",
        "NetworkInterface$attachmentId": "<p>The attachment ID for the network interface.</p>",
        "NetworkInterface$ipv6Address": "<p>The private IPv6 address for the network interface.</p>",
        "NetworkInterface$privateIpv4Address": "<p>The private IPv4 address for the network interface.</p>",
        "NodePropertyOverride$targetNodes": "<p>The range of nodes, using node index values, with which to override. A range of <code>0:3</code> indicates nodes with index values of <code>0</code> through <code>3</code>. If the starting range value is omitted (<code>:n</code>), then <code>0</code> is used to start the range. If the ending range value is omitted (<code>n:</code>), then the highest possible node index is used to end the range.</p>",
        "NodeRangeProperty$targetNodes": "<p>The range of nodes, using node index values. A range of <code>0:3</code> indicates nodes with index values of <code>0</code> through <code>3</code>. If the starting range value is omitted (<code>:n</code>), then <code>0</code> is used to start the range. If the ending range value is omitted (<code>n:</code>), then the highest possible node index is used to end the range. Your accumulative node ranges must account for all nodes (0:n). You may nest node ranges, for example 0:10 and 4:5, in which case the 4:5 range properties override the 0:10 properties.</p>",
        "ParametersMap$key": null,
        "ParametersMap$value": null,
        "RegisterJobDefinitionRequest$jobDefinitionName": "<p>The name of the job definition to register. Up to 128 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed.</p>",
        "RegisterJobDefinitionResponse$jobDefinitionName": "<p>The name of the job definition.</p>",
        "RegisterJobDefinitionResponse$jobDefinitionArn": "<p>The Amazon Resource Name (ARN) of the job definition.</p>",
        "ResourceRequirement$value": "<p>The number of physical GPUs to reserve for the container. The number of GPUs reserved for all containers in a job should not exceed the number of available GPUs on the compute resource that the job is launched on.</p>",
        "ServerException$message": null,
        "StringList$member": null,
        "SubmitJobRequest$jobName": "<p>The name of the job. The first character must be alphanumeric, and up to 128 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed.</p>",
        "SubmitJobRequest$jobQueue": "<p>The job queue into which the job is submitted. You can specify either the name or the Amazon Resource Name (ARN) of the queue.</p>",
        "SubmitJobRequest$jobDefinition": "<p>The job definition used by this job. This value can be either a <code>name:revision</code> or the Amazon Resource Name (ARN) for the job definition.</p>",
        "SubmitJobResponse$jobName": "<p>The name of the job.</p>",
        "SubmitJobResponse$jobId": "<p>The unique identifier for the job.</p>",
        "TagsMap$key": null,
        "TagsMap$value": null,
        "TerminateJobRequest$jobId": "<p>The AWS Batch job ID of the job to terminate.</p>",
        "TerminateJobRequest$reason": "<p>A message to attach to the job that explains the reason for canceling it. This message is returned by future <a>DescribeJobs</a> operations on the job. This message is also recorded in the AWS Batch activity logs.</p>",
        "Ulimit$name": "<p>The <code>type</code> of the <code>ulimit</code>.</p>",
        "UpdateComputeEnvironmentRequest$computeEnvironment": "<p>The name or full Amazon Resource Name (ARN) of the compute environment to update.</p>",
        "UpdateComputeEnvironmentRequest$serviceRole": "<p>The full Amazon Resource Name (ARN) of the IAM role that allows AWS Batch to make calls to other AWS services on your behalf.</p> <p>If your specified role has a path other than <code>/</code>, then you must either specify the full role ARN (this is recommended) or prefix the role name with the path.</p> <note> <p>Depending on how you created your AWS Batch service role, its ARN may contain the <code>service-role</code> path prefix. When you only specify the name of the service role, AWS Batch assumes that your ARN does not use the <code>service-role</code> path prefix. Because of this, we recommend that you specify the full ARN of your service role when you create compute environments.</p> </note>",
        "UpdateComputeEnvironmentResponse$computeEnvironmentName": "<p>The name of the compute environment.</p>",
        "UpdateComputeEnvironmentResponse$computeEnvironmentArn": "<p>The Amazon Resource Name (ARN) of the compute environment.</p>",
        "UpdateJobQueueRequest$jobQueue": "<p>The name or the Amazon Resource Name (ARN) of the job queue.</p>",
        "UpdateJobQueueResponse$jobQueueName": "<p>The name of the job queue.</p>",
        "UpdateJobQueueResponse$jobQueueArn": "<p>The Amazon Resource Name (ARN) of the job queue.</p>",
        "Volume$name": "<p>The name of the volume. Up to 255 letters (uppercase and lowercase), numbers, hyphens, and underscores are allowed. This name is referenced in the <code>sourceVolume</code> parameter of container definition <code>mountPoints</code>.</p>"
      }
    },
    "StringList": {
      "base": null,
      "refs": {
        "ComputeResource$instanceTypes": "<p>The instances types that may be launched. You can specify instance families to launch any instance type within those families (for example, <code>c5</code> or <code>p3</code>), or you can specify specific sizes within a family (such as <code>c5.8xlarge</code>). You can also choose <code>optimal</code> to pick instance types (from the C, M, and R instance families) on the fly that match the demand of your job queues.</p>",
        "ComputeResource$subnets": "<p>The VPC subnets into which the compute resources are launched. For more information, see <a href=\"https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html\">VPCs and Subnets</a> in the <i>Amazon VPC User Guide</i>.</p>",
        "ComputeResource$securityGroupIds": "<p>The Amazon EC2 security groups associated with instances launched in the compute environment. One or more security groups must be specified, either in <code>securityGroupIds</code> or using a launch template referenced in <code>launchTemplate</code>. If security groups are specified using both <code>securityGroupIds</code> and <code>launchTemplate</code>, the values in <code>securityGroupIds</code> will be used.</p>",
        "ContainerDetail$command": "<p>The command that is passed to the container.</p>",
        "ContainerOverrides$command": "<p>The command to send to the container that overrides the default command from the Docker image or the job definition.</p>",
        "ContainerProperties$command": "<p>The command that is passed to the container. This parameter maps to <code>Cmd</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>COMMAND</code> parameter to <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>. For more information, see <a href=\"https://docs.docker.com/engine/reference/builder/#cmd\">https://docs.docker.com/engine/reference/builder/#cmd</a>.</p>",
        "DescribeComputeEnvironmentsRequest$computeEnvironments": "<p>A list of up to 100 compute environment names or full Amazon Resource Name (ARN) entries.</p>",
        "DescribeJobDefinitionsRequest$jobDefinitions": "<p>A list of up to 100 job definition names or full Amazon Resource Name (ARN) entries.</p>",
        "DescribeJobQueuesRequest$jobQueues": "<p>A list of up to 100 queue names or full queue Amazon Resource Name (ARN) entries.</p>",
        "DescribeJobsRequest$jobs": "<p>A list of up to 100 job IDs.</p>"
      }
    },
    "SubmitJobRequest": {
      "base": null,
      "refs": {
      }
    },
    "SubmitJobResponse": {
      "base": null,
      "refs": {
      }
    },
    "TagsMap": {
      "base": null,
      "refs": {
        "ComputeResource$tags": "<p>Key-value pair tags to be applied to resources that are launched in the compute environment. For AWS Batch, these take the form of \"String1\": \"String2\", where String1 is the tag key and String2 is the tag value—for example, { \"Name\": \"AWS Batch Instance - C4OnDemand\" }.</p>"
      }
    },
    "TerminateJobRequest": {
      "base": null,
      "refs": {
      }
    },
    "TerminateJobResponse": {
      "base": null,
      "refs": {
      }
    },
    "Ulimit": {
      "base": "<p>The <code>ulimit</code> settings to pass to the container.</p>",
      "refs": {
        "Ulimits$member": null
      }
    },
    "Ulimits": {
      "base": null,
      "refs": {
        "ContainerDetail$ulimits": "<p>A list of <code>ulimit</code> values to set in the container.</p>",
        "ContainerProperties$ulimits": "<p>A list of <code>ulimits</code> to set in the container. This parameter maps to <code>Ulimits</code> in the <a href=\"https://docs.docker.com/engine/api/v1.23/#create-a-container\">Create a container</a> section of the <a href=\"https://docs.docker.com/engine/api/v1.23/\">Docker Remote API</a> and the <code>--ulimit</code> option to <a href=\"https://docs.docker.com/engine/reference/run/\">docker run</a>.</p>"
      }
    },
    "UpdateComputeEnvironmentRequest": {
      "base": null,
      "refs": {
      }
    },
    "UpdateComputeEnvironmentResponse": {
      "base": null,
      "refs": {
      }
    },
    "UpdateJobQueueRequest": {
      "base": null,
      "refs": {
      }
    },
    "UpdateJobQueueResponse": {
      "base": null,
      "refs": {
      }
    },
    "Volume": {
      "base": "<p>A data volume used in a job's container properties.</p>",
      "refs": {
        "Volumes$member": null
      }
    },
    "Volumes": {
      "base": null,
      "refs": {
        "ContainerDetail$volumes": "<p>A list of volumes associated with the job.</p>",
        "ContainerProperties$volumes": "<p>A list of data volumes used in a job.</p>"
      }
    }
  }
}