My laptop struggles at keeping an SSH connection alive with its default settings. See my pipe break below.
ubuntu@ip-10-106-2-194:~$ client_loop: send disconnect: Broken pipe
This is very annoying, especially if you are attempting something that requires long intervals of inactivity between commands.
Glancing through the SSH documentation, I found two settings that looked to be of importance.
They appear to be intervals that can be set on the server or client that send a keep alive request through the connection.
By setting the
ServerAliveInterval on my local machine I found my SSH connections to persist without intervention.
I also went ahead and put the
ClientAliveInterval setting into my personal AWS boxes.