AWS appstream2 documentation change
Summary
Added a note explaining that existing instances continue running with old images during fleet updates, and suggests using drain mode for multi-session fleets to manage long-running instances with old images.
Security assessment
This change provides operational guidance for fleet updates and instance management. While it mentions security implications of running outdated images (potential security patches missing), it doesn't address a specific security vulnerability or add security features.
Diff
diff --git a/appstream2/latest/developerguide/update-fleets.md b/appstream2/latest/developerguide/update-fleets.md index 8adea7286..216c5fe73 100644 --- a//appstream2/latest/developerguide/update-fleets.md +++ b//appstream2/latest/developerguide/update-fleets.md @@ -47,0 +48,4 @@ After the image status changes to **Available** , you can update the fleet with +###### Note + +All existing instances and user sessions will continue to run with the old image, but all new instance launches will spin up from the new image. For multi-session fleets, it is possible that instances keep running with the older image for a longer duration of time because the service will not terminate an instance if there is an active session on the instance, and if user sessions keep getting provisioned on these instances, it is possible the instance will continue to run with the old image. To get rid of long-running instances on multi-session fleets, evaluate the option of putting them in drain mode. To learn more, refer to [Manage Multi-Session Fleet Instances](./manage-multi-session-instances.html). +