AWS · Cloud service
Amazon Elastic Container Service with OrchestrAI
Catalog exported 2026-09-02
Set up Amazon ECS from chat: create clusters, register task definitions, and launch services.
OrchestrAI exposes 5 ECS operations: 1 is low-risk (read-only or low-impact), and 4 create or modify resources and run only after you confirm the plan. 1 of them also carries a step-level approval gate.
What teams use it for
Teams shipping containers use OrchestrAI to create a cluster, register a task definition with the right image, CPU, memory, and environment, and start a service that keeps the desired number of tasks running behind a target group. Cluster and task definition creation are medium risk, and the service create with the confirm flag waits for your approval. Existing services cannot be updated, scaled, or deleted, and there are no describe operations, so changing a running service's image or task count means going to the console.
Every ECS operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Register ECS Task Definition |
Register an ECS task definition for container workloads | Low risk | No |
Create ECS Cluster |
Create an Amazon ECS cluster | Creates resources | No |
Create ECS Service |
Create an ECS service to run and maintain tasks | Creates resources | No |
Create ECS Service |
Create an ECS service to run and maintain tasks | Creates resources | Yes |
Register ECS Task Definition |
Register a new ECS task definition | Creates resources | No |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Create an ECS cluster called prod-apps in us-east-1
- Register a Fargate task definition for the api-service using image 123456789012.dkr.ecr.us-east-1.amazonaws.com/api:1.4.2 with 512 CPU and 1024 memory
- Create an ECS service named api-service on prod-apps with 3 tasks attached to the api-tg target group
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Can OrchestrAI update an existing ECS service?
- Not yet; coverage is limited to creating clusters, task definitions, and services. Rolling out a new image to an existing service is done in the console or with the CLI.
- Does OrchestrAI support Fargate in ECS?
- Yes, the task definition and service operations accept Fargate launch settings alongside EC2-backed clusters.
- Which ECS operations need an extra approval step?
- One operation carries a step-level approval gate on top of plan confirmation: Create ECS Service. None of them is classed destructive.
Other AWS services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.