By using AWS re:Post, you agree to the Terms of Use

AppStream2 User gets Blank Screen

0

I am completely new to AppStream and AWS having used MS Azure for everything up until now.

Today I created an application using Elastic Fleet in AppStream2. I created a VHD file, uploaded it to a new S3 bucket and set JSON permissions from a document to allow the service to see the VHD file and script:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowAppStream2.0ToRetrieveObjects",
            "Effect": "Allow",
            "Principal": {
                "Service": "appstream.amazonaws.com"
            },
            "Action": "s3:GetObject",
            "Resource": [
                "arn:aws:s3:::my-app/appdrive2.vhdx",
                "arn:aws:s3:::my-app/mount-vhd.ps1",
                "arn:aws:s3:::my-app/icon.png"
            ]
        }
    ]
}

When the user logs in via the web interface, they see the icon from the S3 storage. When they click on the icon there are messages about reserving the session, setting up, etc; but then after about 2-3 minutes the screen just goes black.

As suggested on another post, I set up a new Fleet with Desktop access. There is no C:\AppStream folder, no mount points and I can't see the VHD being mounted or any errors about access or anything. I opened Firefox and tried to use the S3: uri and it cannot download the VHD.

I have found various articles talking about different access settings for the S3 and VPC, but I can't understand where I'm supposed to set this up and how it relates to the issue I am experiencing.

eg, this link - I can't see how it relates to the various objects in my setup?

https://docs.aws.amazon.com/appstream2/latest/developerguide/managing-network-vpce-iam-policy.html

1 Answers
0

As suggested on another post, I set up a new Fleet with Desktop access. There is no C:\AppStream folder, no mount points and I can't see the VHD being mounted or any errors about access or anything. I opened Firefox and tried to use the S3: uri and it cannot download the VHD.

Hi there - since you're not seeing an AppStream folder, and aren't able to download the objects in S3 using FireFox, the issue is most likely that the streaming instance doesn't have access to S3. Does the instance have access to the Internet? Try using a subnet with a NAT gateway that has complete access to the Internet as a starting point. Then that will help isolate the issue specifically.

Hope this helps.

EXPERT
answered 2 months ago
  • I created a new fleet with default internet access ticked. The Appstream folder is now created but it is empty. I can download from s3 using a timed url and get my script and app files, but they are not getting downloaded by the instance.

    I've followed all the instructions in the documentation, but it's too confusing about network access from the instance to see. There isn't anything clear to follow and the documents seem to contradict each other in terms of access and setup.

    Is there a clear step by step guide for everything I need to do to get elastic Appstream working for windows?

  • I've followed that tutorial. I still get a blank screen, I can see the C:\AppStream\AppBlocks\ProjectName folder but it is empty.

    The tutorial has completely different screens for creating VPCs to what are actually in the AWS dashboard, but I think I set everything up the same way.

    I can't understand what is wrong.

  • Is someone able to give me the exact bucket setup and permissions required for the 3 files on the S3 bucket. I have it set up with the bucket on default settings, with the permissions set as above and the 3 files uploaded into the bucket from my local computer (not an imagecreator instance). I'm now getting an empty C:\AppStream folder. The icon from my s3 bucket is visible in the web app.

  • Since the app icon is showing up on the AppStream 2.0 application catalog, your S3 bucket policy seems correct. Just to confirm - how does your VPC provide access to S3? Is it directly through the Internet, or is it through one of the S3 VPC endpoints (Gateway or VPC endpoint)? While default internet access implies using an Internet Gateway in your VPC to access S3, just wanted to confirm. If you haven't tried that, try removing the S3 gateway/VPC endpoint from the subnet route table, and provide full Internet access.

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.

Guidelines for Answering Questions