Skip to content

Unable to associate AppStream Fleet to Stack

0

Hi,

I'm currently taking the AWS Blu Age L3 self-paced troubleshooting workshop to achieve L3 certification, and I've encountered an issue. During the 'Setup Environment' step in the 'Refactoring' section, I'm required to create an AppStream Fleet and Stack.

I successfully created the Fleet using the shared BluAge-L3-Workshop-Image-4-2-0, but when I attempt to associate the Fleet instance with the stack, I receive this error:

"The fleet 'BluAge-L3-Workshop-Fleet' cannot be associated with stack 'BluAge-L3-Workshop-Stack' because it is set up for Auto Time Zone Redirection. The image 'BluAge-L3-Workshop-Image-4-2-0' does not support this feature. Please update the AppStream 2.0 agent version used by your image to enable Auto Time Zone Redirection."

There was a similar question that has been asked on here (https://repost.aws/questions/QUSc2Qbj5JT9Wirg10T16MYA/error-when-associating-appstream-fleet-to-stack). The answer was along the lines of either change the fleet configuration by unchecking the "Enable Auto Time Zone Redirection" option in the Fleet details section or update the AppStream 2.0 agent version. I can't do the latter option since it requires permissions. As for the former, I don't see the option "Enable Auto Time Zone Redirection" in my fleet configuration.

Fleet details not showing time zone configuration

3 Answers
1
Accepted Answer

The issue you're experiencing is due to a mismatch between the AppStream 2.0 agent version in the image and the fleet configuration. The error message indicates that the fleet is set up for Auto Time Zone Redirection, but the image doesn't support this feature.

Since you don't have the option to update the AppStream 2.0 agent version in the image, and you can't see the "Enable Auto Time Zone Redirection" option in your fleet configuration, there are a few steps you can try:

  1. Double-check the fleet configuration: Even though you don't see the specific option, look for any settings related to time zones or user experience. Sometimes, these settings might be grouped under a different category.

  2. Create a new fleet: Try creating a new fleet from scratch using the same image. When setting up the new fleet, pay close attention to all options, especially those related to user settings or time zones. Avoid selecting any advanced features that the older image might not support.

  3. Check stack settings: Although the error seems to be related to the fleet, review your stack settings as well. Ensure there are no conflicting configurations between the stack and the fleet.

  4. Consult workshop materials: Since this is part of a workshop, check if there are any specific instructions or known issues mentioned in the workshop materials regarding this step. There might be a particular way to configure the fleet that's required for the workshop.

  5. Contact workshop support: If none of the above steps resolve the issue, reach out to the workshop organizers or AWS support channels provided for the workshop. They may be aware of this specific issue and can provide tailored guidance.

Remember, in a real-world scenario, updating the AppStream 2.0 agent in the image would typically be the most straightforward solution. However, given the constraints of the workshop environment, you'll need to work within the available options to resolve this configuration mismatch.
Sources
Troubleshooting AppStream 2.0 User Issues - Amazon AppStream 2.0
Step 4: Create your stack - Tableau Desktop on Amazon AppStream 2.0

answered 2 years ago

EXPERT

reviewed 2 years ago

0

Unselect "Set time zone automatically for remote sessions" in the Step 3 "Edit User Setting" during the creation of the AppStream Stack. Kelvin Yeung

AWS

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.