Write Action
emr_containers.call
ActionAmazon Web Servicesconnection required
Calls the AWS emr_containers API (SigV4).
Run one of 13 write actions on EMR containers.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Amazon EMR Containers
- Secret shape
- {"access_key_id", "secret_access_key"}
- Config it needs
- region
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 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 | — | — | — |
action Which write action to run. | string | Yes | — | one of "CancelJobRun", "CreateJobTemplate", "CreateManagedEndpoint", "CreateSecurityConfiguration", "CreateVirtualCluster", "DeleteJobTemplate", "DeleteManagedEndpoint", "DeleteSecurityConfiguration", "DeleteVirtualCluster", "StartJobRun", "TagResource", "UntagResource", "UpdateVirtualCluster" | — |
request The action's input, as AWS documents it. | object | No | — | — | — |
Output
One shape.
result
The AWS response for the operation you named, as returned.
Extra keys beyond the ones listed can appear.
{}Notes
- This performs a real change in the account. Dry runs stub it, like every other external node.
Related Amazon EMR Containers nodes
See Write Action run in a workflow.
In a technical demo we add the Amazon EMR Containers connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.