How pricing works
With Amazon AppStream 2.0, you pay only for the streaming resources that you use plus a small monthly fee per streaming user. There is no upfront investment and no long-term commitment when using Amazon AppStream 2.0.
Streaming resources consist of AppStream 2.0 Always-On fleet instances, On-Demand fleet instances, and image builder instances. Fleet instances and image builder instances are billed per hour, and the price per hour is based on the instance type and size you select. The instance charge includes compute, storage, and any network traffic used by the streaming protocol. User fees are charged per user per month in each AWS Region where users stream applications from AppStream 2.0 fleet instances.
Always-On fleet instances
Always-on fleet instances are charged hourly. The instance charge includes compute, storage, and any network traffic used by the streaming protocol. With Always-On fleets, all instances that are running are charged the applicable running instance fee, based on the instance type and size, even when users aren't connected.
On-Demand fleet instances
On-Demand fleet instances are charged hourly. The instance charge includes compute, storage, and any network traffic used by the streaming protocol. With On-Demand fleets, instances are charged the applicable running instance fee, based on the instance type and size, only when the instances are used for streaming sessions. Instances in On-Demand fleets that are not being used for streaming sessions are charged a small hourly stopped instance 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 any network traffic used by the streaming protocol. All image builder instances that are running are charged the applicable running instance fee, based on the instance type and size, even when no administrators are connected.
Schools, universities, and certain public institutions may qualify for a reduced Microsoft RDS SAL user fee of $0.44 per user per month. Please refer to the Microsoft Licensing Terms and Documents for qualification requirements. If you think you qualify, please contact us.
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 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.
Using the US East (N. Virginia) Region, you launch a stream.standard.medium image builder to install applications and create an image, from which you provision an On-Demand fleet consisting of two stream.standard.medium fleet instances. During the month, one of your users launches streaming sessions from your On-Demand fleet using both the SAML 2.0 and Streaming URL authentication types. And, during the same month, another user launches streaming sessions from the On-Demand fleet using SAML 2.0. 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. AppStream 2.0 also charges a user fee of $4.19 for each authorized user that launches a streaming session from an AppStream 2.0 fleet during the month. User fees are not incurred for administrators connecting to and using image builders to create images.
Assuming your image builder instance runs for four hours, your two On-Demand streaming instances each run for five 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 $22.72 ($10.15 in instance fees plus three user fees of $4.19 each).
Pricing by AWS Region – Always-On, On-Demand, and image builder instances
* 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.