View AMIs from your terminal
orbit lists AMIs as a dense, sortable table: 8 columns including Name, Image Id and State, fetched with EC2:DescribeImages.
Read-only is the default, so browsing is safe against a production account. Start orbit with --write and the mutating actions become reachable: Deregister AMI, each behind its own confirmation dialog.
brew install doughlass/homebrew-tap/orbit
What the AMIs table shows
| Column | Source field |
|---|---|
| Name | Name |
| Image Id | ImageId |
| State | State |
| Arch | Architecture |
| Platform | PlatformDetails |
| Root Type | RootDeviceType |
| Created | CreationDate |
| Public | Public |
Columns with an opt-in flag are hidden by default; press v for the column visibility picker.
Actions on AMIs
| Key | Action | AWS API | Posture |
|---|---|---|---|
ctrl+d | Deregister AMI | EC2:DeregisterImage | needs --write |
See how orbit keeps writes behind --write.
IAM permissions for this view
Read-only browsing needs EC2:DescribeImages
plus the standard EC2 List and Describe permissions for the surrounding views. Write actions map to EC2:DeregisterImage and are reachable only under --write.
Questions about AMIs in orbit
What IAM permissions do I need to view AMIs in orbit?
orbit lists AMIs with EC2:DescribeImages, so a policy granting EC2:DescribeImages is enough for read-only browsing of this view. The mutating actions (EC2:DeregisterImage) additionally require --write at startup, and their IAM actions.
Is browsing AMIs safe against a production account?
Read-only is the default. Listing and describing AMIs performs no mutations. The write actions on this view (Deregister AMI) are reachable only when orbit is started with --write, each behind its own confirmation.
Related views
EC2 Instances
View in the terminal
EBS Volumes
View in the terminal
EBS Snapshots
View in the terminal
VPCs
View in the terminal
orbit is not affiliated with or endorsed by Amazon Web Services, Inc. AWS is a trademark of Amazon.com, Inc. orbit is MIT licensed.