Business continuity - Amazon WorkSpaces Thin Client

Business continuity

WorkSpaces Thin Client provides support for Business continuity as part of a Business Continuity Plan (BCP). WorkSpaces Thin Client business continuity is available for use with WorkSpaces Personal only. For more information on business continuity, see Business continuity for WorkSpaces Personal in the Amazon WorkSpaces Administration guide.

Prerequisites

For business continuity to work on WorkSpaces Thin Client, the following prerequisites must be met:

Configuring business continuity for WorkSpaces Thin Client

To enable WorkSpaces Personal DR on Amazon WorkSpaces Thin Client, you will need to configure connection aliases to map to the environment using the SDK.

Sample doc explanation for setting up disaster recovery:

An example command using the AWS CLI to create a new environment using a WorkSpaces connection alias for the streaming desktop:

aws workspaces-thin-client create-environment --region region --desktop-arn/ arn:aws:workspaces:region:account:connectionalias/wsca-id

Replace wsca-id with your WorkSpaces Personal connection alias. The ID of the WorkSpaces connection alias can be found in the WorkSpaces Management Console or from the SDK.

End user experience

Once business continuity is configured, devices must be registered and active within the last 15 days. After that, should WorkSpaces Thin Client management services become unavailable, users then can stay connected to their sessions for up to 24 hours . In this condition, the device will not receive software updates, exchange posture information, and cannot be activated. The corresponding device entry in WorkSpaces Thin Client console will not show the latest information.

If the WorkSpaces Thin Client device management services remain unavailable beyond 24 hours, the following error message will display:

"An error has occurred. Please try again. If the issue persists, contact your IT administrator. (Error Code: 3006)."