Explanation
Why the waste happens and who it affects.
These instances are commonly left active after configuration or image creation is completed but can be safely stopped or terminated when not in use. Identifying and decommissioning inactive builders helps reduce unnecessary compute costs.
Billing model
The pricing dimensions that drive this cost.
WorkSpaces Applications Image Builder and App Block Builder instances are billed while running, regardless of whether they are actively in use: Windows image builders are charged hourly, while Rocky Linux and Red Hat Enterprise Linux image builders and app block builders are charged in one-second increments with a 15-minute minimum. Charges accrue continuously while the instance is in the running state, even if no users are connected or no configuration is taking place.
How to detect
4 checks to find it in your estate.
- Identify WorkSpaces Applications Image Builder or App Block Builder instances that have remained in a running state without recent user connections or image-related activity
- Review historical usage patterns to determine if the instance was left on after setup or testing
- Check for absence of scheduled image builds, configuration updates, or automation tied to the builder
- Validate with application administrators whether the builder instance is still needed
How to fix
3 ways to remove the waste.
- Stop or decommission builder instances that are no longer required.
- Implement an automated workflow - such as a scheduled Lambda function - that stops builder instances after a defined period of inactivity.
- Establish operational guidelines to ensure builder instances are shut down after image creation or testing tasks are completed.
Documentation
Vendor references for pricing and configuration.