Hey, maker here! This started as a shell alias I kept losing. Every time I needed a Postgres box on a private subnet I was retyping "aws ssm start-session --document-name AWS-StartPortForwardingSessionToRemoteHost" with a JSON blob of parameters, digging the instance ID out of the console, and then failing to find the command again a week later. Half the time the local port was already taken, so I'd get "Address already in use" and go hunt the PID with lsof. Now tunnels are saved cards. Start, stop, see throughput. If a port is held, the app tells you which process holds it and asks before killing it. The part I use most is actually the SSH side. The terminal and the file browser run over the same connection, so I can poke at a config file on the instance, including sudo reads and writes, without opening another session anywhere. RDP hands off to your native client and puts the saved password on your clipboard rather than writing it into the .rdp file. There's Parameter Store browsing and editing too, which was a "while I'm in here" thing that turned out to be the feature people asked about most. Desktop app on macOS and Windows. Everything above is free. Pro keeps an encrypted local history of the last five values for a parameter with a diff against the current one, which has saved me twice already. Genuinely curious whether it holds up against other people's AWS setups, since mine is the only one I've really lived in. If it breaks on yours I want to hear about it.

SSM Dojo

One Stop for AWS SSM Store, Tunnels, SSH, File System, RDP

One Stop for AWS SSM Store, Tunnels, SSH, File System, RDP