> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Switch Heavily Used WorkSpaces to AlwaysOn

> Switch AutoStop WorkSpaces that are used many hours a month to AlwaysOn monthly billing.

AutoStop WorkSpaces are billed a small monthly fee plus an hourly rate, which suits part-time users. Past a break-even number of hours, the flat AlwaysOn monthly price is cheaper. nOps finds AutoStop WorkSpaces used above that break-even and estimates the saving from switching them to AlwaysOn.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | End-user computing |
| **Service** | Amazon WorkSpaces |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

AutoStop is often chosen for everyone, but full-time users then pay more than the AlwaysOn price every month.

## How nOps finds it

nOps reads the last 45 days of WorkSpaces billing. A WorkSpace on AutoStop is flagged when it has at least 14 days of history, was used in the last 4 days, and its hours in the last 7 days and in the last 28 days, each projected to a month, are both above the break-even: the AlwaysOn monthly price minus the AutoStop monthly fee, divided by the AutoStop hourly price. The saving is the AutoStop fee plus projected hours times the hourly price, minus the AlwaysOn price, at public list prices adjusted for your discount, and must be at least \$5 a month.

## Before you start

Permission to modify WorkSpaces (`workspaces:ModifyWorkspaceProperties`).

## How to implement

1. Confirm the user will keep working this many hours.
2. Change the running mode (WorkSpaces console: select the WorkSpace, **Actions → Modify running mode properties → AlwaysOn**, or `aws workspaces modify-workspace-properties --workspace-id WORKSPACE_ID --workspace-properties RunningMode=ALWAYS_ON`).
3. Review usage each month and switch back to AutoStop if it drops.

## Risks and considerations

* If the user's hours drop, AlwaysOn can cost more than AutoStop. Review monthly.
* Billing for a running mode change applies in the month it is made; check how your month is charged.
* To roll back, change the running mode back to AutoStop.

## FAQs

> [accordion] Does the user notice the change?
>
> No disconnection is needed. With AlwaysOn the WorkSpace no longer stops after idle time, so it is ready immediately.

## Related

* [Schedule Non-Production EC2 Instances](https://help.nops.io/inform/supported-recommendations/schedule-non-production-ec2-instances)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.