Amazon WorkSpaces Personal enhances protocol migration with rollback
Amazon WorkSpaces Personal now supports automated rollback and migration of stopped WorkSpaces, simplifying large-scale protocol changes. Migrating to the Amazon DCV protocol offers broader OS support, enhanced security, and improved performance. These features are available in all supported AWS regions and require no manual intervention for rollback or starting stopped instances.
- →Support for migrating stopped WorkSpaces
- →Automated rollback for protocol migration failures
- →Benefits of migrating to Amazon DCV protocol
- →Availability of enhanced migration features
Features (1) ›
- Support for migrating stopped WorkSpaces
Administrators can now initiate protocol migration for WorkSpaces that are in a stopped state, removing the need to manually start each instance before modification.
Enhancements (1) ›
- Automated rollback for protocol migration failures
WorkSpaces Personal now automatically rolls back to a pre-migration snapshot if a protocol modification fails, ensuring a return to a known healthy state without manual intervention.
Notes (2) ›
- Benefits of migrating to Amazon DCV protocol
Migration to DCV provides broader OS support (Windows 11, Windows Server 2025), enhanced security features like certificate-based authentication and WebAuthN redirection, and improved streaming performance.
- Availability of enhanced migration features
These enhancements are available in all AWS commercial and AWS GovCloud (US) Regions where Amazon WorkSpaces Personal is supported.
https://aws.amazon.com/about-aws/whats-new/2026/07/amazon-workspaces-personal-pcoip/
Related releases
- Amazon Aurora DSQL adds multi-Region cluster support in four more Regions AWS What's New ·
- CloudWatch adds managed Prometheus collectors AWS What's New ·
- Amazon EC2 C7i Instances Expand to New Regions AWS What's New ·
- EC2 C7i-flex instances now available in Europe (Milan) region AWS What's New ·
- AWS CodeDeploy Expands to Five New Regions AWS What's New ·
- Redis 8.0 end-of-life date moved to 2026-12-01 endoflife.date ·