AWS systems-manager documentation change
Summary
Updated wording for clarity, emphasized 'can't' with italics, and removed a paragraph recommending explicit session termination via CLI/console. Removed guidance about lingering active sessions when not explicitly terminated.
Security assessment
The changes are primarily editorial improvements. While the removed paragraph discussed session persistence risks, there's no evidence this addresses a specific security vulnerability. The update clarifies existing behavior but doesn't introduce new security documentation.
Diff
diff --git a/systems-manager/latest/userguide/session-manager-working-with-sessions-end.md b/systems-manager/latest/userguide/session-manager-working-with-sessions-end.md index d467f83e1..fc90d19d2 100644 --- a/systems-manager/latest/userguide/session-manager-working-with-sessions-end.md +++ b/systems-manager/latest/userguide/session-manager-working-with-sessions-end.md @@ -9 +9 @@ Ending a session (console)Ending a session (AWS CLI) -You can end a session that you started in your account using the AWS Systems Manager console or the AWS Command Line Interface (AWS CLI). When you choose the **Terminate** button for a session in the console or call the [TerminateSession](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_TerminateSession.html) API action by using the AWS CLI, Session Manager permanently ends the session and closes the data connection between the Session Manager client and SSM Agent on the managed node. You can't resume a terminated session. +You can use the AWS Systems Manager console or the AWS Command Line Interface (AWS CLI) to end a session that you started in your account. If you click the **Terminate** button for a session in the console or call the [TerminateSession](https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_TerminateSession.html) API action by using the AWS CLI, Session Manager permanently ends the session and closes the data connection between the Session Manager client and SSM Agent on the managed node. You _can't_ resume a terminated session. @@ -11,3 +11 @@ You can end a session that you started in your account using the AWS Systems Man -If there is no user activity in an open session for 20 minutes, the idle state triggers a timeout. Session Manager doesn't call `TerminateSession`, but it does close the underlying channel. You can't resume a session closed because of idle timeout. - -We recommend always explicitly terminating a session by using the `terminate-session` command, when using the AWS CLI, or the **Terminate** button when using the console. (**Terminate** buttons are located on both the session window and main Session Manager console page.) If you only close a browser or command window, the session remains listed as **Active** in the console for 30 days. When you don't explicitly terminate a session, or when a session times out, any processes that were running on the managed node at the time will continue to run. +If there is no user activity in an open session for 20 minutes, the idle state triggers a timeout. Session Manager doesn't call TerminateSession, but it does close the underlying channel. You _can't_ resume a session closed because of idle timeout.