# Inactive WorkSpaces Applications Image Builder or App Block Builder instances Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/inactive-appstream-image-builder-or-app-block-builder-instances When Amazon WorkSpaces Applications (formerly AppStream 2.0) builder instances are left running but unused, they continue to generate compute charges... By: Jason DiDomenico Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Inactive WorkSpaces Applications Image Builder or App Block Builder Instances The short version When Amazon WorkSpaces Applications (formerly AppStream 2.0) builder instances are left running but unused, they continue to generate compute charges without delivering any value. [Jason DiDomenico](https://www.linkedin.com/in/jasondidomenico/) Director of FinOps @ Discover Financial Services AWS service [Amazon WorkSpaces Applications](https://www.pointfive.co/efficiency-hub/cloud-services/aws-appstream-2-0) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0175 Type Idle or Unused Resource ## 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. - [Image Builders - Amazon WorkSpaces Applications docs.aws.amazon.com](https://docs.aws.amazon.com/appstream2/latest/developerguide/managing-image-builders.html) - [Application streaming pricing - Amazon WorkSpaces Applications aws.amazon.com](https://aws.amazon.com/workspaces/applications/pricing/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Amazon WorkSpaces Applications CER-0180 ### [Suboptimal WorkSpaces Applications Fleet Auto Scaling Policies](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-appstream-fleet-auto-scaling-policies) When fleet auto scaling policies maintain more active instances than are required to support current usage - particularly during off-peak hours-organizations incur unnecessary compute costs. Fleets often remain oversized due to... Compute - Amazon WorkSpaces Applications CER-0050 ### [Underutilized or Overprovisioned WorkSpaces Applications Instances](https://www.pointfive.co/efficiency-hub/inefficiencies/underutilized-or-overprovisioned-appstream-instances) Amazon WorkSpaces Applications (formerly AppStream 2.0) fleets often default to instance types designed for worst-case or peak usage scenarios, even when average workloads are significantly lighter. This leads to consistently low... Compute - AWS EKS CER-0298 ### [Stale Completed or Failed Fargate Pods Causing Direct Billing and Capacity Waste](https://www.pointfive.co/efficiency-hub/inefficiencies/stale-completed-or-failed-fargate-pods-causing-direct-billing-and-capacity-waste) Kubernetes Jobs or CronJobs running on EKS Fargate leave completed or failed pod objects in the cluster indefinitely. Although the workload execution has finished, AWS keeps the underlying Fargate microVM running to allow log inspection... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.