How pricing works
With Amazon AppStream 2.0, you pay only for the streaming resources that you use, and a small monthly fee per authorized user. There is no upfront investment and no long term commitment when using Amazon AppStream 2.0.
The streaming resources consist of AppStream 2.0 Always-On fleet instances and On-Demand fleet instances as well as image builder instances. Fleet instances and image builder instances are billed per hour, and the price per hour is based on the instance type you select. The instance charge includes compute, storage, and bandwidth that is consumed by the streaming protocol. User fees are charged per user per month in each AWS Region where they connect to AppStream 2.0 fleet instances and are not pro-rated. User fees are not incurred for administrators connecting to and using an Image Builder for creating images for their fleet.
Always-On fleet instances
Always-on fleet instances are charged hourly. The instance charge includes compute, storage, and bandwidth that is consumed by the streaming protocol. With Always-On fleets, all instances that are running are charged the running instance fees based on the instance type and size, even if no users are connected.
On-Demand fleet instances
On-Demand fleet instances are charged hourly. The instance charge includes compute, storage, and bandwidth that is consumed by the streaming protocol. With On-Demand fleets, instances that are being used for streaming are charged the running instance fees based on the instance type and size. Instances in an On-Demand fleet that are stopped and don’t have an active streaming connection are charged a small hourly fee that is the same for all instance types and sizes.
Image builder instances
Image builder instances are charged hourly. The image builder instance charge includes compute, storage, and bandwidth that is consumed by the streaming protocol. All image builder instances that are running are charged the running instance fees even if no administrators are connected.
Users fees are charged monthly. For each authorized end user in an AWS Region accessing applications on your fleet instances, you will be charged a Microsoft RDS SAL fee of $4.19 / user / month. Schools, universities, and public institutions may qualify for a reduced Microsoft RDS SAL user fee of $0.44 / user / month. Please reference the Microsoft Licensing Terms and Documents for qualification requirements. If you think you may qualify, please contact us. We will review your information and work with you to reduce your Microsoft RDS SAL fee. This fee is charged in full and is not pro-rated, regardless of when a user first accesses your applications in that month. This fee is not applicable when using Image Builder.
If you have Microsoft License Mobility, you may be eligible to bring your own Microsoft RDS CAL licenses and use them with Amazon AppStream 2.0. For users covered by your own licenses, you won’t incur the monthly user fees. For more information about using your existing Microsoft RDS CAL licenses with Amazon AppStream 2.0, please visit this page, or consult with your Microsoft representative.
If you use the image builder for a general purpose instance (stream.standard.medium), provision two On-Demand fleet instances using a general purpose instance (stream.standard.medium), and add two users:
In the US East (N. Virginia) Region, the hourly price for stream.standard.medium is $0.10 per hour. The stopped instance fee is $0.025 per hour. You will also be charged a user fee of $4.19 for each authorized user that can connect to your AppStream 2.0 fleet instance. User fees are not incurred for administrators connecting to and using an image builder for creating images for their fleet.
Assuming your image builder instance runs for 4 hours, you add 2 users, your 2 On-Demand streaming instances each run for 5 hours a day over one business week (50 hours), and your instances are stopped for the rest of the business week (190 hours), your total cost will be about $19.
* Hourly pricing fee charged for running instances only. For Image Builder and Always-On fleets, instances may be considered running if they are available for use, even if no user is connected. For On-Demand fleets, instances are considered running only if users are connected with an active streaming session.