AWS res documentation change
Summary
Clarified data loss implications and corrected hibernation behavior description (state saved to disk instead of memory)
Security assessment
Changes clarify operational behavior of desktop states (stop, terminate, hibernate) and correct a technical inaccuracy about hibernation (saving to disk vs. memory). These are operational clarifications with no direct security implications, though they help users understand data persistence risks.
Diff
diff --git a/res/latest/ug/control-desktop-state.md b/res/latest/ug/control-desktop-state.md index 30e433f9b..2661ce18c 100644 --- a//res/latest/ug/control-desktop-state.md +++ b//res/latest/ug/control-desktop-state.md @@ -17 +17 @@ To control your desktop's state: -A stopped session will not suffer data loss, and you can restart a stopped session at any time. +Stopping a session does not cause data loss, and you can restart a stopped session at any time. @@ -25 +25 @@ Reboots current session. -Permanently ends a session. Terminating a session may cause data loss if you are using ephemeral storage. You should backup your data to the RES filesystem before terminating. +Permanently ends a session. Terminating a session may cause data loss if you are using ephemeral storage. Back up your data to the RES filesystem before terminating. @@ -29 +29 @@ Permanently ends a session. Terminating a session may cause data loss if you are -Your desktop state will be saved in memory. When you restart the desktop, your applications will resume but any remote connections may be lost. Not all instances support hibernation, and the option is only available if it was enabled during instance creation. To verify if your instance supports this state, see [Hibernation prerequisites](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/hibernating-prerequisites.html). +Your desktop state is saved to disk. When you restart the desktop, your applications resume but any remote connections may be lost. Not all instances support hibernation, and the option is only available if it was enabled during instance creation. To verify if your instance supports this state, see [Hibernation prerequisites](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/hibernating-prerequisites.html).