View EKS Clusters from your terminal
orbit lists EKS Clusters as a dense, sortable table (1 column: Cluster Name), fetched through the EKS API.
Read-only is the default, so browsing is safe against a production account. Start orbit with --write and the mutating actions become reachable: Delete Cluster, each behind its own confirmation dialog. Press Enter on a row to drill into eks node groups and eks fargate profiles and eks add-ons.
brew install doughlass/homebrew-tap/orbit
What the EKS Clusters table shows
| Column | Source field |
|---|---|
| Cluster Name | name |
Columns with an opt-in flag are hidden by default; press v for the column visibility picker.
Actions on EKS Clusters
| Key | Action | AWS API | Posture |
|---|---|---|---|
ctrl+d | Delete Cluster | EKS:delete_cluster | needs --write |
See how orbit keeps writes behind --write.
IAM permissions for this view
Read-only browsing needs EKS:None
plus the standard read-only permissions for this service. Write actions map to and are reachable only under --write.
Questions about EKS Clusters in orbit
What IAM permissions do I need to view EKS Clusters in orbit?
orbit lists EKS Clusters through the EKS list API, so the standard read-only permissions for EKS are enough. The mutating actions additionally require --write at startup.
Is browsing EKS Clusters safe against a production account?
Read-only is the default. Listing and describing EKS Clusters performs no mutations. The write actions on this view (Delete Cluster) are reachable only when orbit is started with --write, each behind its own confirmation.
Related views
orbit is not affiliated with or endorsed by Amazon Web Services, Inc. AWS is a trademark of Amazon.com, Inc. orbit is MIT licensed.