Amazon AppStream
Developer Guide

This documentation is for an older version of Amazon AppStream. For information about the latest version, see the Amazon AppStream 2.0 Developer Guide.

Amazon AppStream Application Lifecycle

When you deploy and manage your application on Amazon AppStream it goes through a series of states. For more information, see Deploying Your Streaming Application to Amazon AppStream and Managing Your Streaming Application.


During the Building state, Amazon AppStream deploys your application. This has several substates, which are displayed in the console.

  • Preparing environment – Amazon AppStream allocates the IT infrastructure required to host your application.

  • Copying application – Amazon AppStream copies the installer for your application from Amazon S3 to the host. A presigned URL that you provide gives the installer access to the content stored in your AWS account. The installer installs your application and its dependency files.

  • Installing application – Amazon AppStream calls the installer, including any command-line parameters you provided, to install your application on the host.

  • Creating AMI – Amazon AppStream creates an Amazon Machine Image (AMI) of the host with your application installed. For more information, see Amazon Machine Images (AMI) in the Amazon Elastic Compute Cloud User Guide.


During the Active state, your application is ready to accept user connections.


The Archiving state begins after you archive your application but before it is fully archived. In this state, the application continues to stream to existing client connections, but no longer accepts new client connections. When all client connections have concluded, Amazon AppStream moves the application into the Archived state.


Once it is fully archived, your application no longer accepts client connections. This state corresponds to Archived in the console.


A problem during deployment puts your application into the Error state.