Menu
Amazon AppStream 2.0
Developer Guide

Create AppStream 2.0 Fleets and Stacks

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 the steps to set up a fleet and stack, and how to give users access to the stack. If you haven't already done so, we recommend that you try the procedures in Getting Started with Amazon AppStream 2.0 first.

If you want to create an image to use, see Tutorial: Create a Custom Image.

If you plan to join a fleet to an Active Directory domain, configure your Active Directory domain before completing the following steps. For more information, see Using Active Directory with AppStream 2.0.

Create a Fleet

Set up and create a fleet from which user applications are launched and streamed.

To set up and create a fleet

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

  2. Choose Get Started if you are new to the console, or Fleets from the left navigation pane. Choose Create Fleet.

  3. For Step 1: Provide Fleet Details, provide a fleet name, optional display name, and optional description. Choose Next.

  4. For Step 2: Choose an Image, choose an image that meets your needs and then choose Next.

  5. For Step 3: Configure Fleet, do the following:

    1. For Choose instance type, choose the instance type that meets the performance requirements of your applications.

    2. For Fleet type, choose the fleet type that suits your use case. The fleet type determines its immediate availability and how you pay for it.

    3. For Maximum session duration — Choose the maximum amount of time that a streaming session can remain active. If users are still connected to a streaming instance five minutes before this limit is reached, they are prompted to save any open documents before being disconnected. After this time elapses, the instance is terminated and replaced by a new instance.

    4. For Disconnect timeout, choose the time that a streaming session should remain active after users disconnect. If users try to reconnect to the streaming instance 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. The instance the user was using is then terminated.

    5. For Minimum capacity, choose a minimum number of instances for your fleet based on the minimum number of expected concurrent users.

    6. For Maximum capacity, choose a maximum number of instances for your fleet based on the maximum number of expected concurrent users.

    7. For Scaling details, specify the scaling policies that AppStream 2.0 uses to increase and decrease the capacity of your fleet. Note that the size of your fleet is limited by the minimum and maximum capacity that you specified. For more information, see Fleet Auto Scaling for Amazon AppStream 2.0.

  6. For Step 4: Configure Network, do the following:

    1. To add internet access for fleet instances in a VPC with a public subnet, choose Default Internet Access. If you are providing internet access using a NAT gateway, leave Default Internet Access unselected. For more information, see Network Settings for Amazon AppStream 2.0 .

    2. Choose a VPC and two subnets with access to the network resources that your application needs. If you don't have a VPC or subnets, you can create them using the links provided and then click the refresh icons.

    3. For Security groups, select up to five security groups to associate with this fleet. Otherwise, the default security group for the VPC is used. If you need to create a security group, use the link provided and then click the refresh icon.

    4. For Active Directory Domain (Optional), choose the Active Directory and organizational unit (OU) for your streaming instance computer objects. Ensure that the network access settings you selected enable DNS resolvability and communication with your directory. For more information, see Using Active Directory with AppStream 2.0.

  7. Choose Create.

    While your fleet is being created and fleet instances are provisioned, the status of your fleets displays as Starting in the Fleets list. Choose the Refresh icon periodically to update the fleet status until the status is Running. You cannot associate the fleet with a stack and use it for streaming sessions until the status of the fleet is Running.

    Optionally, you can apply one or more tags to help manage the fleet. 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.

Create a Stack

Set up and create a stack to control access to your fleet.

To set up and create a stack

  1. In the left navigation pane, choose Stacks, and then choose Create Stack.

  2. For Step 1: Stack Details, provide a stack name. Optionally, you can provide the following:

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

    • Description— Enter a description for the stack (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.

    • Fleet — Select an existing fleet or create a new one to associate with your stack.

  3. Choose Next.

  4. For Step 2: Enable Storage, you can provide persistent storage for your users by choosing one or more of the following:

    • Home Folders — Users can save their files to their home folder and access existing files in their home folder during application streaming sessions. For information about requirements for enabling home folders, see Enable Home Folders for Your AppStream 2.0 Users.

    • Google Drive for G Suite — Users can link their Google Drive for G Suite account to AppStream 2.0. During application streaming sessions, they can sign in to their Google Drive account, save files to Google Drive, and access their existing files in Google Drive. You can enable Google Drive for accounts in G Suite domains only, not for personal Gmail accounts.

      Note

      After you select Enable Google Drive, type the name of at least one organizational domain that is associated with your G Suite account. Access to Google Drive during application streaming sessions is limited to user accounts that are in the domains that you specify. You can specify up to 10 domains. For more information about requirements for enabling Google Drive, see Enable Google Drive for Your AppStream 2.0 Users.

    • OneDrive for Business — Users can link their OneDrive for Business account to AppStream 2.0. During application streaming sessions, they can sign in to their OneDrive account, save files to OneDrive, and access their existing files in OneDrive. You can enable OneDrive for accounts in OneDrive domains only, not for personal accounts.

      Note

      After you select Enable OneDrive, type the name of least one organizational domain that is associated with your OneDrive account. Access to Google Drive during application streaming sessions is limited to user accounts that are in the domains that you specify. You can specify up to 10 domains. For more information about requirements for enabling OneDrive, see Enable OneDrive for Your AppStream 2.0 Users.

  5. Choose Next.

  6. For Step 3: User Settings, select the ways in which your users can transfer data between their streaming session and their local device. When you're done, choose Review:

    • 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, or you can 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, or you can 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.

    Note

    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.

  7. For Step 4: 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.

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.

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. For more information, see User Pool Administration.

Note that user pool users cannot be assigned to stacks with fleets that are joined to an Active Directory domain.

Clean Up Resources

You can stop your running fleet and delete your active stack to free up resources and to avoid unintended charges to your account. We recommend stopping any unused, running fleets.

Note that you cannot delete a stack with an associated fleet.

To clean up your resources

  1. In the navigation pane, choose Stacks.

  2. Select the stack and choose Actions, Disassociate Fleet.

  3. From Stack Details, open the Associated Fleet link to select the fleet.

  4. Choose Actions, Stop. It takes about 5 minutes to stop a fleet.

  5. When the status of the fleet is Stopped, choose Actions, Delete.

  6. In the navigation pane, choose Stacks.

  7. Select the stack and choose Actions, Delete.