View RDS Instances from your terminal
orbit lists RDS Instances as a dense, sortable table: 5 columns including Db Identifier, Status and Engine, fetched with RDS:DescribeDBInstances.
Read-only is the default, so browsing is safe against a production account. Start orbit with --write and the mutating actions become reachable: Start, Stop, Reboot, Delete, each behind its own confirmation dialog. Press Enter on a row to drill into rds snapshots.
brew install doughlass/homebrew-tap/orbit
What the RDS Instances table shows
| Column | Source field |
|---|---|
| Db Identifier | DBInstanceIdentifier |
| Status | DBInstanceStatus |
| Engine | Engine |
| Class | DBInstanceClass |
| Az | AvailabilityZone |
Columns with an opt-in flag are hidden by default; press v for the column visibility picker.
Actions on RDS Instances
| Key | Action | AWS API | Posture |
|---|---|---|---|
s | Start | RDS:StartDBInstance | needs --write |
S | Stop | RDS:StopDBInstance | needs --write |
r | Reboot | RDS:RebootDBInstance | needs --write |
ctrl+d | Delete | RDS:DeleteDBInstance | needs --write |
See how orbit keeps writes behind --write.
IAM permissions for this view
Read-only browsing needs RDS:DescribeDBInstances
plus the standard RDS List and Describe permissions for the surrounding views. Write actions map to RDS:StartDBInstance, RDS:StopDBInstance, RDS:RebootDBInstance and are reachable only under --write.
Questions about RDS Instances in orbit
What IAM permissions do I need to view RDS Instances in orbit?
orbit lists RDS Instances with RDS:DescribeDBInstances, so a policy granting RDS:DescribeDBInstances is enough for read-only browsing of this view. The mutating actions (RDS:StartDBInstance, RDS:StopDBInstance, RDS:RebootDBInstance) additionally require --write at startup, and their IAM actions.
Is browsing RDS Instances safe against a production account?
Read-only is the default. Listing and describing RDS Instances performs no mutations. The write actions on this view (Start, Stop, Reboot, Delete) are reachable only when orbit is started with --write, each behind its own confirmation.
Related views
Aurora Clusters
View in the terminal
Lambda Functions
View in the terminal
EC2 Instances
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.