Different parts of the GovWorx application suite need different special considerations when setting up the network.
On Prem Data Agent
The following hosts, protocols and ports are needed for the data agent inside of your network to speak to the secure AWS GovCloud.
This is also outlined in the Data Agent Installation Checklist
Protocol | Host | Port | Purpose |
https | app.govworx.net | 443 | Main application |
https | realtime.govworx.net (if using Assist) | 443 | CommsCoach Assist |
https | govworx-cad-incidents.s3-fips.us-gov-west-1.amazonaws.com | 443 | CAD Uploads |
https | gw-coach-temp-upload-storage.s3-fips.us-gov-west-1.amazonaws.com | 443 | Audio Uploads |
https | gw-data-agent.s3.us-gov-west-1.amazonaws.com | 443 | Data Agent Installer |
https | http-intake.logs.us5.datadoghq.com | 443 | Agent Telemetry |
https | api.us5.datadoghq.com | 443 | Agent Telemetry |
Web Applications
Protocol | Host | Port | Purpose |
https | app.govworx.net | 443 | Main application |
https | portal.govworx.net | 443 | Main Application end user portal |
https | simulate.govworx.net | 443 | Simulator |
https | livekit.govworx.net | 443 | Simulator |
https | turn.govworx.net | 3478, 60001-65001 | Simulator |
https | realtime.govworx.net | 443 | Assist |
https | speech.microsoft.com | 443 | Scripted caller accessibility |
https | api.openai.com | 443 | Smart Caller backend for API calls |
UDP | realtime.api.openai.com | 443 | Primary WebRTC media transport for audio streams in Smart Caller |