Build Network Load Balancer backend set, listener, and health check configurations.
Last verified: May 2026
Build Network Load Balancer backend set, listener, and health check configurations for Layer 4 traffic.
Required Fields
compartmentIddisplayNamesubnetIdlistenersbackendSetsOutput will appear here...Build Network Load Balancer backend set, listener, and health check configurations. This tool helps OCI 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.
Your team is running a high-throughput TCP service (real-time data ingestion) currently behind a standard OCI Load Balancer. The builder shows: standard LB with 1 Gbps shape costs $200/month + processing fees; NLB at the same throughput costs ~$30/month. Migration plan: deploy NLB with TCP listener, update DNS to point clients to the NLB, retire the old LB after validation. Net savings: $170/month. NLB also delivers lower latency (closer to wire-speed) which improves p99 latency by ~10ms for the latency-sensitive workload.
Network Load Balancer (Layer 4) preserves source IP by default — critical for IP-based access control or geo-IP analytics. The Application Load Balancer (Layer 7) replaces source IP with the LB's IP unless you enable XFF headers and configure your app to trust them.
NLB is dramatically cheaper than the standard OCI Load Balancer for high-throughput TCP/UDP workloads. NLB charges per GB processed; standard LB charges flat for the bandwidth shape. For sustained high-throughput patterns, NLB cost-effectively scales.
Use IPv6 dual-stack on NLB for modern infrastructure. Configure both IPv4 and IPv6 listeners; the NLB handles the protocol bridging to backends. Future-proof your architecture without forcing application changes.
The builder constructs OCI Network Load Balancer configurations: NLB resource (compartment, VCN, subnet, public/private), listeners (port + protocol: TCP/UDP, optional TLS termination), backend sets (load balancing policy: 5-tuple-hash / 3-tuple-hash, health check config: TCP/HTTP probe with interval/timeout/threshold, backends: instance OCIDs or IP addresses with weights). Output is generated as oci nlb network-load-balancer commands and Terraform oci_network_load_balancer_network_load_balancer + oci_network_load_balancer_backend_set resources.
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.