Outbound network access requirements for self-hosted Instana deployments
Before you deploy Instana backend in a self-hosted environment, set the firewall and proxy properly to allow the following outbound network access:
Instana backend components are provided by using remote software repositories and a remote registry that contains Docker images. For billing purposes, the submission of usage information to the central Instana Accounting System is required. What follows is a list of all remote systems that need to be reachable during installation and operation. The Instana console uses your sales and agent keys as login credentials.
| Port | Protocol | Authentication | Repository or URL | Required by | Comments |
|---|---|---|---|---|---|
| 443 | TCP | Yes | https://artifact-public.instana.io |
- Standard Edition - Custom Edition - Classic Edition |
Repository for kubectl plug-in, package files for the Classic Edition, Instana backend images, new sensors, updates to existing sensors, and agent updates for dynamic agents . |
| 443 | TCP | Yes | https://instana.io |
- Standard Edition - Custom Edition - Classic Edition |
Required for license download and to send Instana usage information to Instana's accounting backend at https://instana.io/portal/statistics/usage. |
| 443 | TCP | No | https://icr.io/instana |
- Standard Edition - Custom Edition - Classic Edition |
Repository for agent images from the IBM Cloud Container Registry (ICR). |
| 443 | TCP | Yes | https://packages.instana.io |
- Standard Edition - Custom Edition - Classic Edition |
Repository for packages to install the host agent. |
| 443 | TCP | Yes | https://setup.instana.io |
- Standard Edition - Custom Edition - Classic Edition |
Repository for the script to install the host agent. |
| 443 | TCP | Yes | https://agents.instana.io/helm |
- Standard Edition - Custom Edition - Classic Edition |
Repository for Synthetic PoP Helm packages, autotrace-webhook, and agent Helm packages. |