Skip to main content

Private network connectivity options for Harness Cloud

When running builds on Harness Cloud, you may need to access internal resources that are not publicly accessible, such as:

  • Internal artifact repositories
  • Private source code management systems (SCMs)
  • Internal APIs and services
  • On-premises databases

Connectivity options​

Harness supports multiple approaches to enable communication between Harness Cloud infrastructure and your private network:

  1. IP allowlisting
  2. Private network connectivity through supported cloud provider solutions: AWS PrivateLink or GCP Private Service Connect.

IP allowlisting​

Your networking or security team can allowlist the IP ranges used by Harness Cloud to permit traffic from Harness-managed build infrastructure to your private resources.

How it works​

  1. Retrieve the current Harness Cloud IP ranges
  2. Configure your firewall or security groups to allow traffic from these IP addresses
  3. Ensure proper access controls are in place for your private resources

When to use IP allowlisting​

Use IP allowlisting when:

  • Your security policy permits allowlisting external IP ranges
  • You need a straightforward connectivity solution without additional client deployment
  • Your resources are accessible via standard firewall rules
  • You want minimal setup and configuration overhead

Getting Harness Cloud IP addresses​

To retrieve allowlisted IPs for Harness Cloud via API, see Retrieve allowlisted IPs for Hosted CI via API.

For comprehensive information about IP allowlisting or to request the current IP ranges, visit the Allowlist Harness domains and IPs documentation or contact Harness Support.

Private network connectivity (Enterprise)​

For enterprise customers with strict compliance and security requirements, cloud provider private networking solutions offer enhanced security without exposing traffic to the public internet.

Benefits​

  • Reliable high-bandwidth connectivity - Ensures stable, performant transfer of large artifacts, caches, and build outputs at enterprise scale
  • No internet exposure - Traffic stays within your cloud provider's private network backbone
  • Granular access control - Restrict access to specific VPCs, subnets, or security principals
  • Simplified compliance - Meets internal-only networking requirements for regulated industries
  • Easy to configure - No VPNs or complex firewall rules required

Available solutions​

AWS PrivateLink Provides private connectivity between VPCs, AWS services, and your on-premises networks without exposing traffic to the public internet.

For detailed setup instructions, see the AWS PrivateLink Documentation.

GCP Private Service Connect Allows you to privately connect your VPC networks to Google-managed services and services hosted in other VPC networks.

For detailed setup instructions, see the GCP Private Service Connect Documentation.

note

For questions about integrating these solutions with Harness, contact Harness Support.

Need help?​

For assistance with private network connectivity options: