Help improve AWS Support Official channel in re:Post and share your experience - complete a quick three-question survey to earn a re:Post badge!
What happens if an AppStream 2.0 Stack is not active?
Hi Community,
I am doing the BluAge L3 training.
I created a fleet, linked it to the latest image. Created a stack but my stack doesn't show the active status, when creating my stack I had the below error about the time zone. I then disabled the time zone and I managed to create the stack, but my stack doesn't even show that it is active.
I can't find the D: as part of my drives when I launch the AppStream desktop, only the C:
I followed all the steps as per the demo.
I am not sure what could have went wrong, your help would be greatly appreciated.
- Newest
- Most votes
- Most comments
Based on the information provided, it appears you're experiencing a few issues with your AppStream 2.0 setup. Let's address them one by one:
-
Stack Status: If your stack is not showing as active, it could mean that the associated fleet is not in a running state or there might be configuration issues. Ensure that your fleet is properly configured and in a running state.
-
Time Zone Error: The error you encountered regarding the time zone is not typical and may indicate a problem with the image or fleet configuration. Disabling the time zone setting allowed you to create the stack, but it might not be the ideal solution.
-
Missing D: Drive: In AppStream 2.0, the D: drive is typically associated with user storage, such as home folders. If you can't see the D: drive, it's possible that home folders or other persistent storage options are not enabled for your stack.
To troubleshoot these issues:
- Check your fleet status and ensure it's properly configured and running.
- Review your stack settings, particularly the storage options. Make sure home folders or other persistent storage options are enabled if you need the D: drive.
- Verify that your image is correctly configured and compatible with your fleet and stack settings.
- If the issues persist, you may need to recreate the stack and ensure all settings are correctly applied during the creation process.
If you continue to experience problems, it would be helpful to review the AppStream 2.0 console logs and check for any error messages or warnings that might provide more insight into the root cause of these issues.
Sources
Disable Home Folders - Amazon AppStream 2.0
AWS BluAge AppStream - workspace folder disappeared due to streaming URL expired | AWS re:Post
General Troubleshooting - Amazon AppStream 2.0
D: drive doesn't show on file explorer by default, you must write D: in the address bar in order to see it.