- Newest
- Most votes
- Most comments
Hi,
You can just create a new Streaming URL from the stack so that you can have a new Appstream Fleet instance running.
Follow these steps: https://docs.aws.amazon.com/appstream2/latest/developerguide/use-client-start-streaming-session.html#use-client-start-streaming-session-streaming-URL
Please note that Appstream is non-persistent. You will lose all work done on the fleet instance by default, unless you saved your data under the HOME_FOLDER. If so, you can access these data again on your new session (be sure though that you are using the same User ID)
answered 2 years ago
Scenario/ Issue:
When the streaming URL of an AppStream 2.0 stack expires, a new streaming URL must be generated to continue working. To access the existing data, the same User ID must be used when regenerating the streaming URL. If a different User ID is used (by mistake), a new instance will be created without any existing data in it.
This troubleshooting guide presents a way to retrieve the original instance, which contains all your existing data.
Troubleshooting Steps:
- Terminate any running session of the AppStream stack.
- Go to S3 and navigate to a path similar to: s3://appstream-app-settings-... /Windows/version/Server-2019/BluAge-L3-Workshop-Stack/custom/ (e.g., s3://appstream-app-settings-eu-central-1-820242900304-4la3rs9b/Windows/v6/Server-2019/BluAge-L3-Workshop-Stack/custom/ ).
- There you will see more than one key, each one corresponding to each stack instance you might have created. You need to carefully delete all the keys EXCEPT the ONLY ONE which is having the largest sized Profile.vhdx file in it.
- Now, go back to your AppStream 2.0 stack and create a streaming URL with the exact same User ID as your original streaming URL, and launch it. You should get back all your data.
answered 2 years ago
Relevant content
asked a year ago
