AWS systems-manager documentation change
Summary
Updated SSH session requirements with TLS encryption details
Security assessment
Adds technical details about TLS usage for SSH connections but doesn't indicate any security vulnerability being fixed. Strengthens documentation of existing security controls.
Diff
diff --git a/systems-manager/latest/userguide/session-manager-working-with-sessions-start.md b/systems-manager/latest/userguide/session-manager-working-with-sessions-start.md index b7ddab982..62de1d376 100644 --- a//systems-manager/latest/userguide/session-manager-working-with-sessions-start.md +++ b//systems-manager/latest/userguide/session-manager-working-with-sessions-start.md @@ -129 +129 @@ To start a Session Manager SSH session, version 2.3.672.0 or later of SSM Agent -Take note of the following requirements and limitations for session connections using SSH: +Take note of the following requirements and limitations for session connections using SSH through Session Manager: @@ -135 +135 @@ Take note of the following requirements and limitations for session connections - * Logging isn't available for Session Manager sessions that connect through port forwarding or SSH. This is because SSH encrypts all session data, and Session Manager only serves as a tunnel for SSH connections. + * Logging isn't available for Session Manager sessions that connect through port forwarding or SSH. This is because SSH encrypts all session data within the secure TLS connection established between the AWS CLI and Session Manager endpoints, and Session Manager only serves as a tunnel for SSH connections.