AWS · Cloud service
Amazon EC2 Auto Scaling with OrchestrAI
Catalog exported 2026-09-02
Create, resize, and tear down EC2 Auto Scaling groups from chat, each change confirmed before it runs.
OrchestrAI exposes 3 EC2 Auto Scaling operations: 3 create or modify resources and run only after you confirm the plan. Every one of them also carry a step-level approval gate.
What teams use it for
Platform teams use OrchestrAI to stand up an Auto Scaling group across subnets, optionally registered with a load balancer target group, and later to move its min, max, and desired capacity or point it at a new launch template. Every one of the three operations waits for your confirmation, and deleting a group is rated high risk because it terminates the instances inside it. There is no describe operation for Auto Scaling groups yet, so checking current capacity or instance health happens in the console.
Every EC2 Auto Scaling operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Create Auto Scaling Group |
Create an EC2 Auto Scaling Group across subnets, optionally behind a load balancer target group | Creates resources | Yes |
Update Auto Scaling Group |
Update an EC2 Auto Scaling Group's capacity bounds or launch template (scale up/down, resize) | Creates resources | Yes |
Delete Auto Scaling Group |
Delete an EC2 Auto Scaling Group, terminating its instances (teardown) | Modifies existing | Yes |
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 Auto Scaling group called web-asg in us-west-2 using the web-lt launch template with min 2, max 6, across the private subnets
- Scale the api-workers Auto Scaling group down to a desired capacity of 1 for the weekend
- Tear down the staging-batch Auto Scaling group and terminate its instances
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 change the capacity of an existing EC2 Auto Scaling group?
- Yes, the update operation changes min, max, and desired capacity or swaps the launch template. It is medium risk and waits for you to confirm before applying.
- What happens when OrchestrAI deletes an Auto Scaling group?
- The group and the instances it manages are terminated. The operation is marked high risk with confirmation, so you see the plan and blast radius and must approve it before anything is removed.
- Which EC2 Auto Scaling operations need an extra approval step?
- 3 operations carry a step-level approval gate on top of plan confirmation: Create Auto Scaling Group, Delete Auto Scaling Group, Update Auto Scaling Group. 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.