Build NEG configurations for serverless, internet, and hybrid connectivity endpoints.
Last verified: May 2026
Build NEG configurations for serverless, internet, and hybrid connectivity endpoints with load balancer integration.
Required Fields
namenetworkEndpointTyperegionOutput will appear here...Your team has Cloud Run services serving traffic via the *.run.app default URLs. You need: custom domain, WAF (Cloud Armor), CDN caching for static API responses. The builder generates a serverless NEG pointing at the Cloud Run service, attached to a global HTTPS load balancer with managed certificate, Cloud Armor policy, and Cloud CDN enabled. Result: production-grade frontend with caching + WAF + custom domain, all sitting in front of your serverless backend. Total config time: 1 hour vs the 1-day estimate for the same infrastructure built piece-by-piece.
Build NEG configurations for serverless, internet, and hybrid connectivity endpoints. This tool helps GCP engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
The builder constructs Network Endpoint Group configurations: NEG resource (network_endpoint_type: GCE_VM_IP_PORT / SERVERLESS / INTERNET_FQDN_PORT / NON_GCP_PRIVATE_IP_PORT, region or zone, network and subnet for zonal NEGs, app_engine/cloud_function/cloud_run binding for serverless NEGs, default_port). Output is generated as gcloud compute network-endpoint-groups commands and Terraform google_compute_network_endpoint_group + google_compute_region_network_endpoint_group resources.
NEG types determine load balancer integration: Zonal NEGs (instance + port), Internet NEGs (FQDN external endpoints), Serverless NEGs (Cloud Run/Functions/App Engine), Hybrid NEGs (on-prem endpoints). Match NEG type to your backend — the load balancer config differs significantly.
Serverless NEGs are the cleanest way to put Cloud Run / Cloud Functions behind a global HTTP load balancer with custom domain + SSL + WAF (Cloud Armor). Without serverless NEGs, you're stuck with the *.run.app default URL.
Internet NEGs let you load balance to external endpoints (third-party APIs, CDN origins). Combined with Cloud CDN, you can cache external content as if it were on GCP — useful for legacy migrations where some backends still run elsewhere.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.