AppStream 2.0 Instance Families
Amazon AppStream 2.0 users stream applications from stacks that you create. Each stack
is associated with a fleet. When you create a fleet, the instance type that you specify
determines the hardware of the host computers used for your fleet. Each instance type offers
different compute, memory, and GPU capabilities. Instance types are grouped into instance
families based on these capabilities. For hardware specifications and pricing information, see AppStream 2.0 Pricing
When you create a fleet or image builder, you must select an image that is compatible with the instance family on which you intend to run your fleet.
-
When launching a new image builder, you are presented with a list of the images in your image registry. Select the appropriate base image.
-
When launching a fleet, ensure that the private image you select was created from the appropriate base image.
The following table summarizes the available instance families and provides the base image naming format for each. Select an instance type from an instance family based on the requirements of the applications that you plan to stream on your fleet, and match the base image according to the following table.
Note
If your use case involves real-time audio-video (AV) or other scenarios that require high frame rates and your display performance isn't as expected, consider scaling up to a larger instance size.
Graphics Pro instances will no longer be available from AWS after 10/31/2025 due to End of Life of hardware supporting Graphics Pro instance types.
Instance Family | Description | Base Image Name |
---|---|---|
General Purpose | Basic computing resources for running web browsers and most business applications. | AppStream-WinServer- AppStream-AmazonLinux2- AppStream-RHEL8-07-30-2024 |
Compute Optimized | Optimized for compute-bound applications that benefit from high performance processors. | AppStream-WinServer- AppStream-AmazonLinux2- AppStream-RHEL8-07-30-2024 |
Memory Optimized | Optimized for memory-intensive applications that process large amounts of data. NoteIf you plan to use AppStream 2.0 z1d-based instances, you must provision them from images that were created from AppStream 2.0 base images published on or after June 12, 2018. |
AppStream-WinServer- AppStream-AmazonLinux2- AppStream-RHEL8-07-30-2024 |
Graphics Pro | Uses NVIDIA Tesla M60 GPUs and provide a high-performance, workstation-like experience for graphics applications that use DirectX, OpenGL, OpenCL, or CUDA. | AppStream-Graphics-Pro-OperatingSystemVersion -MM-DD-YYYY |
Graphics Design | Uses AMD FirePro S7150x2 Server GPUs and AMD Multiuser GPU technology to support graphics applications that use DirectX, OpenGL, or OpenCL. |
AppStream-Graphics-Design-OperatingSystemVersion -MM-DD-YYYY
|
Graphics G4dn | Uses NVIDIA T4 GPUs to support graphics intensive applications. |
AppStream-Graphics-G4dn-OperatingSystemVersion -MM-DD-YYYY AppStream-Graphics-G4dn-RHEL8-07-30-2024 |
Graphics G5 | Uses NVIDIA A10G GPUs to support graphics-intensive applications such as remote workstations, video rendering, and gaming, to produce high fidelity graphics in real time. | AppStream-Graphics-G5-OperatingSystemVersion -07-17-2023
AppStream-Graphics-G5-RHEL8-07-30-2024 |
AppStream 2.0 instances have one 200 GB fixed-size volume, which is used for the C drive. Because AppStream 2.0 is non-persistent, each instance's volume is immediately deleted after each user session.
For more information, see the following: