Network Requirements
This page lists the inbound ports AMS.Eclipse opens on the host machine and the outbound hosts the running system contacts. It is intended for IT and network teams who need to configure firewall rules or proxy allowlists.
Inbound Ports
The AMS.Eclipse installer creates four Windows Firewall rules. Only two of these ports actually need to be reachable from the network — the other two are listed for completeness, but in customer deployments they are accessed only from the local machine.
| Port | Protocol | Service | Reach | Notes |
|---|---|---|---|---|
| 8080 | TCP | Eclipse Server | LAN | Main API. Eclipse.UI, Wallboard, Warehouse, Machine Buddy and the Agent all connect here. |
| 58080 | TCP | Eclipse Supervisor | LAN (admin only) | Management interface. Restrict to an admin subnet if remote management is not required. |
| 8081 | TCP | Eclipse Agent | Localhost | Agent HTTP API. The installer opens a firewall rule, but the Agent is co-located with the Server and is reached over loopback. |
| 58085 | TCP | RavenDB | Localhost | Document database. The installer opens a firewall rule, but in customer deployments RavenDB is only accessed locally by the Eclipse Server. |
The installer registers HTTP URL ACL reservations for all four ports so the services can listen without requiring administrator privileges at runtime. See Installation for details.
Outbound Hosts
For sites with restricted internet access, allowlist the following hosts on outbound HTTPS (TCP port 443). All connections are HTTPS unless noted.
Required at all times
| Host | Purpose |
|---|---|
portal.amscontrols.com | License validation, status reporting, and software-build lookup. |
licenses.ravendb.net | RavenDB ISV license validation. |
edge.eclipsepro.app | Cloud-relayed notifications and edge processing. |
Required during install and upgrade
| Host | Purpose |
|---|---|
amscontrolsportal.blob.core.windows.net | Software release downloads. |
hibernatingrhinos.com | Downloads RavenDB engine binaries during initial install or version upgrade. |
api.nuget.org | Workload package metadata and downloads when the Supervisor installs or updates Eclipse workloads. |
Optional — cloud backup
When AMS-managed cloud backup is enabled for a Pro, the Supervisor uploads RavenDB and Eclipse Classic backups directly to Azure Blob Storage using a SAS token issued by the portal.
| Host | Purpose |
|---|---|
eclipseproedge.blob.core.windows.net | AMS-managed backup uploads. The Supervisor authenticates with a SAS token refreshed via portal.amscontrols.com; the container name is unique per Pro serial number. |
If the customer instead chooses to upload backups to their own Azure Storage account, allowlist that account's {name}.blob.core.windows.net host instead.
Optional — diagnostics and telemetry
These hosts are only contacted when the corresponding feature is enabled. They can be omitted from the allowlist if the feature is not used, at the cost of losing crash reports or self-service diagnostics.
| Host | Purpose | When active |
|---|---|---|
diagnostics.amscontrols.com | Receives diagnostic bundles and crash files for AMS support. | When a user uploads diagnostics. |
app.raygun.io | Exception and crash telemetry. | When the installer was built with a Raygun API key — this is the default for AMS-shipped builds. |
*.in.applicationinsights.azure.com*.livediagnostics.monitor.azure.com | OpenTelemetry export to Azure Monitor / Application Insights. | Only when an Azure Monitor connection string is configured at install time. |
Allowlist quick reference
All outbound traffic is HTTPS on TCP port 443.
# Always required
portal.amscontrols.com
amscontrolsportal.blob.core.windows.net
licenses.ravendb.net
edge.eclipsepro.app
# Install and upgrade
hibernatingrhinos.com
api.nuget.org
# Optional — cloud backup (when enabled)
eclipseproedge.blob.core.windows.net
# Optional — diagnostics and telemetry
diagnostics.amscontrols.com
app.raygun.io
*.in.applicationinsights.azure.com
*.livediagnostics.monitor.azure.com