Amazon AppStream 2.0 Cost optimisation
There are various disparate documented locations that cover the different methods to apply cost savings within an Amazon AppStream 2.0 deployment.
- Changes to an on-demand vs always on circa 15-20% reduction
- Use standard medium instances reduction circa 40% reduction
- If you’re able to use Linux OS circa 30% reduction
- Always on
- On-demand
- Elastic
- Check each instance type that you plan to use, and the number of fleet instances that your VPC can support i.e. Quotas - is greater than the number of anticipated concurrent users for the same instance type.A
- Disconnect time out time – how long after a user disconnects will the session be terminated. If the fleet is set to on-demand then renewing a session after this time out limit will result in 1-2 min delays. Conversely leaving it too long will result in unnecessary cost.
- Disconnect idle time – how long can the session be idle before the session is closed. Example there is an idle time of 15mins and a timeout of 15 mins then that is 30 mins the session has been in a running state being charged.
- Setting minimum and maximum capacities for which the policy will operate and the % tolerances based on the values of cloud watch metrics CapacityUtilization, AvailableCapacity, InsufficientCapacityError
- You can have multiple scaleout /scale in policies
Any opinions in this post are those of the individual author and may not reflect the opinions of AWS.