(2026.06 and earlier) VDIs stuck in STOPPING state after auto stop is triggered

[Murielxun]

Bug description

Virtual Desktops can get stuck in STOPPING state when idle timeout is reached for auto stop.

Affected versions

• 2026.06 and earlier

Mitigation

Tip: We recommend running the following commands in AWS CloudShell in the same account and region where RES is deployed. CloudShell comes with pre-installed dependencies and helps eliminates other local environment conditions that may affect the patching process.

1. Update the memory for <environment-name>-vdc-vdi-helper-lambda lambda function from 128 MB to 512 MB by replacing the <environment-name> with the name of your RES environment in the comment below:
   a. The mitigation requires AWS CLI v2
   b. Configure the AWS CLI for the account / region where RES is deployed.

aws lambda update-function-configuration \ 
    --function-name <environment-name>-vdc-vdi-helper-lambda \ 
    --memory-size 512 

2. Verify that the memory size has been increased to 512 MB for <environment-name>-vdc-vdi-helper-lambda lambda function.