EC2

View EC2 Instances from your terminal

orbit lists EC2 Instances as a dense, sortable table: 49 columns including Name, Instance Id and State, fetched with EC2:DescribeInstances.

Read-only is the default, so browsing is safe against a production account. Start orbit with --write and the mutating actions become reachable: Connect (SSM), Start, Stop, Reboot and more, each behind its own confirmation dialog.

Install orbit brew install doughlass/homebrew-tap/orbit

What the EC2 Instances table shows

Column Source field
NameTags.Name
Instance IdInstanceId
StateState
TypeInstanceType
AzAvailabilityZone
Public IpPublicIpAddress
Private IpPrivateIpAddress
Public DnsPublicDnsName
Private DnsPrivateDnsName
Elastic IpElasticIp
Ipv6 IpIpv6Address
MonitoringMonitoring
Sec GroupsSecurityGroupNames
Sec Group IdsSecurityGroupIds
Key NameKeyName
Launch TimeLaunchTime
PlatformPlatform
Platform DetailsPlatformDetails
Vpc IdVpcId
Subnet IdSubnetId
Image IdImageId
ArchitectureArchitecture
Virt TypeVirtualizationType
Root Device NameRootDeviceName
Root Device TypeRootDeviceType
Ebs OptimizedEbsOptimized
Volume IdVolumeId
Kernel IdKernelId
Ramdisk IdRamdiskId
Ami Launch IndexAmiLaunchIndex
Instance LifecycleInstanceLifecycle
Iam Profile ArnIamInstanceProfileArn
TenancyTenancy
AffinityAffinity
Host IdHostId
Placement GroupPlacementGroup
Partition NumberPartitionNumber
Capacity Reservation IdCapacityReservationId
State Transition CodeStateTransitionCode
State Transition MsgStateTransitionMessage
HibernationHibernation
Outpost ArnOutpostArn
Product CodesProductCodes
Imdsv2Imdsv2
Usage OperationUsageOperation
HypervisorHypervisor
Ena SupportEnaSupport
Spot Request IdSpotInstanceRequestId
OperatorOperator

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

Actions on EC2 Instances

Key Action AWS API Posture
cConnect (SSM)EC2:ssm_connectneeds --write
sStartEC2:StartInstancesneeds --write
SStopEC2:StopInstancesneeds --write
rRebootEC2:RebootInstancesneeds --write
ctrl+dTerminateEC2:TerminateInstancesneeds --write

See how orbit keeps writes behind --write.

IAM permissions for this view

Read-only browsing needs EC2:DescribeInstances plus the standard EC2 List and Describe permissions for the surrounding views. Write actions map to EC2:StartInstances, EC2:StopInstances and are reachable only under --write.

Questions about EC2 Instances in orbit

What IAM permissions do I need to view EC2 Instances in orbit?

orbit lists EC2 Instances with EC2:DescribeInstances, so a policy granting EC2:DescribeInstances is enough for read-only browsing of this view. The mutating actions (EC2:StartInstances, EC2:StopInstances) additionally require --write at startup, and their IAM actions.

Is browsing EC2 Instances safe against a production account?

Read-only is the default. Listing and describing EC2 Instances performs no mutations. The write actions on this view (Connect (SSM), Start, Stop, Reboot) 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.