Menu
Amazon AppStream 2.0
Developer Guide

Getting Started with Amazon AppStream 2.0

To stream your applications, Amazon AppStream 2.0 requires an environment consisting of a stack and at least one application image. This topic walks through the steps for putting together a sample AppStream 2.0 environment for application streaming and give users access to that stream.

Step 1: Set up a Sample Stack

Before you can stream your applications, you need to create a stack. In this step, you create a new stack from the sample stack template to simplify the creation.

To set up the AppStream 2.0 sample stack

  1. Open the AppStream 2.0 console at https://console.aws.amazon.com/appstream2.

  2. Choose Get Started if you are visiting the service console for the first time, or Quick Links from the left navigation menu of the service console.

  3. Choose Set up with sample apps. For Step 1: Stack Details, choose Next to use the default sample stack name and details, or enter your own details and then choose Next.

  4. For Step 2: Choose Image, review the image details for the sample apps and choose Next to use the default image. The sample apps image contains a few pre-installed open source applications for evaluation purposes. Choose the latest sample apps image, for example Amazon-AppStream2-Sample-Image-MM-DD-YYYY, where MM-DD-YYYY is the latest release date. For more information, see Amazon AppStream 2.0 Windows Image Version History.

  5. For Step 3: Configure Fleet, provide the details for your fleet. Most values are pre-populated for you. If you are unsure about a setting, use the default.

    Instance Type — Choose an instance type that matches the performance requirements of your applications. All streaming instances in your fleet launch with the instance type that you select.

    Disconnect Timeout — Select the time that a streaming instance should remain active after users disconnect. If users try to reconnect to the streaming session after a disconnection or network interruption within this time interval, they are connected to the previous session. If users try to connect after this timeout interval, a session launches with a new instance.

    Minimum Capacity — Choose a minimum capacity for your fleet based on the minimum number of expected concurrent users. Capacity is defined in terms of the number of instances within a fleet, and every unique user session is served by an instance. For example, to have your stack support 100 concurrent users during low demand, enter the minimum capacity as 100. This ensures that 100 instances are running even if there are fewer than 100 users. If you are unsure about minimum capacity, accept the default value.

    Maximum Capacity — Choose a maximum capacity for your fleet based on the maximum number of expected concurrent users . Capacity is defined in terms of the number of instances within a fleet, and every unique user session is served by an instance. For example, to have your stack support 500 concurrent users during high demand, enter the maximum capacity as 500. This ensures that up to 500 instances can be created on demand. If you are unsure about maximum capacity, accept the default value.

    Scaling Details (Advanced) — This section contains default scaling policies that can increase and decrease the capacity of your fleet under specific conditions. Expand this section to change the default scaling policy values. Regardless of scaling policy, your fleet size is always in the range of values specified by Minimum Capacity and Maximum Capacity.

    We recommend that you accept the default values and choose Next. You can change these values after fleet creation. For more information, see Fleet Auto Scaling for Amazon AppStream 2.0.

  6. For Step 4: Configure Network, provide two subnets that have access to the network resources with which your applications need to interact. If you don’t have any subnets, create them using the help link provided and then refresh the subnets list. Select up to five security groups for the fleet VPC. If no security group is selected, the default security group is used. You can choose existing network settings or create new settings for this fleet. For more information, see Network Settings for Fleet and Image Builder Instances.

  7. Step 5: Enable Storage is where you choose to have Home Folders enabled. Home Folders offer persistent storage for AppStream 2.0 streaming sessions. For more information, see Persistent Storage with AppStream 2.0 Home Folders. We recommend that you enable this option and choose Review.

  8. Review the details for the sample stack, choose Edit for any section to change, and then choose Create.

After the service sets up some resources, the Stacks dashboard appears. Your new stack is listed as Active when it is available to work with from the console. The stack cannot be used for streaming sessions until the stack fleet is in Running status.

Step 2: Provide Access to Users

After you create a stack, each user needs an active URL for access. The AppStream 2.0 User Pool feature enables you to create and manage users, using a permanent login portal URL. For more information, see Using the AppStream 2.0 User Pool. To quickly test application streaming without setting up users, create a temporary URL as shown below.

To provide access to users with a temporary URL

  1. In the navigation pane, choose Stacks, select the stack to use, check that the fleet status is Running, and then choose Actions, Create Streaming URL.

  2. For UserID, type the user ID and select an expiration time. This time determines how long the generated URL is valid.

  3. To view the user ID and URL, choose Get URL.

  4. To copy the link to the clipboard, choose Copy Link.

  5. Choose Exit.

Next Steps

At this point, you can create user pool users, monitor your resources and make decisions about managing them. For more information, see the following topics.