Submit Job
batch.submit_job
ActionAmazon Web Servicesconnection required
Calls the AWS batch API (SigV4).
Submit a job to an AWS Batch queue.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- AWS Batch
- Secret shape
- {"access_key_id", "secret_access_key"}
- Config it needs
- region
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
region AWS region (overrides the connection). | string | No | — | — | — |
job_name Name of the job to act on, from batch.list_jobs. | string | Yes | — | — | — |
job_queue Job queue name or ARN. | string | Yes | — | — | — |
job_definition Job definition name[:revision]. | string | Yes | — | — | — |
parameters Job parameters. | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
job_id | string | — |
job_name | string | — |
job_arn Full ARN — what a tagging or cross-account step takes. | string | — |
{
"job_arn": "",
"job_id": "",
"job_name": ""
}Related AWS Batch nodes
See Submit Job run in a workflow.
In a technical demo we add the AWS Batch connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.