Enabling Nested Virtualization on Amazon WorkSpaces: GUI, CLI, and PowerShell
Nested virtualization lets you run virtual machines inside an Amazon WorkSpaces Personal which is useful for developers who need local Docker/Hyper-V based workloads, Windows Sandbox, or Android emulators directly on their virtual desktop.
Before you start:
Nested virtualization is supported only on specific bundles and operating systems. Review these before enabling at scale.
Supported
- Personal WorkSpaces on Power and higher bundles [4+ vCPU recommended]
- Windows Server 2019/2022/2025 and Windows 11 [see AutoStop note below]
Known limitations
- AutoStop running mode — WorkSpaces using AutoStop with nested virtualization on Windows Server 2025 or Windows 11 24H2/25H2 perform a full reboot instead of hibernating on timeout. This means longer resume times and loss of the user's unsaved work. Recommended to use AlwaysOn running mode if you need fast resume and session persistence.
- GPU-based bundles — Not supported on GPU WorkSpaces (Graphics/GraphicsPro).
- Unsupported operating systems — Not supported on Windows Server 2016, Windows 10, or Amazon Linux 2.
- Standby WorkSpaces — Not supported.
Option 1: AWS Management Console (GUI)
The console supports nested virtualization in two places: as a checkbox during launch (for new WorkSpaces) and as a setting you modify (for existing WorkSpaces). Both are covered below.
1a. Enable during launch (new WorkSpaces)
Just like the encryption checkbox, nested virtualization can be turned on at creation time — so the WorkSpace comes up with it already enabled, with no follow-up restart.
- Sign in to the AWS Management Console, open the Amazon WorkSpaces console, and choose Create WorkSpaces.
- Select your directory, then choose or search for the users to create WorkSpaces for.
- Choose an eligible bundle — a Power or higher (4+ vCPU) bundle on a supported OS. (Nested virtualization is not offered for GPU bundles or unsupported operating systems; see the limitations section above.)
- In the WorkSpace Customization step — the same screen where you set the volume encryption, and volume sizes — locate the Nested virtualization option and select the checkbox to enable it.

- Review the note about performance/restart behavior, complete the remaining configuration, and choose Create WorkSpaces.

- When the WorkSpaces finish provisioning and reach AVAILABLE, nested virtualization is already active — no separate modify/restart step required.Tip: Enabling at launch is the cleanest path for new fleets — the setting is applied during provisioning, so users never experience a follow-up restart.
1b. Enable on an existing WorkSpace
For WorkSpaces that already exist, enable nested virtualization by modifying the WorkSpace properties.
- In the Amazon WorkSpaces console, choose WorkSpaces in the left navigation, then select the target WorkSpace from the list.
- Choose Actions → Select Enable Nested Virtualization
- Review the warning about the required restart, then choose Save. The WorkSpace will restart to apply the change.>

- Once the WorkSpace returns to AVAILABLE, nested virtualization is active.
Note: The WorkSpace must be in AVAILABLE or STOPPED state to modify this property, and enabling it triggers a restart.
Best for: one-off changes, small numbers of WorkSpaces, or first-time validation. Use 1a for brand-new WorkSpaces and 1b for ones already running.
Option 2: AWS CLI
The CLI is ideal for scripting and repeatable changes. The operation is
modify-workspace-properties .Enable nested virtualization
aws workspaces modify-workspace-properties \ --workspace-id ws-xxxxxxxxx \ --workspace-properties NestedVirtualizationEnabled=true \ --region us-east-1Disable nested virtualization
aws workspaces modify-workspace-properties \ --workspace-id ws-xxxxxxxxx \ --workspace-properties NestedVirtualizationEnabled=false \ --region us-east-1Verify the current setting
aws workspaces describe-workspaces \ --workspace-ids ws-xxxxxxxxx \ --region us-east-1 \ --query "Workspaces[0].WorkspaceProperties"Example output:
{ "RunningMode": "AUTO_STOP", "RunningModeAutoStopTimeoutInMinutes": 60, "RootVolumeSizeGib": 80, "UserVolumeSizeGib": 50, "ComputeTypeName": "POWER", "NestedVirtualizationEnabled": true}Tip: If your CLI reportsUnknown parameter in WorkspaceProperties: "NestedVirtualizationEnabled", your AWS CLI is older than the release that introduced this property. Update to the latest AWS CLI v2.
Best for: scripting, CI/CD pipelines, and cross-platform automation.
Option 3: AWS Tools for PowerShell
For Windows-centric administrators, AWS Tools for PowerShell exposes the same operation through the
Edit-WKSWorkspaceProperty cmdlet.Install / import the module (one-time)
Install-Module -Name AWS.Tools.WorkSpaces -Scope CurrentUserImport-Module AWS.Tools.WorkSpacesEnable nested virtualization
# Build the WorkspaceProperties object with the nested virtualization flag$props = New-Object Amazon.WorkSpaces.Model.WorkspaceProperties$props.NestedVirtualizationEnabled = $true
Edit-WKSWorkspaceProperty ` -WorkspaceId "ws-xxxxxxxxx" ` -WorkspaceProperties $props ` -Region us-east-1Disable nested virtualization
$props = New-Object Amazon.WorkSpaces.Model.WorkspaceProperties$props.NestedVirtualizationEnabled = $false
Edit-WKSWorkspaceProperty ` -WorkspaceId "ws-xxxxxxxxx" ` -WorkspaceProperties $props ` -Region us-east-1Verify
(Get-WKSWorkspace -WorkspaceId "ws-xxxxxxxxx" -Region us-east-1).WorkspacePropertiesBest for: Windows admins already using AWS Tools for PowerShell, or integrating with existing PowerShell-based operational tooling.
Choosing the right method
Method | Best for | Scales to many WorkSpaces? |
|---|---|---|
Console (GUI) | One-off changes, validation | No — manual per WorkSpace |
AWS CLI | Scripting, pipelines, cross-platform | Yes — with a loop/script |
PowerShell | Windows admins, existing PS tooling | Yes — with a loop/script |
For bulk enablement across hundreds or thousands of WorkSpaces, none of the above scale comfortably on their own. In the next post, we build a fully automated, event-driven solution using AWS Lambda and Amazon S3 — upload a file of WorkSpace IDs and let the automation do the rest.
👉 Next: Automating Nested Virtualization at Scale with AWS Lambda and S3
Summary
- Nested virtualization is toggled via the
NestedVirtualizationEnabledWorkSpace property.
- You can enable it at launch (no restart needed) or post-launch via modify (triggers a restart).
- The WorkSpace must be AVAILABLE or STOPPED to modify the property.
- The Console is best for one-offs; the CLI and PowerShell are best for scripting.
- Always check the AutoStop / OS limitations before enabling — especially the AutoStop hibernation behavior on Windows Server 2025 and Windows 11 24H2/25H2.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article