1 Answer
- Newest
- Most votes
- Most comments
1
Hi,
an improvement on your current situation is to run the browser update process in your AppStream Builder when you refresh the image of your fleet.
If you automate this image refresh fully (via scripting) to make it very frequent then, your browsers will stay up-to-date.
Best,
Didier
Relevant content
- Accepted Answerasked 2 years ago
AWS OFFICIALUpdated 6 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Thanks Didier. Do you know if it would be possible to run the browser update process when using AppStream's native image update feature (e.g. by calling the CreateUpdatedImage feature of the API) or would I need to deploy to an Image Builder instance first?
Managed Image Update (CreateUpdatedImage API) do not update the applications. It will only update AppStream 2.0 components and Windows patches. You will need to update the application and create a new image again, then update you fleet with the new image.
Refer the documentation for more details. https://docs.aws.amazon.com/appstream2/latest/developerguide/administer-images.html#keep-image-updated-managed-image-updates
Additionally updating the browsers on the fly on the fleet instance is not recommended as it can utilize the resources and cause performance issue. It may also create issue in the streaming session (with the app itself). So, it's good practices to update application on the image itself.