AWS · Cloud service
Elastic Load Balancing with OrchestrAI
Catalog exported 2026-09-02
Create Application and Network Load Balancers from chat: target groups, listeners, and routing rules.
OrchestrAI exposes 5 ELB 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 use OrchestrAI to create an ALB or NLB, define target groups with health checks, add HTTPS listeners, and write path-based or host-based listener rules that send traffic to different target groups. Load balancer, target group, and listener creation are medium risk, and the combined load balancer operation waits for confirmation. Registering targets, describing existing load balancers, and deleting any of these resources are not covered, so attaching instances or IPs to a target group still happens in the console or through an Auto Scaling group.
Every ELB operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Create ALB Listener Rule |
Create an ALB listener rule for path-based or host-based routing to different target groups | Low risk | No |
Create ALB Listener |
Create a listener for an Application Load Balancer | Creates resources | No |
Create Application Load Balancer |
Create an Application Load Balancer (ALB) | Creates resources | No |
Create Load Balancer (Terraform-style) |
Create an Application or Network Load Balancer | Creates resources | Yes |
Create Target Group |
Create an ALB target group | 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 internet-facing ALB named web-alb in the public subnets of app-vpc with the web-sg security group
- Create a target group api-tg on port 8080 with a /health check and add an HTTPS listener on web-alb using the cert arn:aws:acm:us-east-1:123456789012:certificate/abcd
- Add a listener rule that routes /api/* on web-alb 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 register EC2 instances to a load balancer target group?
- Not directly; it creates target groups, listeners, and rules, but registration is done through an Auto Scaling group attachment or in the console.
- Does OrchestrAI create Network Load Balancers as well as ALBs?
- Yes, the load balancer operation supports both application and network types, with confirmation before it runs.
- Which ELB operations need an extra approval step?
- One operation carries a step-level approval gate on top of plan confirmation: Create Load Balancer (Terraform-style). 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.