- Newest
- Most votes
- Most comments
Apart from the suggestion provided by Alae, one other common mistake I have observed with my colleagues, not using the correct user ID while creating the streaming URL. If you see the step5, the user ID is "BluAge-L3-Workshop-User". If the URL was created with this for the first time, then all future URLs must be created with the same user ID. Otherwise a completely clean session gets created with the provided new user ID.
You can verify if you may have also done the same mistake in couple of ways, and the easiest way is to look at the Bill breakup. If there are more than 1 user against "$4.19 per user per month for RDS SAL User Fees in AWS region", then this is likely the reason for not getting the files synced.
Create a streaming URL Follow the steps below:
- Navigate to AppStream 2.0 service
- Click on Stacks menu (on left)
- Select BluAge-L3-Workshop-Stack
- Click on Action menu and select Create Streaming URL
- Set User ID to BluAge-L3-Workshop-User
- Set URL expiration to 7 Days
Files stored outside **D:/PhotonUser/My Files ** are not synchronized with the S3 bucket and may be lost when session is over.
Take a look at this
answered 2 years ago
The issue was with user id while creating a stack. When the user ID was given as BluAge-L3-Workshop-User it worked. Thanks for support
Relevant content
asked 2 years ago
asked 10 months ago
asked a year ago
- AWS OFFICIALUpdated 8 months ago

Thanks for pointing out this. This was indeed the issue I faced.