Streamline Your Application Delivery with AWS AppStream 2.0: An Introduction

What is AWS AppStream 2.0?

AWS AppStream is a fully managed, secure application streaming service that allows you to stream desktop applications from the cloud to any device running a web browser, without rewriting them. This means that you can run your desktop applications on a variety of devices, including laptops, tablets, and even smartphones, without having to install them.

Use Cases

Appstream is a versatile service that can be used for a variety of use cases. Here is a list of some of the most common use cases for AWS Appstream:

1. Remote Workforce
2. Bring Your Own Device (BYOD)
3. High Performance Computing (HPC)
4. Graphics-Intensive Applications
5. Software Demos and Trials

Basic Components needed for an end to end Deployment

In order to stream your applications on Appstream, you need to use the following components of appstream:

• Image Builder
• Stack and Fleets

AWS AppStream Image Builder

AWS AppStream Image Builder is a fully managed service that makes it easy to create and maintain custom image versions of your applications. With AppStream Image Builder, you can create custom images that include your applications, custom settings, and any required dependencies.

AppStream Image Builder can help you automate the process of building and updating custom images, which can save time and effort compared to manually building and maintaining images. It helps ensure that the images are working correctly before you deploy them.

You can create an image builder using AWS CLI, console, or the AWS SDK. While calling the CreateImageBuilder API you need to provide the following:

• Subnet ID
• Security Group
• Base Image

Subnet ID, and Security Group are for configuring the network of the image builder, and the base image is actually the operating system you want to use to build your application. AWS Appstream provides a wide variety of base images that you can use to build your applications.

Inside these base images AWS has all the necessary components pre-installed so that you only need to focus on adding the relevant components for your application to function. Monitoring, and patching services like SSM, and Cloudwatch already have their agents installed in the image builder instance. Furthermore, there is an Image-Assistant CLI present in the image builder that helps you build an image by walking you through guided instructions.

Stack and Fleets

Overview

AWS AppStream Stacks and Fleets allow you to stream desktop applications from the cloud to any device running a web browser, without rewriting them.

An AppStream Stack is a collection of resources that are required to run a specific application or set of applications. This can include the applications themselves, as well as any required dependencies, custom settings, and user data.

An AppStream Fleet is a group of streaming instances that are used to run and scale your applications. You can create multiple fleets in a single stack, and each fleet can be configured with different instance types, capacity settings, and other parameters to meet the needs of your applications.

Using AppStream Stacks and Fleets, you can easily scale your application usage up or down based on demand, and you can also customize the environment in which your applications are run to meet your specific needs. This can be particularly useful for businesses that experience spikes in usage at certain times of the year, as it allows them to quickly and easily accommodate the increase in demand without having to invest in additional hardware or infrastructure.

Fleet Types

There are 3 types of Fleet in AWS Appstream:

• AlwaysOn
• OnDemand
• Elastic

The main difference between the fleet types is how the streaming instances are run, and managed. In AlwaysOn, the streaming session remains on regardless of the demand, whereas in OnDemand fleets are launched when the user starts streaming, and they are shut down when the streaming session ends. Elastic fleets are the ones that are managed by AWS, and you don’t need auto scaling policies to address changes in demand. However, you need to configure the maximum concurrency you expect when creating and updating the fleet, and ensure that you have sufficient streaming instance limits to meet your user demand.

Step By Step Process of using Appstream

1. Navigate to the Appstream console, and click on images from the menu on your left.

2. Select image builders, and click on launch an image builder.

3. In the image builder console, you need to select the OS on which you want to install your application, and package it as an image. In this example I am using a general purpose Windows server image: AppStream-WinServer2019-03-29-2023 (Public). Give the image builder an appropriate name, and for this example I am selecting a standard general purpose instance. While configuring the networking side select the VPC, and subnet IDs along with the security group. Now you have added all the relevant parameters, and it is time to launch the image builder.

4. Connect to the demo-builder, and install any application that you want to install on that builder. In my case I am installing Google Chrome from firefox, and I will package that in my image.

5. After installing your applications you need to open the Appstream Image Assistant, and then add the applications you want your users to stream.

When you select an application then you need to set application launch settings if you have any, otherwise you can leave it to default.

6. After adding the application you need to configure it, and for that you can follow the instructions given in this image

My use case is very simple so I don’t need to perform the above operations, and I can simply go to the next stage.

7. In the next stage you can test your applications to make sure they work as expected. Our use case does not require any testing so I will proceed to the next stage.

8. After the test stage you need to go to the optimize stage where you can optimize your apps to reduce their launch time. You need to simply press the Launch icon, and the image assistant will optimize the application for you.

9. After optimization you need to configure your image that is adding a name, description, and tags etc to your image.

10. Finally you need to click “Disconnect” and Create Image icon.

11. Navigate to the image-registry, and search for your image. You can use it as soon as it enters the Available state.

12. Now go to the fleet console, and create a fleet. For this example, I have created a general purpose, always-on fleet with default settings that will run the image that we have just created.

13. It takes about 10 minutes for the fleet to enter the Running state. During this time you can navigate to the stack console, and create a stack. For this example, I have created a stack using default settings.

14.  When the fleet enters the Running state you need to go to the stacks console, and associate your fleet to the stack that you have created.

15. Now you need to create a user in the user pool console, and assign that user to the stack that you have created. You will receive an email with login details, and a url to access Appstream’s streaming session.

16. Finally this is what a streaming session looks like