- Newest
- Most votes
- Most comments
I understand this is a frustrating situation. Unfortunately, when you rebuild a WorkSpace, it recreates the root volume from the most recent image of the bundle the WorkSpace was created from, which means any applications installed or system settings changed after the WorkSpace was created are lost. The user volume is recreated from the most recent snapshot, which overwrites the current contents.
Based on the information available, if all your snapshots are labeled as unhealthy, this significantly limits recovery options. Snapshots are typically taken every 12 hours when a WorkSpace is healthy. However, if a WorkSpace is unhealthy, snapshots may only be created for the user volume, not the root volume.
If a WorkSpace becomes unhealthy before initial snapshots are taken, or before new snapshots can be taken after a restore, the WorkSpace cannot be restored through normal means. In such cases, your options are limited to:
- Attempting to rebuild the WorkSpace again (though this may yield the same result if snapshots are unhealthy)
- Contacting AWS Support for assistance, as they may have additional tools or options available to help recover your data
It's important to note that both restoring and rebuilding WorkSpaces are potentially destructive actions that can result in data loss, as data recovered from snapshots can be up to 12 hours old. For future prevention, ensure regular backups of critical data to locations outside the WorkSpace.
I recommend reaching out to AWS Support directly, as they may be able to investigate your specific situation more thoroughly.
Sources
AWSSupport-RecoverWorkSpace - AWS Systems Manager Automation runbook reference
Rebuild a WorkSpace in WorkSpaces Personal - Amazon WorkSpaces
Restore a WorkSpace in WorkSpaces Personal - Amazon WorkSpaces
answered 2 months ago
Relevant content
asked 4 years ago
