Skip to content

Viewing and Copying Commands

Copy generated SSH or AWS Session Manager commands for use in terminals or scripts.

Access the Command Section

  1. Select a tunnel in the main list
  2. Scroll to the Command section (collapsed by default)
  3. Click the disclosure triangle to expand

Command Types

SSH Tunnels

ssh -p 2222 -l ubuntu -i ~/.ssh/prod_key prod.example.com
Parameter Example Purpose
-p -p 2222 Port (if non-standard)
-l -l ubuntu Username
-i -i ~/.ssh/prod_key Identity file path
Host prod.example.com Target server

AWS Session Manager

aws ssm start-session --target i-0abc123def456 --document-name AWS-StartSSHSession
Parameter Purpose
--target EC2 instance ID
--document-name Session document
--profile AWS profile (optional)
--region AWS region (optional)

Copy to Clipboard

Click Copy or press Cmd+Shift+C with the detail view active.

The command is copied with proper shell escaping.

Warnings

Warnings appear above the command when configuration issues are detected:

Warning Action
No SSH key configured Add key in tunnel settings
Identity file not found Verify path or generate key
Host verification disabled Enable in settings if possible
AWS credentials missing Configure AWS credentials
Invalid AWS instance ID Verify ID in AWS console

Informational Only

Warnings don't prevent command generation—they alert you to potential issues.

Common Uses

Paste in Terminal

  1. Copy command (Cmd+Shift+C)
  2. Open Terminal
  3. Paste (Cmd+V)
  4. Press Enter

Add to SSH Config

Use the command parameters to create an SSH config entry:

Host prod-db
    HostName prod.example.com
    Port 2222
    User ubuntu
    IdentityFile ~/.ssh/prod_key

Then connect with: ssh prod-db

Best Practices

  • Review before executing - Verify all parameters are correct
  • Fix warnings first - Address configuration issues before connecting
  • Protect SSH keys - Ensure identity files have 600 permissions
  • Don't share commands - They may contain sensitive configuration details

Troubleshooting

Command Doesn't Work

  1. Check warnings section for configuration issues
  2. Verify SSH key permissions (chmod 600 ~/.ssh/key)
  3. Ensure host is reachable

AWS Session Fails

  1. Verify AWS credentials are configured
  2. Check IAM permissions for Session Manager
  3. Confirm instance ID is correct