Amazon WorkSpaces protocol "WSP" has been renamed to "DCV" starting from October 2024

Amazon WorkSpaces protocol "WSP" has been renamed to "DCV" starting from October 2024

When I asked the generative AI, it replied "The protocols that can be used with Amazon WorkSpaces are WSP and PCoIP," but I thought this seemed different from what the documentation says.
2025.08.13

Good evening, this is Chiba (Sachi).

This time, what I want to say is almost entirely in the title.

As of August 2025, the AWS documentation states that Amazon WorkSpaces Personal supports the following two protocols:

  • DCV
  • PCoIP

Networking protocols and access for WorkSpaces Personal - Amazon WorkSpaces

When referring to slightly older information, you can find many documents stating "either WSP or PCoIP". And the term "WSP" still appears everywhere in official documentation and API return values.

After investigating what this means, I found that in October 2024, the protocol name was changed from WSP to DCV. At that time, our colleague Shibata wrote an explanatory blog. It seems that while WSP was renamed to DCV, the term WSP itself hasn't completely disappeared.

https://dev.classmethod.jp/articles/nice-dcv-renames-to-amazon-dcv/

Although the announcement was properly made, since the content was "NICE DCV renamed to Amazon DCV. And WSP also renamed to Amazon DCV", the latter change wasn't particularly highlighted. I couldn't easily find it with my Google skills.

Since I spent about 15 minutes researching "when and where was this protocol renaming announced...!", I'm writing this blog to save others those 15 minutes.

Honestly, I've said almost everything I wanted to say, and since Shibata's blog from that time covers the details including sources, you probably won't have much trouble if you don't read beyond this point. If you found this article because you were confused about the relationship between WSP and DCV, directing you to Shibata's article is this post's main purpose.

Summary

  • In October 2024, WSP was renamed to DCV
  • In official documentation (admin guide/user guide), the notation has mostly been unified to DCV
  • In the AWS Management Console and references, expressions like DCV (formerly WSP) are often used
  • In APIs, it remains WSP just as before the renaming
  • The official name of DCV is "Amazon DCV", but depending on context, it's sometimes simply expressed as DCV

Reviewing the basics of Amazon WorkSpaces

Before checking the protocols, let's review Amazon WorkSpaces more broadly. My knowledge of Amazon WorkSpaces is from around 2019, but things seem to have changed a lot since then.### Amazon WorkSpaces Family Consisting of Multiple Services

Amazon WorkSpaces is a virtual desktop service. Currently, there is a larger service category called Amazon WorkSpaces Family, which includes multiple services within it.

  1. Amazon WorkSpaces: Cloud-native virtual desktop
  2. Amazon WorkSpaces Core: Virtual desktop infrastructure and APIs for third-party VDI software
  3. Amazon WorkSpaces Secure Browser: Cloud-native remote enterprise browser
  4. Amazon WorkSpaces Thin Client: Cost-effective secure access to virtual desktops

https://aws.amazon.com/jp/workspaces-family/

When simply saying "Amazon WorkSpaces," 99% of the time it refers to service "1." You'll rarely need to interact with the other services, so just remember them when necessary.

In the rest of this blog, when I say "Amazon WorkSpaces," I'm referring to service "1."

Two Types to Choose from in Amazon WorkSpaces

"1. Amazon WorkSpaces" has two types:

  • Amazon WorkSpaces Personal: Provides a persistent virtual desktop environment
  • Amazon WorkSpaces Pools: Provides a pool of non-persistent virtual desktop environments

Amazon WorkSpaces Pools was introduced in June 2024, and with its introduction, the traditional "Amazon WorkSpaces" was renamed "Amazon WorkSpaces Personal."

When simply saying "Amazon WorkSpaces," about 98% of the time it refers to "WorkSpaces Personal."

Streaming Protocols Available in Amazon WorkSpaces

In Amazon WorkSpaces, virtual desktop environments run on Amazon-managed VPCs. Clients can use the virtual desktop environment by streaming the virtual desktop through a dedicated gateway.

Clients stream using either a dedicated application or a compatible web browser (Web Access). The protocol used for streaming is either "DCV or PCoIP" as mentioned at the beginning.

Below is a summary of the compatibility between types, connection methods, and protocols.

Type Connection Method DCV (former WSP) PCoIP
WorkSpaces Personal Client Application ⚪︎ ⚪︎
WorkSpaces Personal Web Access ⚪︎ △※1
WorkSpaces Pools Client Application ⚪︎

※1: Supported but with many limitations### History of Streaming Protocols Used in Amazon WorkSpaces

Relatively speaking, DCV (formerly WSP) is a new protocol. Previously, Amazon WorkSpaces only supported PCoIP. Here's a brief summary of protocol-related events:

Considering the long history of Amazon WorkSpaces, it's clear that WSP (now DCV) is a relatively new concept.

Let's also look at this in relation to Amazon AppStream 2.0, which is often compared to Amazon WorkSpaces as another AWS EUC (End User Computing) service.

First, here's an excerpt from an online seminar held in November 2019:

2019_BlackBelt
From https://d1.awsstatic.com/webinars/jp/pdf/services/20191126_AWS-BlackBelt_AmazonAppStream2.0.pdf#page=9

👆Amazon AppStream 2.0 shows NICE DCV (the predecessor of Amazon DCV), while Amazon WorkSpaces only lists PCoIP. NICE DCV was adopted by Amazon AppStream 2.0 first.

And in February 2023 documentation, the expression became:

Amazon_AppStream_2_0_2023From https://pages.awscloud.com/rs/112-TZM-766/images/AWS-Black-Belt_2023_Amazon-AppStream-2.0_0228_v1.pdf

👆WSP and DCV are shown as protocols used across various EUC services.

And in the comparison table, there is a description stating that "WSP equals NICE DCV."

Amazon_AppStream_2_0_2023_2
Image source: same as above

This expression is likely used because WSP was originally developed based on NICE DCV. I now understand the flow: NICE DCV was renamed to Amazon DCV in October 2024, which led to WSP also being unified under the DCV name.

Completely tangential story

The original Amazon AppStream (without 2.0) was released in November 2013. It appears that Amazon AppStream used a protocol called STX.

The SDK connects the developer's application with the Amazon AppStream STX Protocol that manages the streaming process. The Protocol monitors the network status and automatically adapts video streaming to provide customers with a low-latency, high-resolution user experience.

2013 AppStream
From https://www.slideshare.net/slideshow/aws-reinvent-2013-report-report-appstream/29058478

Various Descriptions About DCV and WSP in Amazon WorkSpaces

So far, we've briefly reviewed Amazon WorkSpaces and its protocols. Next, let's look at "How the change from WSP to DCV is described in various places?"### Description in AWS Official Documentation (Admin Guide/User Guide)

Amazon WorkSpaces provides an admin guide and a user guide.

In both guides, the protocol is simply described as "DCV." If these documents had included expressions like "DCV (formerly WSP)" or explanations such as "DCV was previously known as WSP," people like me would have been less confused.

One thing to note is that in images within the documentation, the WSP designation still remains. This is probably because changing images is more challenging than updating text.

Architecture_diagram
From https://docs.aws.amazon.com/workspaces/latest/adminguide/managing-wsp-personal.html

While the documentation update history doesn't mention the protocol's renaming, there is a relevant entry in the host agent release notes.

Release Date Changes
Windows WorkSpaces - 2.1.0.1786 October 31, 2024 Renamed WorkSpaces Streaming Protocol (WSP) to Amazon DCV. ...(omitted)

In the API reference, it's described as "DCV (formerly WSP)".

  • You don't need to specify the PCOIP protocol for Linux bundles because DCV (formerly WSP) is the default protocol for those bundles.

CreateWorkspaces - Amazon WorkSpaces Service

  • The Protocols property is case sensitive. Ensure you use PCOIP or DCV (formerly WSP).

WorkspaceProperties - Amazon WorkSpaces Service

It's in a peculiar state where it's expressed as DCV, but you actually need to specify WSP as the value, otherwise you'll get an error. It seems unlikely that this will change in the future.

Description in AWS re:Post Knowledge Center

I found an official AWS description in AWS re:Post. Here it's expressed as "DCV (formerly WSP)".

For DCV (formerly WSP) WorkSpaces, clients need to connect to TCP port 4195.

Troubleshooting issues with accessing Windows WorkSpace | AWS re:Post

TCP port 4195 for DCV (formerly WSP) WorkSpaces

Troubleshooting WorkSpaces connectivity issues | AWS re:Post

Description in AWS Management Console

In the AWS Management Console, it's expressed as "DCV (formerly WSP)" or "DCV (WSP)".

WorkSpaces_Personal___WorkSpaces_Console

In the bundle selection screen, it's simply labeled as "WSP".

Step_2___Configure_WorkSpace___WorkSpaces_Console### AWS CLI Description

In AWS CLI (and by extension, the AWS API), the term remains simply as "WSP". Since changing values handled by the API could have significant impacts, they appear to be maintaining "WSP" even after the renaming.

WorkSpaces that are displayed as "DCV(WSP)" in the console are simply returned as "WSP" in AWS CLI results.

			
			$ aws workspaces describe-workspaces \
  --query "Workspaces[*].[ComputerName,WorkspaceProperties.Protocols[0]]" \
  --output text

EC2AMZN-XXXXXXX WSP
EC2AMZN-XXXXXXX WSP
EC2AMZN-XXXXXXX WSP
EC2AMZN-XXXXXXX WSP
EC2AMZN-XXXXXXX WSP
WSAMZN-XXXXXXX WSP

		

Let's also check the public bundles in the Tokyo region. Regarding bundles, there's no output in AWS CLI that directly represents the protocol itself, so we need to determine it from the name or description.

			
			$ aws workspaces describe-workspace-bundles \
  --owner AMAZON \
  --query "Bundles[*].[BundleId,Name,Description]" \
  --output text | sed 's/\t/,/g' | grep DCV

		

👆There are none containing "DCV".

For reference, here's a bit more of the results. It's clear that there are only "PCoIP" or "WSP (and WorkSpaces Streaming Protocol)" or "No Streaming Protocol (for BYOP)".

About 30% of the full results
			
			wsb-fqllktgz5,Standard with Windows 10 and Office 2019 Pro Plus (Server 2022 based) (PCoIP) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with 64bit Microsoft Office 2019 Pro Plus and PCoIP 2 vCPU 4GiB Memory 50GB Storage (Japanese)
wsb-5gzk487rr,GraphicsPro.g4dn with Windows 10 (Server 2022 based) (WSP) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with WorkSpaces Streaming Protocol 16 vCPU 64GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (Japanese)
wsb-hflmxmbbz,Value with Red Hat Enterprise Linux 8,Red Hat Enterprise Linux 8 GNOME Desktop Environment with WorkSpaces Streaming Protocol 1 vCPU 2GiB Memory 10GB Storage (English)
wsb-hwwp9rslw,Value with Windows Server 2019 (BYOP),Windows Server 2019 with No Streaming Protocol 1 vCPU 2GiB Memory 10GB Storage (English)
wsb-j6z7w9tk5,Performance with Windows 10 (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with WorkSpaces Streaming Protocol 2 vCPU 7.5GiB Memory 100GB Storage (Japanese)
wsb-vlq5cxrsz,PowerPro with Windows 10 and Office 2019 Pro Plus (Server 2022 based) (PCoIP) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with 64bit Microsoft Office 2019 Pro Plus and PCoIP 8 vCPU 32GiB Memory 100GB Storage (Japanese)
wsb-xyv83v8b5,Graphics.g4dn with Windows 10 (Server 2022 based) (WSP),Windows Desktop Experience provided by Windows Server 2022 with TPM with WorkSpaces Streaming Protocol 4 vCPU 16GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (English)
wsb-8x5p9z0dm,Performance with Windows Server 2022 (BYOP) (Japanese),Windows Server 2022 with TPM with No Streaming Protocol 2 vCPU 8GiB Memory 100GB Storage (Japanese)
wsb-gk1wpk43z,Standard with Windows 10 (Server 2019 based),Windows 10 Experience powered by Windows Server 2019 with PCoIP 2 vCPU 4GiB Memory 50GB Storage (English)
wsb-2lc8mbdsn,Power with Windows 10 and Office 2016 Pro Plus (Server 2016 based) (Japanese),Windows 10 Experience provided by Windows Server 2016 with Office 2016 and PCoIP 4 vCPU 16GiB Memory 100GB Storage (Japanese)
wsb-6vvd8tq1l,Standard with Windows 10 and Office 2019 Pro Plus (Server 2019 based),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and PCoIP 2 vCPU 4GiB Memory 50GB Storage (English)
wsb-bf5th9f2y,PowerPro with Windows 10 (Server 2019 based),Windows 10 Experience powered by Windows Server 2019 with WorkSpaces Streaming Protocol 8 vCPU 32GiB Memory 100GB Storage (English)
wsb-dn1vx9kwp,PowerPro with Windows Server 2022 (BYOP) (Japanese),Windows Server 2022 with TPM with No Streaming Protocol 8 vCPU 32GiB Memory 100GB Storage (Japanese)
wsb-gm4d5tx2v,Performance with Windows 10 (Server 2016 based),Windows 10 Experience provided by Windows Server 2016 with PCoIP 2 vCPU 7.5GiB Memory 100GB Storage
wsb-3dv91jbcg,Power with Windows Server 2022 (BYOP),Windows Server 2022 with TPM with No Streaming Protocol 4 vCPU 16GiB Memory 100GB Storage (English)
wsb-8wj6hjz8r,PowerPro with Windows 10 and Office 2019 Pro Plus (Server 2022 based) (WSP),Windows Desktop Experience provided by Windows Server 2022 with TPM with 64bit Microsoft Office 2019 Pro Plus and WorkSpaces Streaming Protocol 8 vCPU 32GiB Memory 100GB Storage (English)
wsb-jqtl3ms8d,GraphicsPro with Windows 10 and Office 2019 Pro Plus (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and PCoIP 16 vCPU 122GiB Memory 100GB Storage (Japanese)
wsb-kflpvfq6f,Graphics.g4dn with Windows Server 2019 (BYOP),Windows Server 2019 with No Streaming Protocol 4 vCPU 16GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (English)
wsb-v5znyph46,GraphicsPro.g4dn with Windows Server 2019 (BYOP),Windows Server 2019 with No Streaming Protocol 16 vCPU 64GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (English)
wsb-wrmglv3g6,Standard with Windows 10 and Office 2019 Pro Plus (Server 2022 based) (WSP) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with 64bit Microsoft Office 2019 Pro Plus and WorkSpaces Streaming Protocol 2 vCPU 4GiB Memory 50GB Storage (Japanese)
wsb-wm34qc877,PowerPro with Windows 10 and Office 2019 Pro Plus (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and PCoIP 8 vCPU 32GiB Memory 100GB Storage (Japanese)
wsb-4cc39lz4t,Power with Windows 10 and Office 2019 Pro Plus (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and PCoIP 4 vCPU 16GiB Memory 100GB Storage (Japanese)
wsb-6cdbk8901,Performance with Windows 10 and Office 2016 Pro Plus (Server 2016 based),Windows 10 Experience provided by Windows Server 2016 with Office 2016 and PCoIP 2 vCPU 7.5GiB Memory 100GB Storage
wsb-h90sf22n7,Standard with Windows 10 (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with WorkSpaces Streaming Protocol 2 vCPU 4GiB Memory 50GB Storage (Japanese)
wsb-2144yld8f,Value with Rocky 8,Rocky 8 GNOME Desktop Environment with WorkSpaces Streaming Protocol 1 vCPU 2GiB Memory 10GB Storage (English)
wsb-39nl99v7l,Performance with Windows 10 (Server 2022 based) (PCoIP),Windows Desktop Experience provided by Windows Server 2022 with TPM with PCoIP 2 vCPU 8GiB Memory 100GB Storage (English)
wsb-bh8rsxt14,Value with Windows 10 (Server 2016 based),Windows 10 Experience provided by Windows Server 2016 with PCoIP 1 vCPU 2GiB Memory 10GB Storage
wsb-g6cfwkdpz,Graphics.g4dn with Windows 10 (Server 2022 based) (PCoIP),Windows Desktop Experience provided by Windows Server 2022 with TPM with PCoIP 4 vCPU 16GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (English)
wsb-1pwvl14jn,Value with Windows 10 and Office 2019 Pro Plus (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and WorkSpaces Streaming Protocol 1 vCPU 2GiB Memory 10GB Storage (Japanese)
wsb-92tn3b7gx,Value with Windows 7,Windows 7 Experience provided by Windows Server 2008 R2 with PCoIP 1 vCPU 2GiB Memory 10GB Storage
wsb-5zyypds9c,Power with Windows Server 2019 (BYOP) (Japanese),Windows Server 2019 with No Streaming Protocol 4 vCPU 16GiB Memory 100GB Storage (Japanese)
wsb-xhzyys004,Power with Windows 10 (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with PCoIP 4 vCPU 16GiB Memory 100GB Storage (Japanese)
wsb-888n86lsq,Value with Windows 10 (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with PCoIP 1 vCPU 2GiB Memory 10GB Storage (Japanese)
wsb-dk55sygy0,Performance with Windows 10 (Server 2016 based) (Japanese),Windows 10 Experience provided by Windows Server 2016 with PCoIP 2 vCPU 7.5GiB Memory 100GB Storage (Japanese)
wsb-w94f3tgkh,Performance with Windows 10 and Office 2019 Pro Plus (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and WorkSpaces Streaming Protocol 2 vCPU 7.5GiB Memory 100GB Storage (Japanese)
wsb-5rldsz4nl,Standard with Windows 10 (Server 2022 based) (PCoIP),Windows Desktop Experience provided by Windows Server 2022 with TPM with PCoIP 2 vCPU 4GiB Memory 50GB Storage (English)
wsb-6081l95sg,Graphics.g4dn with Windows Server 2022 (BYOP),Windows Server 2022 with TPM with No Streaming Protocol 4 vCPU 16GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (English)
wsb-8ds434h6p,Power with Windows 10 and Office 2019 Pro Plus (Server 2022 based) (WSP) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with 64bit Microsoft Office 2019 Pro Plus and WorkSpaces Streaming Protocol 4 vCPU 16GiB Memory 100GB Storage (Japanese)
wsb-dxnkbf67s,Power with Windows 10 (Server 2022 based) (PCoIP) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with PCoIP 4 vCPU 16GiB Memory 100GB Storage (Japanese)
wsb-dfyzk6mz7,Standard with Windows 10 and Office 2016 Pro Plus (Server 2016 based),Windows 10 Experience provided by Windows Server 2016 with Office 2016 and WorkSpaces Streaming Protocol 2 vCPU 4GiB Memory 50GB Storage (English)
wsb-391xpys5j,PowerPro with Windows 10 (Server 2022 based) (WSP) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with WorkSpaces Streaming Protocol 8 vCPU 32GiB Memory 100GB Storage (Japanese)
wsb-8cr4763wd,PowerPro with Red Hat Enterprise Linux 8 (Japanese),Red Hat Enterprise Linux 8 GNOME Desktop Environment with WorkSpaces Streaming Protocol 8 vCPU 32GiB Memory 100GB Storage (Japanese)
wsb-1zs7fqzhz,Performance with Windows Server 2019 (BYOP),Windows Server 2019 with No Streaming Protocol 2 vCPU 8GiB Memory 100GB Storage (English)
wsb-0rz9h7m0m,Graphics.g4dn with Windows 10 and Office 2019 Pro Plus (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and PCoIP 4 vCPU 16GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (Japanese)
wsb-b53htjptj,Standard with Windows Server 2019 (BYOP) (Japanese),Windows Server 2019 with No Streaming Protocol 2 vCPU 4GiB Memory 50GB Storage (Japanese)
wsb-jgd1k6zg4,Value with Windows Server 2019 (BYOP) (Japanese),Windows Server 2019 with No Streaming Protocol 1 vCPU 2GiB Memory 10GB Storage (Japanese)
wsb-kgdcvc8yc,GeneralPurpose.8xlarge with Windows 10 (Server 2022 based) (BYOP) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with No Streaming Protocol 32 vCPU 128 GiB Memory 175 GB Storage (Japanese)
wsb-6vttw8tg3,Standard with Windows 10 (Server 2022 based) (PCoIP) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with PCoIP 2 vCPU 4GiB Memory 50GB Storage (Japanese)
wsb-3vw4c37lm,Standard with Windows 10 and Office 2016 Pro Plus (Server 2016 based) (Japanese),Windows 10 Experience provided by Windows Server 2016 with Office 2016 and PCoIP 2 vCPU 4GiB Memory 50GB Storage (Japanese)
wsb-b1gz69yyy,PowerPro with Windows 10 (Server 2022 based) (WSP),Windows Desktop Experience provided by Windows Server 2022 with TPM with WorkSpaces Streaming Protocol 8 vCPU 32GiB Memory 100GB Storage (English)
wsb-0qcgctgrv,PowerPro with Windows Server 2022 (BYOP),Windows Server 2022 with TPM with No Streaming Protocol 8 vCPU 32GiB Memory 100GB Storage (English)
wsb-0mpskjfmf,Performance with Windows 10 and Office 2019 Pro Plus (Server 2022 based) (WSP),Windows Desktop Experience provided by Windows Server 2022 with TPM with 64bit Microsoft Office 2019 Pro Plus and WorkSpaces Streaming Protocol 2 vCPU 8GiB Memory 100GB Storage (English)
wsb-x5142w8dw,Power with Windows 10 and Office 2019 Pro Plus (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and WorkSpaces Streaming Protocol 4 vCPU 16GiB Memory 100GB Storage (Japanese)
wsb-d05xp3jc8,Performance with Windows 10 (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with PCoIP 2 vCPU 7.5GiB Memory 100GB Storage (Japanese)
wsb-88p2c5sr7,PowerPro with Windows 10 (Server 2016 based) (Japanese),Windows 10 Experience provided by Windows Server 2016 with PCoIP 8 vCPU 32GiB Memory 100GB Storage (Japanese)
wsb-chjqprhj9,Standard with Ubuntu 22.04 (Japanese),Ubuntu 22.04 GNOME Desktop Environment with WorkSpaces Streaming Protocol 2 vCPU 4GiB Memory 50GB Storage (Japanese)
wsb-b4p8q6w2p,GraphicsPro.g4dn with Windows 10 and Office 2019 Pro Plus (Server 2019 based),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and PCoIP 16 vCPU 64GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (English)
wsb-vfk2nwr1h,Standard with Windows 10 and Office 2016 Pro Plus (Server 2016 based) (Japanese),Windows 10 Experience provided by Windows Server 2016 with Office 2016 and WorkSpaces Streaming Protocol 2 vCPU 4GiB Memory 50GB Storage (Japanese)
wsb-fx3bdyds8,PowerPro with Windows 10 (Server 2019 based),Windows 10 Experience powered by Windows Server 2019 with PCoIP 8 vCPU 32GiB Memory 100GB Storage (English)
wsb-58c9s34pz,Performance with Windows 10 and Office 2019 Pro Plus (Server 2019 based),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and PCoIP 2 vCPU 7.5GiB Memory 100GB Storage (English)
wsb-6ztc3ls4b,Graphics.g4dn with Windows 10 (Server 2022 based) (PCoIP) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with PCoIP 4 vCPU 16GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (Japanese)
wsb-8wthbqzhx,Standard with Red Hat Enterprise Linux 8,Red Hat Enterprise Linux 8 GNOME Desktop Environment with WorkSpaces Streaming Protocol 2 vCPU 4GiB Memory 50GB Storage (English)
wsb-9757zbz1z,Graphics.g4dn with Windows Server 2022 (BYOP) (Japanese),Windows Server 2022 with TPM with No Streaming Protocol 4 vCPU 16GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (Japanese)
wsb-9jvhtb24f,Standard with Windows 10 and Office 2016 Pro Plus (Server 2016 based),Windows 10 Experience provided by Windows Server 2016 with Office 2016 and PCoIP 2 vCPU 4GiB Memory 50GB Storage
wsb-djp2k6jxl,Standard with Rocky 8,Rocky 8 GNOME Desktop Environment with WorkSpaces Streaming Protocol 2 vCPU 4GiB Memory 50GB Storage (English)
wsb-kft3y4qsw,PowerPro with Windows 10 and Office 2019 Pro Plus (Server 2019 based),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus and PCoIP 8 vCPU 32GiB Memory 100GB Storage (English)
wsb-6fphfyzqg,GeneralPurpose.4xlarge with Windows 10 (Server 2022 based) (Japanese),Windows Desktop Experience provided by Windows Server 2022 with TPM with WorkSpaces Streaming Protocol 16 vCPU 64 GiB Memory 175 GB Storage (Japanese)
wsb-j0w8d23sc,GraphicsPro.g4dn with Ubuntu 22.04 (Japanese),Ubuntu 22.04 GNOME Desktop Environment with WorkSpaces Streaming Protocol 16 vCPU 64GiB Memory 1 GPU 16GiB Video Memory 100GB Storage (Japanese)
wsb-v6727whq5,Power with Windows 10 (Server 2019 based),Windows 10 Experience powered by Windows Server 2019 with PCoIP 4 vCPU 16GiB Memory 100GB Storage (English)
wsb-fb2xfp6r8,Value with Windows 10 (Server 2019 based),Windows 10 Experience powered by Windows Server 2019 with WorkSpaces Streaming Protocol 1 vCPU 2GiB Memory 10GB Storage (English)
wsb-05t16yhz8,Performance with Windows 10 and Office 2016 Pro Plus (Server 2016 based),Windows 10 Experience provided by Windows Server 2016 with Office 2016 and WorkSpaces Streaming Protocol 2 vCPU 7.5GiB Memory 100GB Storage (English)
wsb-gttgrcdj2,Standard with Windows Server 2019 (BYOP),Windows Server 2019 with No Streaming Protocol 2 vCPU 4GiB Memory 50GB Storage (English)
wsb-3v313gvgc,PowerPro with Rocky 8,Rocky 8 GNOME Desktop Environment with WorkSpaces Streaming Protocol 8 vCPU 32GiB Memory 100GB Storage (English)
wsb-wdxhc0y7w,GraphicsPro.g4dn with Windows 10 and Office 2019 Pro Plus (Server 2019 based) (Japanese),Windows 10 Experience powered by Windows Server 2019 with 64bit Microsoft Office 2019 Pro Plus an:::

## Summary (repeated)

- Renamed from `WSP` to `DCV` in October 2024
- In official documentation (administrator guide/user guide), the term `DCV` is used almost consistently
- In AWS Management Console and references, expressions like `DCV (formerly WSP)` are often used
- In the API, it remains unchanged as `WSP`
- The official name is "Amazon DCV", but depending on context, it may be simply expressed as `DCV`

Remember that DCV is WSP, for clarity it's best to use `DCV (formerly WSP)`, and in APIs it's still treated as WSP.

## Conclusion

This article covered the name change of the Amazon WorkSpaces protocol from WSP to DCV.

While I'm writing this article in August 2025, the change happened in October 2024, which feels like a somewhat ambiguous transition period that's neither too old nor too new. Due to this transition period, there may be many occasions for confusion, so I hope this article serves as a useful reference.

Also, at this time, many of the major generative AI models have knowledge cutoff dates before October 2024. When asking questions to these models without enabling web search, they are likely to respond with "Amazon WorkSpaces supports WSP and PCoIP protocols," so please be aware of this.

This has been [Chiba Yuki (@batchicchi)](https://x.com/batchicchi).

## References

- [AWS Introduction Blog Relay 2024 - Amazon WorkSpaces Family Edition | DevelopersIO](https://dev.classmethod.jp/articles/introduction-2024-amazon-workspaces-family/)
- [AWS Re-Introduction Blog Relay Amazon AppStream 2.0 Edition | DevelopersIO](https://dev.classmethod.jp/articles/re-introduction-2020-appstream2/)
- [WorkSpaces Pools Bundles - Amazon WorkSpaces](https://docs.aws.amazon.com/ja_jp/workspaces/latest/adminguide/instance-types.html)


		

Share this article

FacebookHatena blogX

Related articles