Update a Fleet with a New Image in Amazon WorkSpaces Applications
To apply operating system updates or make new applications available to users, create a new image that has these changes. Then, update the fleet with the new image.
To update an WorkSpaces Applications fleet with a new image
-
Connect to the image builder that you want to use and sign in with an account that has local administrator permissions on the image builder. To do so, do either of the following:
-
Use the WorkSpaces Applications console (for web connections only)
-
Create a streaming URL (for web or WorkSpaces Applications client connections)
Note
If your organization requires smart card sign in, you must create a streaming URL and use the WorkSpaces Applications client for the connection. For information about smart card sign in, see Smart Cards.
-
-
Do either or both of the following as required:
-
Install updates to the operating system.
-
Install applications.
If an application requires the Windows operating system to restart, let it do so. Before the operating system restarts, you are disconnected from your image builder. After the restart is complete, connect to the image builder again, then finish installing the application.
-
-
On the image builder desktop, open Image Assistant.
-
Follow the necessary steps in Image Assistant to finish creating your image. For more information, see Tutorial: Create a Custom WorkSpaces Applications Image by Using the WorkSpaces Applications Console.
After the image status changes to Available, you can update the fleet with your new image.
-
In the left navigation pane, choose Fleets.
-
Select the fleet that you want to update with the new image.
-
On the Fleet Details tab, choose Edit.
-
In the Edit Fleet dialog box, the list of available images displays in the Name list. Select the new image from the list.
-
Choose Update.
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.
