List Clusters

emr.list_clusters
ActionAmazon Web Servicesconnection required

Calls the AWS emr API (SigV4).

List EMR clusters and their state.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Amazon EMR
Secret shape
{"access_key_id", "secret_access_key"}
Config it needs
region
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
region
AWS region (overrides the connection).
stringNo———
states
e.g. ["RUNNING","WAITING"].
arrayNo—array of string—
next_token
Continues a previous run of this node, using that run's next_token output.
stringNo———

Output

One shape.

result

FieldTypeExample
clusters
array—
clusters[].cluster_id
Cluster id (j-…).
string—
clusters[].name
Cluster name.
string—
clusters[].state
STARTING, RUNNING, WAITING, TERMINATED, …
string—
clusters[].cluster_arn
The cluster's ARN, for tagging and IAM.
string—
clusters[].outpost_arn
ARN of the Outpost the cluster runs on, when it runs on one.
string—
clusters[].normalized_instance_hours
Approximate instance hours the cluster has used, rounded up to the hour.
number—
count
number—
next_token
Cursor for the next page; empty when there are no further pages.
string—
{
  "clusters": [
    {
      "cluster_arn": "",
      "cluster_id": "",
      "name": "",
      "normalized_instance_hours": 0,
      "outpost_arn": "",
      "state": ""
    }
  ],
  "count": 0,
  "next_token": ""
}

Related Amazon EMR nodes

See List Clusters run in a workflow.

In a technical demo we add the Amazon EMR connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.