Skip to main content

Load Balancing

VPC load balancing distributes traffic across backend VMs within the VPC. NetActuate supports two types of load balancers, plus reusable backend groups.

Navigate to Load Balancing within your VPC. The page has three tabs: HTTPS Load Balancers, Network Load Balancers, and Backend Groups.

HTTPS Load Balancers (Layer 7)​

HTTPS load balancers operate at the application layer with SSL termination, domain-based routing, and HTTP-level health checks.

SSL Certificates​

Before creating an HTTPS load balancer, you may want to upload SSL certificates. On the HTTPS Load Balancers tab, scroll to the SSL Certificates section and click + Add:

  1. Enter a Name and Description.
  2. Upload the Certificate file.
  3. Upload the Private key.
  4. Click Submit.

Uploaded certificates are available for selection when configuring domain forwarding rules on your HTTPS load balancers.

Creating an HTTPS Load Balancer​

Click + Add under HTTPS Load Balancers. You will be prompted to choose an add mode:

  • Wizard — a step-by-step guided flow (recommended)
  • Quick Add — a single-screen form for experienced users

You can check Remember my choice to skip this prompt in the future.

Step 1: Frontend Configuration​

  • Name — a friendly name for the load balancer
  • Source IP — select a floating IP or the gateway address
  • Port — the port to listen on (e.g., 443)
  • Algorithm — Least Connections or Round Robin
  • Description — optional
  • Sticky Sessions — enable or disable session persistence

Step 2: Health Checks (Optional)​

  • Active health check — when enabled, configure:
    • Interval (seconds) — how often to check
    • Delay (seconds) — initial delay before checks begin
    • Timeout (seconds) — how long to wait for a response
    • Retries — number of failed checks before marking a backend as down
    • Path — the URL path to check (expects HTTP 200 OK)
  • Passive health check — enable to monitor backends passively based on response behavior

Step 3: Domain Forwarding Rules​

Domain forwarding rules define how traffic is routed to your domains with SSL and redirect options.

For each domain:

  1. Select an SSL certificate — either one you uploaded or Auto SSL (Let's Encrypt).
  2. Enable or disable SSL and HTTPS redirect.
  3. Enter the Domain name and optional Path.
  4. Click Add.

You can add multiple domains to a single load balancer.

Step 4: Backends​

  • Backend port — the port on backend servers (must be the same for all servers in the group)
  • Backend SSL — disabled (HTTP to backend) or enabled (HTTPS to backend)
  • Template — optionally select a previously saved backend group template

For each backend server, enter a Name and Host (internal IP). Add as many backend servers as needed.

You can Save as new template to reuse this backend group across other load balancers.

Step 5: Review and Launch​

The review screen shows:

  • Frontend details (name, IP, port, algorithm, sticky sessions)
  • Health check configuration
  • Number of domain forwarding rules
  • Backend port, SSL setting, and number of hosts

Click Add Load Balancer to create it.

HTTPS Load Balancer Dashboard​

Click into an existing HTTPS load balancer to view:

  • Backend health — number of online nodes
  • Nodes — total backend node count
  • Network transfer — total traffic through the load balancer
  • Requests — total request count
  • Average uptime — backend availability percentage
  • Network transfer by node — per-node traffic breakdown
  • Requests by HTTP method — GET, POST, etc.
  • Requests by HTTP status — 200, 404, 500, etc.
  • Requests per second — current throughput
  • Backend uptime — detailed uptime history

Use the time-range filters in the top right to adjust the dashboard view. Click the gear icon in the top right to reconfigure the load balancer settings or backend groups.

Network Load Balancers (Layer 4)​

Network load balancers operate at the transport layer, forwarding TCP and UDP traffic to backend servers.

Creating a Network Load Balancer​

Click + Add under Network Load Balancers. Choose Wizard or Quick Add mode.

Step 1: Frontend Configuration​

  • Name — a friendly name
  • IP Version — IPv4 or IPv6
  • Floating IP — select the public IP for this load balancer
  • Algorithm — Least Connections or Round Robin
  • Description — optional

Step 2: Health Checks (Optional)​

  • Method — Ping, TCP, or UDP
  • Interval (seconds), Delay (seconds), Timeout (seconds), Retries

Step 3: Forwarding Rules​

Define how traffic is routed to backend servers:

  1. Select the Protocol — TCP or UDP.
  2. Enter the Port to listen on.
  3. Enter the Target port on backend servers.

For example, forward all TCP traffic on port 80 to target port 80 on the backends.

Step 4: Backends​

Select a previously saved template group or enter servers manually:

  • Name — backend server name
  • IP address — internal IP of the backend VM

Optionally save the group as a template for reuse.

Step 5: Review and Launch​

Review the frontend details (name, IP version, IP, algorithm), health check configuration, and backend host count. Click Add Load Balancer to create it.

Network Load Balancer Dashboard​

Click into an existing network load balancer to view:

  • Backend health — number of online nodes
  • Total traffic — aggregate traffic volume
  • Total connections — connection count
  • Average uptime — backend availability
  • Connections per second — current throughput
  • Network bandwidth — bandwidth utilization
  • Backend uptime — detailed uptime history

Use the time-range filters in the top right to adjust the view. Click the gear icon to reconfigure or add new resources.

Backend Groups​

The Backend Groups tab provides a central view of all backend server groups. Groups created through the HTTPS or network load balancer wizards are also available here. Backend groups can be shared across both HTTPS and network load balancers.

Templates are useful when you have standard server groups (e.g., web servers, application servers) that are referenced by multiple load balancers. Updating a template updates it everywhere it is used.

Next Steps​

  • NAT Rules — configure port forwarding for services not behind a load balancer
  • Firewall — control which traffic reaches the VPC
  • Gateway — manage floating IPs used by load balancers

Need Help?​

Contact support@netactuate.com or open a support ticket from the portal.