Client-side only
No data sent
2026 Migration Ready
READY
VDI & Workstation Diagnostics — 2026 Edition
Amazon Connect
VDI Compatibility Tester
Instantly verify your Citrix, AWS WorkSpaces, Omnissa, RDP, or physical workstation meets every Amazon Connect prerequisite — including 2026 sign-in migration readiness, VDIPlatform audio redirection, Audio Enhancement eligibility, WebRTC ICE types, NAT detection, and full endpoint reachability.
Auto-detects Citrix, WorkSpaces, Omnissa & RDP environments
VDIPlatform audio redirection URL generator
New 2026 sign-in endpoints (*.signin.aws) reachability
Audio Enhancement eligibility (Noise Suppression / Voice Isolation)
ICE candidate types: host / srflx / relay + NAT type estimate
Headset wired vs Bluetooth detection
Browser engine, version & WebRTC API coverage
AWS region endpoint reachability + dualstack IPv6
// COMPATIBILITY SCORE
—
/100
Compatibility Check
Initializing checks…
Summary
Detailed Results
Network & Endpoint Reachability
Endpoint Latency & Reachability
| Endpoint | Purpose | Protocol | Latency / Status | Required | Result |
|---|
Amazon Connect Requirements Checklist
| Requirement | Category | Expected | Detected | Status |
|---|
// COMPATIBILITY REPORT — EXPORTABLE TEXT
Amazon Connect VDI Compatibility Guide 2026 — Citrix, WorkSpaces & Omnissa
Amazon Connect's Contact Control Panel (CCP) runs entirely in the browser and uses WebRTC for real-time voice and omnichannel contacts. In 2026, this means your Citrix, AWS WorkSpaces, Omnissa Horizon, or RDP environment must satisfy strict browser, network, and hardware prerequisites — plus new 2026 sign-in endpoint requirements — before agents can take calls. This free tool auto-detects your VDI platform, generates the correct VDIPlatform audio redirection URL, checks all new sign-in domains (*.signin.aws), tests Audio Enhancement eligibility (noise suppression and voice isolation), and validates ICE candidate types, NAT detection, and every required AWS endpoint — all from your browser, nothing uploaded.
Does Amazon Connect work on Citrix, AWS WorkSpaces, and Omnissa VDI in 2026?
Yes, with audio optimization enabled. Amazon Connect supports Citrix, Amazon WorkSpaces (PCoIP and DCV), and Omnissa Horizon through WebRTC audio redirection using the
VDIPlatform query parameter. Without optimization, audio processes on the VDI server adding 50–200ms latency. To enable: append ?VDIPlatform=CITRIX, ?VDIPlatform=AWS_WORKSPACE, or ?VDIPlatform=OMNISSA to the agent workspace URL. Citrix requires Workspace App 2305 or later. WorkSpaces requires a custom CCP built with the Connect Streams API.
What is the Amazon Connect 2026 sign-in migration and how does it affect VDI agents?
Amazon Connect is migrating all instances to a new sign-in experience using
*.signin.aws domains. The migration timeline: April 7 2026 (new instances default), July 7 2026 (auto-migration for eligible instances), October 7 2026 (all remaining forced). VDI environments are especially at risk because their firewall/proxy configurations are often more restrictive. The new sign-in also requires *.s3.dualstack.{region}.amazonaws.com (IPv6/dualstack S3) and *.threat-mitigation.aws.amazon.com. Run this tester to check if your VDI network allows all required domains.
What browser does Amazon Connect require in VDI environments?
Amazon Connect officially supports the latest 3 major versions of Google Chrome and Mozilla Firefox. Microsoft Edge (Chromium) is also supported. Chrome is strongly recommended for VDI, especially when using Audio Enhancement (noise suppression and voice isolation modes launched February 2026) which requires Chrome or Edge. Safari has partial WebRTC support and is not recommended. The browser must run inside the VDI session (or redirect audio to the local machine) with access to the microphone device via USB or audio passthrough.
What is Amazon Connect Audio Enhancement and what are the VDI requirements?
Amazon Connect Audio Enhancement (launched February 2026) provides real-time noise suppression and voice isolation for agents. In VDI environments, Audio Enhancement must be paired with VDIPlatform audio optimization — without audio redirection to the local device, the VDI server processes audio and Audio Enhancement has no effect. Requirements: minimum 4-core CPU or 4 vCPU (on the local endpoint for Citrix/WorkSpaces), wired headset for Voice Isolation mode (Noise Suppression works with Bluetooth). Configure via Connect Admin Console under User Management.
What network ports does Amazon Connect require in VDI environments in 2026?
Amazon Connect requires TCP 443 outbound to:
*.my.connect.aws, *.transport.connect.{region}.amazonaws.com, *.telemetry.connect.{region}.amazonaws.com, participant.connect.{region}.amazonaws.com, *.cloudfront.net, *.signin.aws (new 2026 sign-in), and *.threat-mitigation.aws.amazon.com. UDP 3478 outbound is required to TurnNlb-*.elb.{region}.amazonaws.com for STUN/TURN media. For VDI with audio optimization, the local endpoint (not the VDI server) must have UDP 3478 access. Stateless firewalls also need ephemeral UDP ports 32768–65535 for RTP return traffic.
What causes no audio or one-way audio in Amazon Connect on Citrix or VDI?
The most common VDI audio causes are: (1) VDIPlatform parameter not configured — audio processes on the VDI server with high latency; (2) ICE failure — UDP 3478 blocked at the VDI host or local network; (3) Symmetric NAT — all traffic must relay through TURN, requires
TurnNlb-*.elb.{region}.amazonaws.com:3478 UDP open; (4) Citrix HDX RealTime not configured — browser inside VDI cannot access audio device; (5) Microphone permission denied inside the virtual browser. Run this tester to identify which of the five causes applies — it checks all of them automatically.
How do I set up VDIPlatform for Citrix audio optimization in Amazon Connect?
To enable Citrix audio optimization for Amazon Connect, append
?VDIPlatform=CITRIX to the agent workspace URL: https://your-instance.my.connect.aws/agent-app-v2?VDIPlatform=CITRIX. Bookmark this URL for all agents. For SSO users, add VDIPlatform=CITRIX to the relay state URL. Requirements: Citrix Workspace App (CWA) 2305 or later on the local client machine, Citrix Virtual Delivery Agent (VDA) 2109 LTSR or later, and the local machine must have UDP 3478 access to Amazon Connect TURN servers. The Citrix Unified Communications SDK handles WebRTC redirection automatically once the parameter is set.
What network latency is acceptable for Amazon Connect in VDI?
Amazon Connect recommends under 150ms round-trip time to the AWS region, under 30ms jitter, and under 1% packet loss for good call quality. In VDI environments without audio optimization, the media path is: agent headset → VDI host → network → AWS TURN server — each hop adds latency. Full-tunnel VPN typically adds 50–200ms. With VDIPlatform audio optimization properly configured, the path shortens to: local headset → local network → AWS TURN, which behaves identically to a physical workstation. Always use split-tunnel VPN when agents run Connect from VDI environments.
More Free Online Tools
Simple tools. Surgical fixes. Zero friction.
Amazon Connect CCP Log Parser
Parse Amazon Connect CCP logs into structured, searchable diagnostics.
OpenAmazon Connect Agent Workstation Validator
Pre-flight check for Amazon Connect softphone agents.
OpenAmazon Connect Pricing Calculator
Instantly estimate monthly AWS Connect costs — voice, chat, email, campaigns, telephony & more.
OpenConnect CloudWatch Log Analyzer
Drop any Amazon Connect CloudWatch log and get a rich visual breakdown.
Open