Harness Cloud Network and Security
Choose how Harness Cloud reaches private resources, and how you control outbound traffic from Cloud VMs
When you run pipelines on Harness Cloud, those pipelines often need private resources that are not available on the public internet. Typical resources include internal artifact registries and private source control providers.
Harness Cloud VMs run these workloads for Continuous Integration and for other modules, such as Infrastructure as Code Management (IaCM). This page explains how a Cloud VM reaches those resources, and how you control what the VM can reach on the way out.
Private resource access
When a Harness Cloud VM runs a workload, you may need to access internal resources that are not publicly accessible. Access those resources without exposing them to the public internet. Enterprise builds often depend on internal artifact repositories, artifact registries, Private source code management systems (SCMs), On-premises databases, and Internal APIs and services.
IP allowlisting is one option. Cloud Private Connectivity, PrivateLink, and VPN are separate alternatives. Cloud Private Connectivity is the recommended option for enterprise use.
IP allowlisting
Use IP allowlisting when the private resources are reachable through public endpoints and you permit access from Harness Cloud IP ranges.
Allowlist the published Harness Cloud IP ranges on your firewall or security group. Harness Cloud can then reach the resource from those addresses.
IP allowlistingCloud Private Connectivity
Use Cloud Private Connectivity when builds need secure access to private resources without public exposure, IP allowlisting, or a VPN client in the pipeline.
Cloud Private Connectivity connects a Harness Cloud VM to your private network. The resource stays off the public internet. You can move more CI workloads to managed infrastructure without giving up network control.
Cloud Private ConnectivityAWS PrivateLink or Google Cloud Private Service Connect
Use PrivateLink when you need cloud-native private connectivity to private services in the same cloud provider. Harness Cloud supports AWS PrivateLink and Google Cloud Private Service Connect.
PrivateLink for Harness CloudVPN
Use a VPN client when you can establish private network connectivity by running OpenVPN or WireGuard directly in the CI pipeline.
VPN for Harness CloudEgress control
Egress control is separate from private connectivity. Use it to restrict what a Harness Cloud VM is allowed to reach on the way out.
Define outbound network policies for Harness Cloud in one place. Those policies restrict traffic to approved destinations, block unauthorized resources and artifacts, and give you visibility for security, compliance, and auditing.
Egress Controls for Harness CloudNeed help
Go to Harness Support to get guidance on the right option for your requirements.
Last updated
Was this helpful?