Questions tagged with Amazon AppStream
Content language: English
Sort by most recent
How does AppStream Disconnect Timeout state affect my app
We're migrating an app that currently saves its state and users' work every 10 minutes. Persistent storage is configured. I wonder what happens in a situation where a user accidentally disconnects before the next 10 minutes (let's assume that 8 minutes of work has passed and the user closes the browser tab). Will our application stay alive, so to say, and be able to write to S3? I understand that session is in a Disconnect timeout state but will our app be able to save the last work made by a user in this state? Or does the instance enter some kind of hibernate state? ![Enter image description here](/media/postImages/original/IM8E6sy8IsQn2Pf_HgRw5Lew)
AppStream timeouts and auto scaling
When using Application Auto Scaling with AppStream Fleet is this assumption correct (see picture below)? ![Enter image description here](/media/postImages/original/IM2mXHSEdBTYefmn_AO-V3GQ) What I mean is: does the Instances in Idle and Disconnect Timeouts count as a Running Capacity and are included in CapacityUtilization within CloudWatch Alarms metrics? Is the assumption correct that cooldown and evaluation period would be picked up by CloudWatch alarm after the Timeouts have expired?
What path to specify for Apps Working Directory
I'm using an Image Builder and in step 1 when I try to configure Working Directory for the installed application I cannot specify **C:\Users\PhotonUser\My Files\Home Folder** because it's not even listed (one cannot type it in either): ![Enter image description here](/media/postImages/original/IMei_JoJtpSB2pXfvI4f9WOw) The stack that will use that Image has Home folders enabled and when the fleet is running the Home folders are present, but I want to configure the default app behavior to use the Home Folder path so users wouldn't need to change it. Doing the same while logged in as Template User won't work because as I understand it the persistent storage (S3) isn't even mounted while creating an Image (Home Folder isn't listed) ![Enter image description here](/media/postImages/original/IMMhtQNvewRgChx7m1UYtVgw) So my question is: what path to Working Directory am I supposed to provide at this stage to enable default persistent storage path for an app and users?
What happens with AppStream session in case of instance failure
I'm in the developing phase of an AppStream application. My team is wondering if there are any guardrails for session users in case of an instance failure. What happens to users' data in that case? Is the data retrievable? Will the instance be automatically replaced with the new one with users' data? Those are relevant questions that a potential end-user might ask when working with delicate and time-consuming workloads, but I wasn't able to find any answers in AppStream documentation.
AppStream stopped working in Safari on MacOS
Our AppStream app has recently stopped working in Safari on MacOS. It works fine in Chrome on MacOS and on Windows. The fleet instance appears to start but the UI hangs while displaying Connecting. If I put Safari in developer mode and change the user agent to something other than the default Safari one, for instance to impersonate a Chrome or Edge or FireFox Mac browser, then the browser connects to the streamed app. Is there some new limitation on streaming applications only to Safari on MacOS or is this a bug?
Application xxx could not be launched successfully
For the first time in about 6 months, we're updating our AWS application (with no environmental type changes at all). But in the 'configure' phase of running the Appstream 2.0 Image Assistant, when we try to start the app, we immediately get a dialog box that says "Application xxx could not be launched successfully. Check that the application was installed properly , does not require elevated privileges to launch, or is not part of a user folder hierarchy." We can execute the app successfully out of its 'C:' drive home just fine, up to the point where it needs the environment as set up by Appstream, so we don't think it's anything to do with the application itself. And in any case, we haven't changed anything outside the standard functionality of our application. We haven't been able to find any useful references to the message via a web search. We're wondering if there's been an Appstream change in the last 6 months or so (and what to do about it if so), or if anyone has any ideas about what might now be wrong. Thanks!
Domain-join AppStream fleet profile management issue
We are trying to deploy FSLogix profile management to a domain-joined AppStream fleet. We are also using folder redirection. Every time we try to enable profile management, I get a series of errors when the user logins in that they don't have permissions to the redirected folders of the test user. I'm using a domain user for the testing part of the sealing process, and it is applying the test user's redirected folders to any user that logs in instead of the logged in user's redirected folders. Of course the logged in user doesn't have rights to those folders and these are not the folders we need to access anyway. Anyone, know how to resolve this issue? ![![Enter image description here](/media/postImages/original/IMBgU5bHFHT4SUc2PTKvqJbg) Enter image description here](/media/postImages/original/IMqGmD-EHGQNedUDtUEA1INQ)
Printing to DCV printer from Appstream will result in .xps file where .pdf is expected
We use Appstream 2 to host an application, which is accessed by our users via a browser. Within this environment, users have a DCV printer available. For most users, printing to the DCV printer results in a PDF file to become available in a separate browser tab. But for 1 user printing results in a XPS file. I can't find how to change this to PDF for him.
In App Stream 2.0 Getting error An unknown error occurred (1355).
Hi, I am trying to setup the ADFS with App Stream 2.0 with SAML Authentication, and have done all the steps for the needful (Referred from : https://aws.amazon.com/blogs/compute/enabling-identity-federation-with-ad-fs-3-0-and-amazon-appstream-2-0/ ) , but after login to App Stream relay state URL screen, system gives an error: "An unknown error occurred (1355)." As per my research its indicating some DNS issue. When we have checked my system ip configs, its displaying something like this : > **Windows IP Configuration** ( Host Name : EC2AMAZ-NMGRP10 [this is my server system name], Primary Dns Suffix : example.local. > **Ethernet adapter Ethernet** : Connection-specific DNS Suffix : sarvajeevan.com DNS Servers : ::1 127.0.0.1 Username for App Stream is : email@example.com As per my understanding, our Active directory domain name is **sarvajeevan.com**, but internal federation domain is **example.local**. Please help us to understand, we are doing something wrong or something needs to fix manually from Route 53 or something else ? Thanks
AppStream - Visual FoxPro App
Hi, I am new to appstream and running into an issue I'm not sure how fix. Installed a VSP app and it runs fine under Admin. Switch to the other users, both can run it also if I just launch the EXE. I'm mapping the initialization datafiles to %USERPROFILE% so it picks up which user is logged in and looking to setup home directories with S3. However, when I add to the image builder, it will not launch and says it can't find files under c:\program files\amazon\photon\ ... which is not even the directory I have the app running. Any pointers? Thank you.
Anyone else getting blank password window when streaming MS Office App
When I attempt to stream and MS Office app (in my case Visio) I get the sign in request. I successfully respond to username request then the password request never comes up. Just a blank pane where the request would normally appear. Has anyone else experienced this and can suggest solution?