ELBv2

View Load Balancers from your terminal

orbit lists Load Balancers as a dense, sortable table: 6 columns including Name, Type and Scheme, fetched with ELBv2:DescribeLoadBalancers.

Read-only is the default, so browsing is safe against a production account. Start orbit with --write and the mutating actions become reachable: Delete Load Balancer, each behind its own confirmation dialog. Press Enter on a row to drill into listeners and target groups.

Install orbit brew install doughlass/homebrew-tap/orbit

What the Load Balancers table shows

Column Source field
NameLoadBalancerName
TypeType
SchemeScheme
StateState
Dns NameDNSName
VpcVpcId

Columns with an opt-in flag are hidden by default; press v for the column visibility picker.

Actions on Load Balancers

Key Action AWS API Posture
ctrl+dDelete Load BalancerELBv2:DeleteLoadBalancerneeds --write

See how orbit keeps writes behind --write.

IAM permissions for this view

Read-only browsing needs ELBv2:DescribeLoadBalancers plus the standard ELBv2 List and Describe permissions for the surrounding views. Write actions map to ELBv2:DeleteLoadBalancer and are reachable only under --write.

Questions about Load Balancers in orbit

What IAM permissions do I need to view Load Balancers in orbit?

orbit lists Load Balancers with ELBv2:DescribeLoadBalancers, so a policy granting ELBv2:DescribeLoadBalancers is enough for read-only browsing of this view. The mutating actions (ELBv2:DeleteLoadBalancer) additionally require --write at startup, and their IAM actions.

Is browsing Load Balancers safe against a production account?

Read-only is the default. Listing and describing Load Balancers performs no mutations. The write actions on this view (Delete Load Balancer) are reachable only when orbit is started with --write, each behind its own confirmation.

orbit is not affiliated with or endorsed by Amazon Web Services, Inc. AWS is a trademark of Amazon.com, Inc. orbit is MIT licensed.