AWS Blu Insights Issue - Workspace in Codebase is not responding

To troubleshoot the issue with the unresponsive workspace in AWS Blu Insights Codebase, you can try the following steps:

Verify that the IAM role you are using to access Blu Insights has the necessary permissions. 

If the workspace was created from a public Windows 7 bundle, you may need to migrate it to a Windows 10 bundle, as Windows 7 workspaces can no longer be rebuilt after January 14, 2020. Refer to the AWS Documentation for the migration process.

Check if the computer name of the workspace has been changed. If so, change it back to the original name:
    Open the Amazon WorkSpaces console and expand the unhealthy workspace to view the Computer Name.
    Connect to the workspace using RDP and open a command prompt.
    Run "hostname" to check the current computer name.
    If the names don't match, open system properties using "sysdm.cpl"
    and update the computer name to the one from the WorkSpaces console.

Ensure that the
SkyLightWorkspaceConfigService
is in the Running state. If not, start the service.

https://docs.aws.amazon.com/m2/latest/userguide/ba-bi-tabclose.html