Private Network Connectivity

Connect Harness Cloud VMs to private resources, and control what these VMs can reach — without giving up the operational simplicity of Harness-hosted infrastructure.

This section covers two related but distinct needs:

Private connectivity - letting a Harness Cloud VM reach resources that live inside your network (a private Git server, an internal artifact registry, an internal API, an on-prem database). Egress control - restricting what your Harness Cloud VM is allowed to talk to on the way out.

Private connectivity

When a Harness Cloud VM runs a workload, you may need to access internal resources that are not publicly accessible. Harness Cloud VMs are used by Continuous Integration and by other modules, such as Infrastructure as Code Management (IaCM). Examples include:

• Internal artifact repositories

• Private source code management systems (SCMs)

• Internal APIs and services

• On-premises databases

Refer the following subsections for Private Connectivity options on Harness Cloud

Cloud Private ConnectivityPrivateLink for Harness CloudVPN for Harness CloudIP allowlisting

Need help?

• Contact Harness Support for guidance on choosing the right solution for your requirements