AWS AppStream 2.0
Turbo supports deploying applications to Amazon AppStream 2.0. AppStream 2.0 provides cloud-based Windows desktops hosted in the AWS cloud.
AppStream 2.0 offers two deployment models: Always-On/On-Demand and Elastic fleets.
With Always-On and On-Demand fleets, one creates a golden image that includes the Turbo client configured as you would any other VDI environment. In this case, Turbo allows applications to be dynamically deployed without modifications to the base image.
With Elastic fleets, it is necessary to have a way to rapidly provision applications on the clean base image provided by AWS as well as run applications that may not originally be designed for portable use or for execution in the specific Windows environment provided by AWS. Turbo containers address all of these issues in a single, efficient solution.
Before starting the AppStream 2.0 setup, please note the following information:
- URL of the Turbo Hub Server
- API Key to access the Hub Server
The API key can be generated from the Turbo Server administration console under Hub / API Keys. Press Add Key and enter a key name such as
aws-appstream. Leave the Run as system option unselected.
It is strongly recommended that a dedicated API key be used for the AppStream 2.0 fleet.
For the best performance, it is recommended that the Hub Server run in the same AWS Availability Zone as the AppStream 2.0 fleet. This also minimizes costs associated with data transfer. If necessary, the AWS Hub instance can federate respositories from an external Turbo Hub such as an on-premises Hub.
AppStream 2.0 Setup
Turbo AppStream 2.0 setup consists of:
- Configuring an AppStream 2.0 Stack and Fleet
- Setting up the Turbo App Block
- Adding applications
Stack and Fleet Setup
Prior to configuring Turbo in AppStream, it is necessary to create an AppStream 2.0 Stack and Fleet. These provide the computate infrastructure that will run applications.
Instructions on configuration can be found in the AWS AppStream 2.0 documentation:
AppStream 2.0 includes the ability to use Elastic Fleets which are a very cost effective way to launch and stream Turbo applications to end users. Since elastic fleet VMs are provisioned from a ready-to-use pool of instances, provisioning is fast, yet customers are only charged for actual time used, exclusive of "standby" time.
An AppStream App Block provides shared setup for a set of AppStream applications. When using Turbo to deploy on AppStream, a single App Block is used to deploy the Turbo Client, which can then run any Turbo-packaged application.
For convenience, the Turbo Client is available in VHD form from the Turbo Downloads page:
A setup script is provided that handles mounting of the VHD and setup of the Turbo Client. The setup script is available in the Turbo GitHub repository:
The setup script accepts a single parameter indicating the Hub server to be used.
The Turbo Client VHD and setup script must be copied into an S3 bucket in the same zone as the AppStream 2.0 fleet. AppStream 2.0 must also have permissions to access the S3 bucket.
For more information on S3 bucket configuration, see the document:
The following App Block settings should be used:
|Setup script object||Select
|Setup script executable||
|Setup script executable arguments||
Once the App Block is configured, any Turbo application can be launched within the AppStream 2.0 interface.
Prior to adding the application, the application icon should be added to the connected S3 bucket.
The following Application settings should be used:
|Application icon object||Select
|Application executable launch path||
|Application launch parameters||
|App block||Select App Block created above|
Note that each application must be associated to a fleet before the application will be available.
To test applications, select the applicable AppStream 2.0 Stack and press Action / Create Streaming URL. This creates a one-time URL that will launch AppStream as the specified user.