Amazon WorkSpaces Applications

Name: Amazon WorkSpaces Applications
Brand: Amazon Web Services (AWS)
Rating: 4.4 (111 reviews)

Leader

Official Global LinkedIn page for Amazon Web Services (AWS).

Est 2006|Valuation $2560B

LinkedIn 10.9M|Website|Web traffic 1.1M|FTEs 148,001|HQ Seattle, Washington, US

MarketsDesktop as a Service (DaaS)

Platform CoversIT Asset Management (ITAM)Digital Employee Experience (DEX)Development Environments

Amazon WorkSpaces Applications screenshot

Published Oct 13, 2026

01Common complaints

- An organization that requires the most mature published-app experience with deep policy tuning and an extensive third-party ecosystem: Citrix DaaS may provide a broader feature set at the cost of additional licensing and complexity. - Users with extreme latency sensitivity (for example, interactive 3D manipulation or time-critical UI workflows) where fleet proximity and network guarantees cannot be provided; multiple reports indicate degraded interactivity in some scenarios. - Teams with limited in-house EUC or image engineering capacity that expect a managed service to require no image lifecycle work; community reports indicate image creation and maintenance can demand ongoing effort. - An organization whose cost model requires very predictable per-user pricing without usage-driven variability; WorkSpaces Applications can be cost-effective for some patterns and expensive for others. - Situations where Microsoft licensing implications are unclear for specific applications; licensing misunderstandings can create compliance risk. **From community feedback (non-exhaustive):** - Scaling policy and fleet start/stop delays - Long image creation times and operational friction - Persistent storage configuration issues in some deployments - Performance and latency limitations for interactive workloads **From reviews (G2 summary):** - Cost concerns for larger deployments - Challenges adapting legacy applications to streaming **Vendor-acknowledged limitations** - AWS documentation emphasizes configuration and control patterns (for example, application access control via AppLocker). AWS does not publish a single consolidated "known issues" list for the service; operational problems are typically tracked via service health dashboards, release notes, and support cases.

02Why they buy

Documented differentiators (not all independently verified): - Streams desktop applications without requiring application code changes. - A managed service model integrated with AWS infrastructure and services (IAM, VPC, monitoring). - Expanded instance type and storage configuration options announced in Nov 2025, and the ability to import custom EC2 AMIs for images. User feedback–supported differentiators (limited but present): - Review summaries cite relatively fast initial setup and straightforward integration within AWS environments. Where competitors have clearer advantages: - Citrix: enterprise-grade published-app UX and optimization features. - AVD: licensing and ecosystem alignment for Microsoft-centric organizations.

User feedback–supported differentiators (limited but present):

Key Differentiator

03Field reports

Because WorkSpaces Applications is a rebrand, review content is fragmented across AppStream 2.0, WorkSpaces Applications listings, and WorkSpaces (DaaS) reviews. These sources are not identical but are often evaluated together by buyers.

Review platforms (examples)

**G2 — Amazon AppStream 2.0** - Positive sentiment themes: reported ease of setup, fast initial configuration, and reliable performance; cost concerns are noted for larger teams. - Example positive review excerpt (G2 listing): "Appstream 2.0 is a good VDI and App Virtualization solution." (Reviewer: Infrastructure Architect; enterprise context; recent) - Example negative feedback excerpt: "Be more adaptable regarding the virtualization of legacy applications." (same G2 review) **G2 — Amazon WorkSpaces (desktops, adjacent)** - The separate Amazon WorkSpaces product page includes user reviews addressing latency, client user experience, and pricing complexity; these comments are relevant when comparing desktop virtualization versus application streaming. **Gartner Peer Insights — Amazon WorkSpaces applications** - Gartner hosts a listing for Amazon WorkSpaces applications. Access may be gated, but the listing indicates product category alignment.

Community / social (Reddit) — recurring user-reported issues

**Operational friction, reliability, and scaling complaints** - Recent community posts report frequent production-level escalations, scaling policy problems, slow image creation, and delays when stopping and starting fleets, as well as issues with persistent storage configurations (for example, S3-backed persistent storage). These reports reflect administrator operational challenges rather than vendor claims. **User experience and performance reports** - Multiple community threads describe degraded interactive performance for graphics-intensive and 3D workloads and longer sign-in times compared with some alternative solutions. **Monitoring and permissions complexity** - Community posts have documented permission errors (such as AccessDenied on PutMetricData) due to missing identity-based policies, demonstrating that managed services still require careful IAM role and policy configuration. **Client and endpoint workflow notes** - Threads describing how to set or save the application portal URL for the WorkSpaces Applications desktop client via registry keys indicate some client configuration details are not centrally manageable by default and may require manual workarounds.

Reasons customers select this product (inferred from reviews and discussions)

Alignment with AWS-native architecture and security controls
Centralized application delivery and reduced endpoint footprint
Elasticity for variable or seasonal usage

Reasons some customers avoid or leave the product (from complaints)

Performance and latency concerns compared to alternatives for certain workloads
Operational overhead: image management, scaling, and troubleshooting
Cost unpredictability when usage patterns change
Limitations with legacy applications and certain multi-monitor or notification workflows

Vendor-commissioned economic study (Forrester TEI)

AWS hosts a Forrester Total Economic Impact (TEI) report covering AWS End User Computing (including WorkSpaces and AppStream 2.0). Such reports present modeled ROI and benefits based on interviews and assumptions.
Critical evaluation: TEI studies are vendor-sponsored and depend on interview-based modeling and assumptions; buyers should treat ROI figures as directional and validate them against internal metrics and constraints.

Feature announcements as indicative evidence

- AWS announced recently that WorkSpaces Applications expanded available compute instance types and sizes, configurable storage volume sizes, and the ability to import custom EC2 AMIs for images. - Critical evaluation: increased feature breadth can reduce cost-performance mismatches, but announcements do not guarantee improved user experience or reduced operational overhead; validation through pilots is still recommended. **Gap:** Public, independently verified customer case studies focused specifically on WorkSpaces Applications (as distinct from the broader AWS EUC suite) are less visible compared with Citrix or Microsoft ecosystems.

04Best fit

**Company size** - Typically justified for mid-market to large enterprise organizations with significant user populations where centralized management and security justify image lifecycle and operations costs. **Industries / verticals** - Regulated industries (healthcare, finance) where restricting data exposure on endpoints is a priority. - Engineering, design, and architecture firms that may stream GPU-enabled applications, subject to performance validation. **Roles / personas** - Decision makers: CIO/CTO, Head of Infrastructure, Security leadership, End User Computing (EUC) managers. - Implementers: AWS platform engineers, EUC/VDI administrators, identity and directory engineers. **Pain points addressed** - Delivering applications to unmanaged or heterogeneous endpoints - Centralizing sensitive data and reducing local installation sprawl - Faster onboarding and offboarding compared to shipping physical devices **Deal disqualifiers (poor fit indicators)** - Small teams without AWS operations capacity to manage images and scaling - Extremely latency-sensitive workloads where local workstation performance is required and fleet placement cannot mitigate network conditions - Organizations primarily invested in Microsoft endpoint management that prefer AVD or Windows 365

05The pitch

Amazon WorkSpaces Applications (AWS EUC) is AWS's managed application streaming service for delivering desktop applications (and full desktops) to end users over the network without requiring local installation. It is the rebranded successor to Amazon AppStream 2.0 and is marketed within the WorkSpaces family umbrella. It is typically positioned for: - Securely delivering Windows or Linux desktop applications to contractors, partners, and employees - Modernizing delivery of traditional "thick client" applications by hosting them centrally and streaming the user interface to end users - Independent software vendors (ISVs) delivering desktop software in a SaaS-like model without rewriting code Core value proposition (objective): centrally manage application images and streaming fleets, control data egress, and provide device-agnostic access (browser/native client) while using AWS primitives (VPC, IAM, CloudWatch, S3, directories/IdPs). **Target market / positioning** - Mid-market to enterprise organizations already standardized on AWS - Regulated environments needing tighter data controls than unmanaged endpoints - Engineering, design, GIS, and other GPU-assisted application delivery use cases - Call centers, BPO, and seasonal workforce scenarios where rapid provisioning and centralized controls are important **Company background** - Vendor: Amazon Web Services (AWS), part of Amazon. - Service lineage: launched historically as AppStream 2.0; currently marketed as WorkSpaces Applications within AWS End User Computing (AWS often references "Amazon WorkSpaces applications (formerly AppStream 2.0)"). **Funding / growth** - AWS is an established business unit of Amazon; service-level revenue and customer counts for WorkSpaces Applications are not publicly broken out. **Pricing model (what’s publicly clear vs not)** AWS positions Applications pricing as: - Published pricing is structured as charges for provisioned streaming resources (fleet instances) plus published per-user licensing fees that vary by operating system and applicable software licensing requirements. Evidence: - Vendor pricing overview distinguishes Applications as a combination of provisioned resources plus published per-user licensing tied to relevant Windows Server licensing for Windows-based streaming. - Vendor product documentation notes that customers are charged a published per-user licensing fee for every user that streams applications, with the fee linked to applicable Windows server licensing. - AWS blog and documentation provide scenario-based estimates and a vendor pricing tool; effective per-user costs vary widely depending on fleet sizing and usage patterns. **Important limitation:** public pricing pages are fragmented across WorkSpaces family overview and the detailed Applications/AppStream line items. Buyers typically must model costs with the vendor calculator and/or the vendor-provided pricing tool. **Total cost of ownership (TCO) considerations (often underestimated)** 1. Directory and identity costs & complexity - WorkSpaces family services commonly depend on directory integration (AWS Directory Service, AD Connector, or external IdPs), which can add both cost and operational overhead. 2. Image engineering and application packaging - Building, patching, hardening, and testing images can become a dedicated function similar to VDI "gold image" operations. 3. Fleet scaling and capacity engineering - On-demand versus always-on fleet configurations materially change cost and user experience (startup latency). 4. Licensing (especially Microsoft and third-party applications) - Windows remote-desktop/server licensing-related fees apply for Windows-based streaming; Microsoft application licensing can be a compliance risk if not correctly managed. 5. Observability and support operations - CloudWatch metrics, permissions, and incident response processes can be non-trivial to implement and maintain. **Key competitors / direct alternatives (4–6)** - Microsoft Azure Virtual Desktop (AVD) - Citrix DaaS (Citrix Virtual Apps and Desktops as a service) - VMware Horizon / Horizon Cloud - Windows 365 Cloud PC (adjacent alternative; full desktop rather than app streaming) - Kasm Workspaces (containerized workspaces / application delivery) - Traditional RDS/RemoteApp on Windows Server (self-managed)

Get a comprehensive analysis of Amazon WorkSpaces Applications including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 13, 2026

01Common complaints

An organization that requires the most mature published-app experience with deep policy tuning and an extensive third-party ecosystem: Citrix DaaS may provide a broader feature set at the cost of additional licensing and complexity.
Users with extreme latency sensitivity (for example, interactive 3D manipulation or time-critical UI workflows) where fleet proximity and network guarantees cannot be provided; multiple reports indicate degraded interactivity in some scenarios.
Teams with limited in-house EUC or image engineering capacity that expect a managed service to require no image lifecycle work; community reports indicate image creation and maintenance can demand ongoing effort.
An organization whose cost model requires very predictable per-user pricing without usage-driven variability; WorkSpaces Applications can be cost-effective for some patterns and expensive for others.
Situations where Microsoft licensing implications are unclear for specific applications; licensing misunderstandings can create compliance risk.

From community feedback (non-exhaustive):

Scaling policy and fleet start/stop delays
Long image creation times and operational friction
Persistent storage configuration issues in some deployments
Performance and latency limitations for interactive workloads

From reviews (G2 summary):

Cost concerns for larger deployments
Challenges adapting legacy applications to streaming

Vendor-acknowledged limitations

AWS documentation emphasizes configuration and control patterns (for example, application access control via AppLocker). AWS does not publish a single consolidated "known issues" list for the service; operational problems are typically tracked via service health dashboards, release notes, and support cases.

02Why they buy

Documented differentiators (not all independently verified):

Streams desktop applications without requiring application code changes.
A managed service model integrated with AWS infrastructure and services (IAM, VPC, monitoring).
Expanded instance type and storage configuration options announced in Nov 2025, and the ability to import custom EC2 AMIs for images.

User feedback–supported differentiators (limited but present):

Review summaries cite relatively fast initial setup and straightforward integration within AWS environments.

Where competitors have clearer advantages:

Citrix: enterprise-grade published-app UX and optimization features.
AVD: licensing and ecosystem alignment for Microsoft-centric organizations.

User feedback–supported differentiators (limited but present):

Key Differentiator

03Field reports

Review platforms (examples)

G2 — Amazon AppStream 2.0

Positive sentiment themes: reported ease of setup, fast initial configuration, and reliable performance; cost concerns are noted for larger teams.
Example positive review excerpt (G2 listing): "Appstream 2.0 is a good VDI and App Virtualization solution." (Reviewer: Infrastructure Architect; enterprise context; recent)
Example negative feedback excerpt: "Be more adaptable regarding the virtualization of legacy applications." (same G2 review)

G2 — Amazon WorkSpaces (desktops, adjacent)

The separate Amazon WorkSpaces product page includes user reviews addressing latency, client user experience, and pricing complexity; these comments are relevant when comparing desktop virtualization versus application streaming.

Gartner Peer Insights — Amazon WorkSpaces applications

Gartner hosts a listing for Amazon WorkSpaces applications. Access may be gated, but the listing indicates product category alignment.

Community / social (Reddit) — recurring user-reported issues

Operational friction, reliability, and scaling complaints

Recent community posts report frequent production-level escalations, scaling policy problems, slow image creation, and delays when stopping and starting fleets, as well as issues with persistent storage configurations (for example, S3-backed persistent storage). These reports reflect administrator operational challenges rather than vendor claims.

User experience and performance reports

Multiple community threads describe degraded interactive performance for graphics-intensive and 3D workloads and longer sign-in times compared with some alternative solutions.

Monitoring and permissions complexity

Community posts have documented permission errors (such as AccessDenied on PutMetricData) due to missing identity-based policies, demonstrating that managed services still require careful IAM role and policy configuration.

Client and endpoint workflow notes

Threads describing how to set or save the application portal URL for the WorkSpaces Applications desktop client via registry keys indicate some client configuration details are not centrally manageable by default and may require manual workarounds.

Reasons customers select this product (inferred from reviews and discussions)

Alignment with AWS-native architecture and security controls
Centralized application delivery and reduced endpoint footprint
Elasticity for variable or seasonal usage

Reasons some customers avoid or leave the product (from complaints)

Performance and latency concerns compared to alternatives for certain workloads
Operational overhead: image management, scaling, and troubleshooting
Cost unpredictability when usage patterns change
Limitations with legacy applications and certain multi-monitor or notification workflows

Vendor-commissioned economic study (Forrester TEI)

AWS hosts a Forrester Total Economic Impact (TEI) report covering AWS End User Computing (including WorkSpaces and AppStream 2.0). Such reports present modeled ROI and benefits based on interviews and assumptions.
Critical evaluation: TEI studies are vendor-sponsored and depend on interview-based modeling and assumptions; buyers should treat ROI figures as directional and validate them against internal metrics and constraints.

Feature announcements as indicative evidence

AWS announced recently that WorkSpaces Applications expanded available compute instance types and sizes, configurable storage volume sizes, and the ability to import custom EC2 AMIs for images.
Critical evaluation: increased feature breadth can reduce cost-performance mismatches, but announcements do not guarantee improved user experience or reduced operational overhead; validation through pilots is still recommended.

Gap: Public, independently verified customer case studies focused specifically on WorkSpaces Applications (as distinct from the broader AWS EUC suite) are less visible compared with Citrix or Microsoft ecosystems.

04Best fit

Company size

Typically justified for mid-market to large enterprise organizations with significant user populations where centralized management and security justify image lifecycle and operations costs.

Industries / verticals

Regulated industries (healthcare, finance) where restricting data exposure on endpoints is a priority.
Engineering, design, and architecture firms that may stream GPU-enabled applications, subject to performance validation.

Roles / personas

Decision makers: CIO/CTO, Head of Infrastructure, Security leadership, End User Computing (EUC) managers.
Implementers: AWS platform engineers, EUC/VDI administrators, identity and directory engineers.

Pain points addressed

Delivering applications to unmanaged or heterogeneous endpoints
Centralizing sensitive data and reducing local installation sprawl
Faster onboarding and offboarding compared to shipping physical devices

Deal disqualifiers (poor fit indicators)

Small teams without AWS operations capacity to manage images and scaling
Extremely latency-sensitive workloads where local workstation performance is required and fleet placement cannot mitigate network conditions
Organizations primarily invested in Microsoft endpoint management that prefer AVD or Windows 365

05The pitch

Securely delivering Windows or Linux desktop applications to contractors, partners, and employees
Modernizing delivery of traditional "thick client" applications by hosting them centrally and streaming the user interface to end users
Independent software vendors (ISVs) delivering desktop software in a SaaS-like model without rewriting code

Core value proposition (objective): centrally manage application images and streaming fleets, control data egress, and provide device-agnostic access (browser/native client) while using AWS primitives (VPC, IAM, CloudWatch, S3, directories/IdPs).

Target market / positioning

Mid-market to enterprise organizations already standardized on AWS
Regulated environments needing tighter data controls than unmanaged endpoints
Engineering, design, GIS, and other GPU-assisted application delivery use cases
Call centers, BPO, and seasonal workforce scenarios where rapid provisioning and centralized controls are important

Company background

Vendor: Amazon Web Services (AWS), part of Amazon.
Service lineage: launched historically as AppStream 2.0; currently marketed as WorkSpaces Applications within AWS End User Computing (AWS often references "Amazon WorkSpaces applications (formerly AppStream 2.0)").

Funding / growth

AWS is an established business unit of Amazon; service-level revenue and customer counts for WorkSpaces Applications are not publicly broken out.

Pricing model (what’s publicly clear vs not) AWS positions Applications pricing as:

Published pricing is structured as charges for provisioned streaming resources (fleet instances) plus published per-user licensing fees that vary by operating system and applicable software licensing requirements.

Evidence:

Vendor pricing overview distinguishes Applications as a combination of provisioned resources plus published per-user licensing tied to relevant Windows Server licensing for Windows-based streaming.
Vendor product documentation notes that customers are charged a published per-user licensing fee for every user that streams applications, with the fee linked to applicable Windows server licensing.
AWS blog and documentation provide scenario-based estimates and a vendor pricing tool; effective per-user costs vary widely depending on fleet sizing and usage patterns.

Important limitation: public pricing pages are fragmented across WorkSpaces family overview and the detailed Applications/AppStream line items. Buyers typically must model costs with the vendor calculator and/or the vendor-provided pricing tool.

Total cost of ownership (TCO) considerations (often underestimated)

Directory and identity costs & complexity
- WorkSpaces family services commonly depend on directory integration (AWS Directory Service, AD Connector, or external IdPs), which can add both cost and operational overhead.
Image engineering and application packaging
- Building, patching, hardening, and testing images can become a dedicated function similar to VDI "gold image" operations.
Fleet scaling and capacity engineering
- On-demand versus always-on fleet configurations materially change cost and user experience (startup latency).
Licensing (especially Microsoft and third-party applications)
- Windows remote-desktop/server licensing-related fees apply for Windows-based streaming; Microsoft application licensing can be a compliance risk if not correctly managed.
Observability and support operations
- CloudWatch metrics, permissions, and incident response processes can be non-trivial to implement and maintain.

Key competitors / direct alternatives (4–6)

Microsoft Azure Virtual Desktop (AVD)
Citrix DaaS (Citrix Virtual Apps and Desktops as a service)
VMware Horizon / Horizon Cloud
Windows 365 Cloud PC (adjacent alternative; full desktop rather than app streaming)
Kasm Workspaces (containerized workspaces / application delivery)
Traditional RDS/RemoteApp on Windows Server (self-managed)

Get a comprehensive analysis of Amazon WorkSpaces Applications including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Securely delivering Windows or Linux desktop applications to contractors, partners, and employees
Modernizing delivery of traditional "thick client" applications by hosting them centrally and streaming the user interface to end users
Independent software vendors (ISVs) delivering desktop software in a SaaS-like model without rewriting code

Target market / positioning

Mid-market to enterprise organizations already standardized on AWS
Regulated environments needing tighter data controls than unmanaged endpoints
Engineering, design, GIS, and other GPU-assisted application delivery use cases
Call centers, BPO, and seasonal workforce scenarios where rapid provisioning and centralized controls are important

Company background

Vendor: Amazon Web Services (AWS), part of Amazon.
Service lineage: launched historically as AppStream 2.0; currently marketed as WorkSpaces Applications within AWS End User Computing (AWS often references "Amazon WorkSpaces applications (formerly AppStream 2.0)").

Funding / growth

AWS is an established business unit of Amazon; service-level revenue and customer counts for WorkSpaces Applications are not publicly broken out.

Pricing model (what’s publicly clear vs not) AWS positions Applications pricing as:

Published pricing is structured as charges for provisioned streaming resources (fleet instances) plus published per-user licensing fees that vary by operating system and applicable software licensing requirements.

Evidence:

Vendor pricing overview distinguishes Applications as a combination of provisioned resources plus published per-user licensing tied to relevant Windows Server licensing for Windows-based streaming.
Vendor product documentation notes that customers are charged a published per-user licensing fee for every user that streams applications, with the fee linked to applicable Windows server licensing.
AWS blog and documentation provide scenario-based estimates and a vendor pricing tool; effective per-user costs vary widely depending on fleet sizing and usage patterns.

Total cost of ownership (TCO) considerations (often underestimated)

Directory and identity costs & complexity
- WorkSpaces family services commonly depend on directory integration (AWS Directory Service, AD Connector, or external IdPs), which can add both cost and operational overhead.
Image engineering and application packaging
- Building, patching, hardening, and testing images can become a dedicated function similar to VDI "gold image" operations.
Fleet scaling and capacity engineering
- On-demand versus always-on fleet configurations materially change cost and user experience (startup latency).
Licensing (especially Microsoft and third-party applications)
- Windows remote-desktop/server licensing-related fees apply for Windows-based streaming; Microsoft application licensing can be a compliance risk if not correctly managed.
Observability and support operations
- CloudWatch metrics, permissions, and incident response processes can be non-trivial to implement and maintain.

Key competitors / direct alternatives (4–6)

Microsoft Azure Virtual Desktop (AVD)
Citrix DaaS (Citrix Virtual Apps and Desktops as a service)
VMware Horizon / Horizon Cloud
Windows 365 Cloud PC (adjacent alternative; full desktop rather than app streaming)
Kasm Workspaces (containerized workspaces / application delivery)
Traditional RDS/RemoteApp on Windows Server (self-managed)