# Inactive AWS WorkSpace | Cloud Efficiency Hub Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/inactive-aws-workspace If an AWS WorkSpace has been provisioned but not accessed in a meaningful timeframe, it may represent waste - particularly if it is set to monthly billing. By: Taylor Houck Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version If an AWS WorkSpace has been provisioned but not accessed in a meaningful timeframe, it may represent waste - particularly if it is set to monthly billing. [Taylor Houck](https://www.linkedin.com/in/twhouck/) Cloud FinOps Specialist @ PointFive AWS service [AWS WorkSpaces](https://www.pointfive.co/efficiency-hub/cloud-services/aws-workspaces) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0033 Type Idle or Unused Resource ## Explanation Why the waste happens and who it affects. Many organizations leave WorkSpaces active for users who no longer need them or have shifted roles, leading to persistent charges without corresponding business value. Even in hourly mode, costs can accrue if WorkSpaces are left in a running state. ## Billing model The pricing dimensions that drive this cost. Amazon WorkSpaces supports two primary billing options: monthly (AlwaysOn) and hourly (AutoStop). In monthly mode, you are billed a flat rate regardless of usage. In hourly mode, you pay a fixed monthly infrastructure fee plus an hourly rate while the WorkSpace is running; the fixed fee continues even when the WorkSpace is stopped and is removed only by deleting the WorkSpace. Inactive WorkSpaces therefore result in unnecessary recurring charges in either mode; switching to AutoStop only helps for users with intermittent usage. ## How to detect 5 checks to find it in your estate. - Review the last login date for all provisioned WorkSpaces to identify users with prolonged inactivity - Confirm whether inactive WorkSpaces are set to monthly billing (always-on) or hourly (auto-stop) - Evaluate if inactive WorkSpaces are associated with users who have left the organization or changed roles - Check whether a WorkSpace remains in a running state even in hourly mode, causing unnecessary hourly charges - Review tagging metadata or directory assignments to determine if the WorkSpace is part of a temporary, staging, or unused environment ## How to fix 4 ways to remove the waste. - Decommission WorkSpaces that are no longer needed - Switch billing mode from monthly to auto-stop for WorkSpaces with intermittent usage - Automate reviews of WorkSpaces based on last login data to flag stale resources for cleanup or conversion - Use lifecycle management policies to standardize default billing modes and enforce deactivation schedules ## Documentation Vendor references for pricing and configuration. - [Amazon WorkSpaces Pricing aws.amazon.com](https://aws.amazon.com/workspaces/pricing/) - [Manage the running mode in WorkSpaces Personal docs.aws.amazon.com](https://docs.aws.amazon.com/workspaces/latest/adminguide/running-mode.html) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS WorkSpaces CER-0356 ### [WorkSpaces Running Mode Mismatched to Usage Hours](https://www.pointfive.co/efficiency-hub/inefficiencies/workspaces-running-mode-mismatched-to-usage-hours) WorkSpaces Personal offers two running modes with different billing: AlwaysOn, a fixed monthly fee for unlimited use, and AutoStop, which bills by the hour while the WorkSpace runs on top of a fixed monthly infrastructure fee. Which one is... 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 - AWS EKS CER-0120 ### [Orphaned and Overprovisioned Resources in EKS Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-and-overprovisioned-resources-in-eks-clusters) In EKS environments, cluster sprawl can occur when workloads are removed but underlying resources remain. Common issues include persistent volumes no longer mounted by pods, services still backed by ELBs despite being unused, and... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.