Appearance
AWS ECS
Manage container clusters, services, and tasks with Amazon ECS.
| Detail | Value |
|---|---|
| Category | Cloud & Infra |
| Base URL | https://ecs.us-east-1.amazonaws.com |
| Authentication | API Key |
| Endpoints | 8 |
| Connector key | aws-ecs |
Using AWS ECS in a workflow
- Go to Connections and click New Connection.
- Pick AWS ECS from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /#ListClusters | List ECS clusters |
POST /#DescribeClusters | Describe clusters |
POST /#CreateCluster | Create a cluster |
POST /#ListServices | List services |
POST /#DescribeServices | Describe services |
POST /#UpdateService | Update a service |
POST /#ListTasks | List tasks |
POST /#RunTask | Run a task |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /#ListClusters
List ECS clusters
| Detail | Value |
|---|---|
| Operation ID | cloud.listClusters |
| Method | POST |
| Path | /#ListClusters |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS ECS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listClusters. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS ECS API reference.
POST /#DescribeClusters
Describe clusters
| Detail | Value |
|---|---|
| Operation ID | cloud.describeClusters |
| Method | POST |
| Path | /#DescribeClusters |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS ECS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.describeClusters. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS ECS API reference.
POST /#CreateCluster
Create a cluster
| Detail | Value |
|---|---|
| Operation ID | cloud.createCluster |
| Method | POST |
| Path | /#CreateCluster |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS ECS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createCluster. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS ECS API reference.
POST /#ListServices
List services
| Detail | Value |
|---|---|
| Operation ID | cloud.listServices |
| Method | POST |
| Path | /#ListServices |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS ECS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listServices. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS ECS API reference.
POST /#DescribeServices
Describe services
| Detail | Value |
|---|---|
| Operation ID | cloud.describeServices |
| Method | POST |
| Path | /#DescribeServices |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS ECS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.describeServices. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS ECS API reference.
POST /#UpdateService
Update a service
| Detail | Value |
|---|---|
| Operation ID | cloud.updateService |
| Method | POST |
| Path | /#UpdateService |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS ECS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.updateService. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS ECS API reference.
POST /#ListTasks
List tasks
| Detail | Value |
|---|---|
| Operation ID | cloud.listTasks |
| Method | POST |
| Path | /#ListTasks |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS ECS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listTasks. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS ECS API reference.
POST /#RunTask
Run a task
| Detail | Value |
|---|---|
| Operation ID | cloud.runTask |
| Method | POST |
| Path | /#RunTask |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your AWS ECS connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.runTask. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream AWS ECS API reference.