Purpose:
This guide outlines the recommended steps to resolve when an AWS WorkSpace becomes unresponsive for a user.
—————
Step 1: Check WorkSpaces Status in AWS Console
1. Log in to AWS Console.
2. Navigate to WorkSpaces → WorkSpaces.
3. Locate the affected user and check the current status:
– If the WorkSpace is stopped, start it.
– If the WorkSpace shows running but the user cannot connect, continue to the next step.
Step 2: Reboot the WorkSpace (Recommended first action)
1. Select the WorkSpace.
2. Click Actions → Reboot WorkSpace.
Rebooting is similar to restarting a physical computer. This does not affect user data.
Step 3: Stop and Start the WorkSpace
This refreshes the network interfaces and services.
1. Select the WorkSpace.
2. Click Actions → Stop WorkSpace.
3. Once fully stopped, choose Actions → Start WorkSpace.
Step 4: Rebuild the WorkSpace
Rebuild recreates the OS using the original bundle image while preserving user data stored in: - The D drive - The user profile
Installed apps may need to be reinstalled after a rebuild.
Steps: 1. Select the WorkSpace. 2. Click Actions → Rebuild WorkSpace.
Step 5: Restore (If enabled)
Restores to the latest snapshot of the WorkSpace image. Faster than a rebuild depending on configuration.
Steps: 1. Select the WorkSpace. 2. Click Actions → Restore WorkSpace.
Step 6: Recreate the WorkSpace (Last resort)
Only perform this step if all other options fail.
1. Back up any data if possible.
2. Delete and re-provision the WorkSpace.
Optional: User Side Troubleshooting
Have the user try: - Restarting their local device. - Switching between WSP and PCoIP protocols in the WorkSpaces client. - Ensuring no firewall is blocking required WorkSpaces ports (4172 for PCoIP or 4195 for WSP).
Quick Action Summary
1. Reboot
2. Stop and Start
3. Rebuild
4. Restore
5. Recreate