D: Drive and S3 Bucket Not Visible in App Stream

This issue with the missing D: drive in your AppStream 2.0 environment for the BluAge L3 Workshop is a common problem. Here are some potential causes and solutions:

1. User ID verification: Double-check that you're consistently using the exact same User ID "BluAge-L3-Workshop-User" when creating streaming URLs. Even slight variations in the User ID will result in a new, clean session without your previous data.

2. Persistent storage location: In AppStream 2.0, only data stored in D:/PhotonUser is typically persisted between sessions. If you stored data outside this directory, it may not be synchronized with the S3 bucket and could be lost when the session ends.

3. S3 bucket investigation: Your user settings and files are typically stored in S3 buckets with names starting with "appstream2-app-settings-" and "appstream2-" respectively. Check if these buckets exist in your account.

4. Storage configuration: Verify that persistent storage is properly enabled for your AppStream fleet and stack.

5. Creating the directory structure: If the D: drive exists but the PhotonUser folder is missing, you might need to create it manually using commands like:

mkdir D:\PhotonUser
mkdir D:\PhotonUser\Workshop

6. Disk space: Check if the disk is full, as this can sometimes cause the D: drive to not appear properly.

7. Fleet restart: After making any changes to your configuration, try restarting your fleet and creating a new streaming URL with the exact same User ID.

If you've already recreated the fleet and stack multiple times as mentioned, you might need to contact AWS support for further assistance, as there might be specific configurations or limitations in your AppStream 2.0 environment causing this problem.
Sources
Can't see my D drive | AWS re:Post
Blu Age L3 Workshop AppStream - Start Local Database Server not running | AWS re:Post
Appstream: Original Appstream link is expired after 7 days, Application Persistent storage is active, New appstream link doesnt show the workspace in D:\ and configuration is reset. | AWS re:Post