Menu
Amazon AppStream 2.0
Developer Guide

Set up AppStream 2.0 Stacks and Fleets

To stream your applications, Amazon AppStream 2.0 requires an environment consisting of a stack, an associated fleet and at least one application image. This topic walks through the steps to set up a stack and a fleet, and how to give users access to the stack. If you haven't already done so, we recommend that you go through the procedures in Getting Started with Amazon AppStream 2.0 before using this topic.

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

Set up a Fleet

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

To set up and create a fleet

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

  2. You may see the welcome screen showing two choices: Try it now and Get started. Choose Get started, Skip.

    If you do not see a welcome screen, move on to the next step.

  3. In the left navigation pane, choose Fleets.

  4. Choose Create Fleet and for Step 1: Provide Fleet Details, provide a fleet name, optional display name, and optional description. Choose Next.

  5. For Step 2: Choose an Image, select an image and choose Next. Be sure to select an image that aligns with the instance family you need. For more information, see AppStream 2.0 Instance Families. If you don't have an image to use, see Tutorial: Using an AppStream 2.0 Image Builder.

  6. For Step 3: Configure Fleet, provide details for your fleet by providing inputs for the following fields:

    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. For more information, see AppStream 2.0 Instance Families.

    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 session instance they were disconnected from. 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 expected number of connected users at any one time. 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 expected number of connected users at any one time. 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 Review. You can change these values after fleet creation. For more information, see Fleet Auto Scaling for Amazon AppStream 2.0.

  7. For Step 4: Configure Network, select a VPC and 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. You can choose existing network settings or create new settings for this fleet.

    For internet access on the fleet using your default VPC or with a VPC with a public subnet, choose Default Internet Access.

    For VPC, select your default VPC or VPC with a public subnet. For Subnet, select one or two public subnets. If you are controlling internet access using a NAT gateway, leave Default Internet Access unselected and use the VPC with the NAT gateway. For more information, see Network Settings for Fleet and Image Builder Instances.

    For Security group(s), select up to five security groups to associate with this fleet. If needed, choose Create new security group. If you do not choose a security group, the fleet is associated with the default security group for your VPC. For more information, see VPC Security Groups.

    For Active Directory Domain (Optional), expand this section to choose the Active Directory and organizational unit in which to place your streaming instance computer objects. Ensure that the selected network access settings enables DNS resolvability and communication with your directory. For more information, see Using Active Directory Domains with AppStream 2.0.

  8. Review the details for the fleet, choose Edit for any section to change, and choose Create.

Upon completion of the previous steps, the initial status of your new fleet is listed as Starting in the Fleets dashboard. The fleet needs to be in Running status to be associated with a stack and used for streaming sessions. Over the next few minutes, the service sets up some resources and the fleet moves to Running status. Wait for the fleet to be in Running status before attempting to use it for streaming sessions.

Set up a Stack

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

To set up and create a stack

  1. On the left navigation pane, choose Stacks, Create Stack.

  2. Provide a stack name, optional display name and description. For Fleet, select the fleet to associate with your stack. Choose Next.

  3. To enable or disable persistent storage for the stack users, select or clear the Enable Home Folders check box For more information, see Persistent Storage with AppStream 2.0 Home Folders.

    Choose Review.

  4. Review the details for the stack, choose Edit for any section to change, and choose Create.

Upon completion of the previous steps, the status of your new stack is listed as Active in the Stacks dashboard. This signifies that the stack is available to work with from the console, but it cannot be used for streaming sessions until the associated fleet is in Running status.

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. For more information, see Using Active Directory Domains with AppStream 2.0.

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. For more information, see AppStream 2.0 Pricing.

To clean up your resources

  1. In the navigation pane, choose Stacks and select the active stack.

  2. Choose Actions, Disassociate Fleet.

  3. From Stack Details, open the Associated Fleet link.

  4. The associated fleet is automatically selected in the new window. Choose Actions, Stop. It usually takes about 5 minutes for a fleet to stop completely. Use the refresh button to update the status.

  5. When the fleet has a Stopped status, choose Actions, Delete.

  6. In the navigation pane, choose Stacks and select the active stack that you chose above.

  7. Choose Actions, Delete.

Next Steps

For more information, see the following topics: