View SQS Queues from your terminal
orbit lists SQS Queues as a dense, sortable table: 1 column: Queue Url, fetched with SQS:ListQueues.
Read-only is the default, so browsing is safe against a production account. Start orbit with --write and the mutating actions become reachable: Purge Queue, Delete Queue, each behind its own confirmation dialog.
brew install doughlass/homebrew-tap/orbit
What the SQS Queues table shows
| Column | Source field |
|---|---|
| Queue Url | QueueUrl |
Columns with an opt-in flag are hidden by default; press v for the column visibility picker.
Actions on SQS Queues
| Key | Action | AWS API | Posture |
|---|---|---|---|
P | Purge Queue | SQS:PurgeQueue | needs --write |
ctrl+d | Delete Queue | SQS:DeleteQueue | needs --write |
See how orbit keeps writes behind --write.
IAM permissions for this view
Read-only browsing needs SQS:ListQueues
plus the standard SQS List and Describe permissions for the surrounding views. Write actions map to SQS:PurgeQueue, SQS:DeleteQueue and are reachable only under --write.
Questions about SQS Queues in orbit
What IAM permissions do I need to view SQS Queues in orbit?
orbit lists SQS Queues with SQS:ListQueues, so a policy granting SQS:ListQueues is enough for read-only browsing of this view. The mutating actions (SQS:PurgeQueue, SQS:DeleteQueue) additionally require --write at startup, and their IAM actions.
Is browsing SQS Queues safe against a production account?
Read-only is the default. Listing and describing SQS Queues performs no mutations. The write actions on this view (Purge Queue, Delete Queue) are reachable only when orbit is started with --write, each behind its own confirmation.
Related views
CloudWatch Alarms
View in the terminal
SNS Topics
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.