Choosing the Right Pattern
Virtual Desktop Infrastructure (VDI) in the cloud is not one-size-fits-all. The two primary patterns — persistent and non-persistent — have fundamentally different cost structures, management overhead, and user experiences. Matching the pattern to the user persona is the core architectural decision.
1. Persistent VDI (WorkSpaces)
| Dimension | Detail |
|---|---|
| Target Users | Developers, power users, executives, full-time employees |
| User Experience | "My Desktop" — personalized, stateful, always available |
| Cost Model | Higher — monthly fee or hourly with base charge; instance runs continuously or resumes on demand |
| Patching | Higher overhead — each WorkSpace is an individual instance; you must patch OS and agents on every WorkSpace (use AWS Systems Manager for automation) |
| Storage | Local drive persists; user files survive logoff |
Key operational challenge: At scale (hundreds of WorkSpaces), patching becomes a significant operational burden. Without automation via SSM (AWS Systems Manager), you are manually managing hundreds of individual Windows instances. This is the hidden cost of persistent VDI that is often underestimated during planning.
2. Non-Persistent VDI (AppStream 2.0 or WorkSpaces Pools)
| Dimension | Detail |
|---|---|
| Target Users | Call center agents, lab students, contractors, kiosk users |
| User Experience | "Fresh Start" — clean environment every session |
| Cost Model | Lower — pay per session hour; scale to zero when unused |
| Patching | Lower overhead — patch the Golden Image once, update the fleet, and every new session gets the patched version automatically |
| Storage | Local drive wiped on session end; persistent storage requires Home Folders (S3), OneDrive, or Google Drive |
The golden image advantage: In non-persistent VDI, patching is a one-time operation per update cycle. You update the image, push it to the fleet, and every subsequent session is clean and patched. There is no concept of "drift" — a WorkSpace that hasn't been patched in 6 months because the user never reboots it. This is the primary operational advantage of non-persistent VDI at scale.
WorkSpaces Pools (a newer AWS offering) bridges the gap: it provides a WorkSpaces-like full desktop experience but with non-persistent, fleet-based provisioning — combining the familiar desktop UI of WorkSpaces with the operational simplicity of AppStream's fleet model.