Amazon AppStream 2.0
Developer Guide

Get Started with Amazon AppStream 2.0: Set Up With Sample Applications

To stream your applications, Amazon AppStream 2.0 requires an environment that includes a fleet that is associated with a stack, and at least one application image. This tutorial describes how to configure a sample AppStream 2.0 environment for application streaming and give users access to that stream.


For additional guidance in learning how to get started with AppStream 2.0, see the Amazon AppStream 2.0 Getting Started Guide. This guide describes how to install and configure two applications, perform foundational administrative tasks using the AppStream 2.0 console, and provision an Amazon Virtual Private Cloud by using a provided AWS CloudFormation template.

Step 1: Set Up a Sample Stack, Choose an Image, and Configure a Fleet

Before you can stream your applications, you need to set up a stack, choose an image that has applications installed, and configure a fleet. In this step, you use a template to help simplify these tasks.

To set up a sample stack, choose an image, and configure a fleet

  1. Open the AppStream 2.0 console at

  2. Choose Get Started if you are new to the console, or Quick Links from the left navigation menu. Choose Set up with sample apps.

  3. For Step 1: Stack Details, keep the default stack name or enter your own. Optionally, you can provide the following:

    • Display name — Enter a name to display for the stack (maximum of 100 characters).

    • Description— Keep the default description or enter your own (maximum of 256 characters).

    • Redirect URL — Specify a URL to which users are redirected after their streaming sessions end.

    • Feedback URL — Specify a URL to which users are redirected after they click the Send Feedback link to submit feedback about their application streaming experience. If you do not specify a URL, this link is not displayed.

  4. Choose Next.

  5. For Step 2: Choose Image, choose an image, and then choose Next. The sample image contains pre-installed open source applications for evaluation purposes. For more information, see AppStream 2.0 Base Image Version History.

  6. For Step 3: Configure Fleet, we recommend that you keep the default values and choose Next. You can change most of these values after fleet creation.

    • Choose instance type — Choose the instance type that matches the performance requirements of your applications. All streaming instances in your fleet launch with the instance type that you select. For more information, see AppStream 2.0 Instance Families.

    • Fleet type — Choose the fleet type that suits your use case. The fleet type determines its immediate availability and how you pay for it.

    • Maximum session duration — Choose the maximum amount of time that a streaming session can remain active. If users are still connected to a streaming session five minutes before this limit is reached, they are prompted to save any open documents before being disconnected.

    • Disconnect timeout — Choose 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. Otherwise, they are connected to a new session with a new instance. If you associate a stack with a fleet for which a redirect URL is specified, after users’ streaming sessions end, the users are redirected to that URL.

      If a user ends the session by choosing End Session on the streaming session toolbar, the disconnect timeout does not apply. Instead, the user is prompted to save any open documents, and then immediately disconnected from the streaming instance.

    • Minimum capacity — Choose a minimum number of instances for your fleet based on the minimum number of expected concurrent users. Every unique user session is served by an instance. For example, to have your stack support 100 concurrent users during low demand, specify a minimum capacity of 100. This ensures that 100 instances are running even if there are fewer than 100 users.

    • Maximum capacity — Choose a maximum number of instances for your fleet based on the maximum number of expected concurrent users. Every unique user session is served by an instance. For example, to have your stack support 500 concurrent users during high demand, specify a maximum capacity of 500. This ensures that up to 500 instances can be created on demand.

  7. For Step 4: Configure Network, choose an Amazon VPC and two subnets with access to the network resources that your application needs, and then choose Next. If you don't have a VPC or subnets, you can create them using the links provided and then click the refresh icons. For Security groups, you can select up to five security groups. Otherwise, the default security group is used. For more information, see Networking, Access, and Security for Amazon AppStream 2.0.

  8. For Step 5: Enable Storage, choose one or more of the following, then choose Next.

    • Enable Home Folders — By default, this setting is enabled. Keep the default setting. For information about requirements for enabling home folders, see Enable Home Folders for Your AppStream 2.0 Users.

    • Enable Google Drive — Optionally, you can enable users to link their Google Drive for G Suite account to AppStream 2.0. You can enable Google Drive for accounts in G Suite domains only, not for personal Gmail accounts. For information about requirements for enabling Google Drive, see Enable Google Drive for Your AppStream 2.0 Users.

    • Enable OneDrive — Optionally, you can enable users to link their OneDrive for Business account to AppStream 2.0. You can enable OneDrive for accounts in OneDrive domains only, not for personal accounts. For information about requirements for enabling OneDrive, see Enable OneDrive for Your AppStream 2.0 Users.

  9. For Step 6: User Settings, select the ways in which your users can transfer data between their streaming session and their local device. Then, choose whether to enable application settings persistence. When you're done, choose Review:

    Clipboard, file transfer, and print to local device permissions options:

    • Clipboard — By default, users can copy and paste data between their local device and streaming applications. You can limit Clipboard options so that users can paste data to their remote streaming session only or copy data to their local device only. You can also disable Clipboard options entirely. Note that users can still copy and paste between applications in their streaming session.

    • File transfer — By default, users can upload and download files between their local device and streaming session. You can limit file transfer options so that users can upload files to their streaming session only or download files to their local device only. You can also disable file transfer entirely.

    • Print to local device — By default, users can print to their local device from within a streaming application. When they choose Print in the application, they can download a .pdf file that they can print to a local printer. You can disable this option to prevent users from printing to a local device.


    These settings affect only whether users can use AppStream 2.0 data transfer features. If your image provides access to a browser, network printer, or other remote resource, your users might be able to transfer data to or from their streaming session in other ways.

    Application settings persistence options:

    • Enable Application Settings Persistence — Users' application customizations and Windows settings are automatically saved after each streaming session and applied during the next session. These settings are saved to an Amazon Simple Storage Service (Amazon S3) bucket in your account, within the AWS Region in which application settings persistence is enabled.

    • Settings Group — The settings group determines which saved application settings are used for a streaming session from this stack. If the same settings group is applied to another stack, both stacks use the same application settings. By default, the settings group value is the name of the stack.


    For information about requirements for enabling and administering application settings persistence, see Enable Application Settings Persistence for Your AppStream 2.0 Users.

  10. For Step 7: Review, confirm the details for the stack. To change the configuration for any section, choose Edit and make the needed changes. After you finish reviewing the configuration details, choose Create.

  11. After the service sets up resources, the Stacks page appears. The status of your new stack appears as Active when it is ready to use.

    Optionally, you can apply one or more tags to help manage the stack. Choose Tags, choose Add/Edit Tags, choose Add Tag, specify the key and value for the tag, and then choose Save. For more information, see Tagging Your Amazon AppStream 2.0 Resources.

Step 2: Provide Access to Users

After you create a stack with an associated fleet, you can provide access to users through the AppStream 2.0 user pool, SAML 2.0 [single sign-on (SSO)], or the AppStream 2.0 API. For more information, see User Pool Administration and Single Sign-on Access to AppStream 2.0 Using SAML 2.0.


Users in the AppStream 2.0 user pool can't be assigned to stacks with fleets that are joined to an Active Directory domain.

For this getting started exercise, you can use the AppStream 2.0 user pool. This access method enables you to create and manage users by using a permanent login portal URL. To quickly test application streaming without setting up users, complete the following steps to create a temporary URL.

To provide access to users with a temporary URL

  1. In the navigation pane, choose Stacks. Select the stack, and then choose Actions, Create Streaming URL.

  2. For User id, type the user ID. Choose an expiration time, which 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.

After you provide your users with access to AppStream 2.0, they can start AppStream 2.0 streaming sessions. If you provide access through the AppStream 2.0 user pool, they must use a web browser for streaming sessions.

If you plan to use SAML 2.0 [single sign-on (SSO)] or the AppStream 2.0 API to provide access to your users, you can make the AppStream 2.0 client available to them. The AppStream 2.0 client is a native application that is designed for users who require additional functionality during their AppStream 2.0 streaming sessions. For more information, see The AppStream 2.0 Client.


For more information, see the following: