CODEWITHSUNDEEP
windowsamazon-web-servicesvhdamazon-workspacesamazon-fsx
ADARSH K
ADARSH K

Reputation: 119

Sharing FSLogix Profiles Between AWS WorkSpaces Across Multiple Regions with Seamless User Experience

Hello Team,

We are running AWS WorkSpaces in two geographical regions (primary and secondary) and are facing challenges in providing a consistent user experience when users switch between regions. Below is a summary of the current situation and the challenges we are facing:

What We Are Trying to Achieve

Seamless Profile Sharing Across Regions: Users should have access to the same FSLogix profile (files, settings, etc.) whether they log into the primary or secondary WorkSpace. Any changes made in one region should be reflected in the other region.

Real-Time Profile Synchronization: Profile updates in one region should sync with the other region with minimal latency.

Automatic Session Management: If a user switches regions (e.g., logs into the secondary region while logged into the primary), the active session in the previous region should automatically log out to avoid profile locking.

Challenges We Are Facing

Profile Locking: FSLogix locks the VHD profile in the region where it is actively mounted. This prevents users from accessing the profile in the secondary region until they fully sign out of the primary session (closing the WorkSpaces client or disconnecting does not release the lock).

Session Persistence: Users are required to manually sign out from the primary WorkSpace before logging into the secondary WorkSpace, which is cumbersome and impractical.

What We’ve Tried

Cloud Cache (CCD): Configured FSLogix Cloud Cache with both FSx file shares (primary and secondary) as CCD locations. While this provides redundancy, it doesn’t resolve the profile locking issue.

Single VHD Location: Configured both regions to share a single FSx file share for profile storage. This also results in profile locking when users switch regions.

Manual Sign-Outs: Users manually sign out from one region before logging into the other. While this works, it is not user-friendly or efficient.

Help Needed

Profile Locking and Session Management: Is there a way to automatically log out users from the previous WorkSpace session when they log into a new region? Can FSLogix or AWS WorkSpaces be configured to release profile locks when the WorkSpaces client is closed or disconnected?

Real-Time Synchronization: Are there more efficient ways to synchronize FSLogix profiles (VHD files) between instances in different regions?

Best Practices for Multi-Region WorkSpaces: Are there better architectures or tools for sharing FSLogix profiles between AWS WorkSpaces across regions?

Example Scenario

Current Behavior: User logs into a WorkSpace in the primary region, updates files, and then attempts to log into a WorkSpace in the secondary region. The profile is locked, requiring a full sign-out from the primary WorkSpace before proceeding.

Desired Behavior: When the user logs into the secondary WorkSpace, the session in the primary region should automatically terminate, releasing the profile lock and providing access to the updated profile in the secondary region.

We appreciate any suggestions or best practices to resolve these challenges. Thank you in advance for your help!

Upvotes: 0

Views: 25

Answers (0)

Related Questions