Broken pipe with start-session inactivity

[avylove]

When using start-session, the connection will fail with a broken pipe if there is no input or output for 60 seconds.

Cannot perform start session: write tcp 1.2.3.4:45678->100.99.98.97:443: write: broken

As long as there is input or output, the connection will hold.

The shell is still active on the instance, it just seems the socket connection get's dropped.

The weird thing I found is this only seems to happen when using an SSO profile to connect and does not seem to occur when using access keys.

Client OS: Fedora 41
AWS CLI: 2.17.18
SSM plugin: 1.2.707.0

Instance OS: Rocky 9 (Official AMI with LVM),
SSM Agent: 3.3.1957.0
Same behavior on an Ubuntu instance

[JanMosigItemis]

Hi there,

I think I may have encountered the same issue. Activating the tunnel and then connecting to a PostgresDB here. After connection is active, when idling for a small amount of time (didn't measure but 60s seems legit), I cannot post any commands via psql. It just gets stuck. No error message whatsoever. Matches the description of the OP about closing sockets.

Any hints on how to solve would be appreciated.

• Windows 10.0.22631.5624
• aws-cli/2.17.59 Python/3.12.6 Windows/11 exe/AMD64
• SSM 1.2.707.0