AWS's batch service · portable interface driver.Batch · AWS index
| Operation | Description |
|---|---|
CancelJob |
|
CreateComputeEnvironment |
Compute environments. |
CreateJobQueue |
Job queues. |
CreateSchedulingPolicy |
Scheduling policies. |
DeleteComputeEnvironment |
|
DeleteJobQueue |
|
DeleteSchedulingPolicy |
|
DeregisterJobDefinition |
|
DescribeComputeEnvironments |
|
DescribeJobDefinitions |
|
DescribeJobQueues |
|
DescribeJobs |
|
DescribeSchedulingPolicies |
|
ListJobs |
|
ListSchedulingPolicies |
|
ListTagsForResource |
|
RegisterJobDefinition |
Job definitions. |
SubmitJob |
Jobs. |
TagResource |
Tags (by ARN), shared across every taggable resource kind. |
TerminateJob |
|
UntagResource |
|
UpdateComputeEnvironment |
|
UpdateJobQueue |
|
UpdateSchedulingPolicy |
- Jobs run no workload: a job always succeeds (container
exitCode0) once its dependencies succeed. By default it isSUCCEEDEDas soon as it is submitted; with--async-settleit spends about one second each inSUBMITTED,RUNNABLEandSTARTING, then five seconds inRUNNING(and staysPENDINGwhile a dependency is unfinished).attemptsis always empty, and retry strategies and timeouts are stored and echoed but never applied. CancelJobon aPENDINGjob takes effect at once. Real Batch waits for the job's dependencies to finish first.- Array jobs: children are derived from the parent, not stored one by one.
SEQUENTIALandN_TO_Ndependencies are honoured. An array parent reportsPENDINGwhile any child is unfinished. - Multi-node parallel jobs: nodes are derived from the job, not stored one by one.
DescribeJobson<jobId>#<n>andListJobswithmultiNodeJobIdreturn each node withnodeDetails(nodeIndex,isMainNode) and the container, ECS or EKS properties of its node range. Every node, main or child, has the job's own status, reason and times; real Batch starts the child nodes only once the main node isRUNNING, and a child node can finish or fail on its own.CancelJobandTerminateJobtake the job ID, not a node ID. - Fair-share scheduling policies are stored, validated and bound to queues, but they never change the order in which jobs run. Jobs never stay
RUNNABLEbecause no capacity is free, so "Batch Job Queue Blocked" events are never sent. - "Batch Job State Change" events go to the EventBridge default bus on the serve scheduler's tick (and on any Batch job API call), one per status the job passed through; none is sent for the initial submission. In library mode, nothing ticks, so events are published when a job API call sees the change or when
Tickis called. A job that fails reports onlyFAILED, without the earlier steps. Array children and multi-node nodes send no events of their own. Real Batch sends no state-change events for compute environments or job queues, so the emulator sends none either. - Error messages are written by the emulator. The exception type (
ClientException, HTTP 400) is the documented one. containerOverrides,ecsPropertiesOverride,eksPropertiesOverrideandnodeOverridesare merged into the job detailDescribeJobsreturns (environment variables by name, resource requirements by type, other fields replaced). On a job queue whose compute environments areFARGATEorFARGATE_SPOT,SubmitJobrejectsnodeOverridesand multi-node job definitions with aClientException, andRegisterJobDefinitionrejectsnodePropertieswith theFARGATEplatform capability. Other platform rules are not checked: multi-node jobs on Spot orUNMANAGEDcompute environments, theinstanceType,memoryandvcpuscontainer overrides on Fargate, and ECS versus EKS properties against the compute environment, since EKS compute environments are not modeled.