AWS Elastic Load Balancing

You can use a load balancer to uniformly distribute the traffic from AWS target VMs to GigaVUE V Series Nodes. The load balancer distributes the traffic to the GigaVUE V Series Nodes and the auto-scaling group deploys the GigaVUE V Series Nodes based on the traffic.

The following load balancers are supported:

Network Load Balancer

The AWS Network Load Balancer (NLB) uses NLB targets to distribute traffic across multiple resources such as EC2 instances, containers, or IP addresses within a VPC. It operates at the transport layer (Layer 4) and supports protocols like TCP, UDP, and TLS for low-latency, high-throughput applications. With the NLB, you can forward traffic from any subnet to targets across multiple Availability Zones for better fault tolerance and scalability. It allows you to monitor and manage network traffic across your VPC, ensuring high availability and performance.

In this diagram, GigaVUE Cloud Suite deploys fabric components in a centralized VPC. External AWS accounts send mirrored traffic from their target VMs to an external Network Load Balancer. GigaVUE‑FM configures traffic mirroring on these targets and forwards the mirrored traffic to the NLB. The load balancer then distributes the traffic to the GigaVUE V Series Nodes.

An Auto Scaling group monitors traffic levels and, through RESTful API integration with GigaVUE‑FM, automatically adds or removes V Series Nodes based on pre-defined thresholds.

Components Required:

  • GigaVUE‑FM (Fabric Manager)

  • GigaVUE V Series Nodes

  • AWS Network Load Balancer (uniformly distributes traffic from AWS target VMs to GigaVUE V Series Nodes)

For detailed setup instructions, refer to Configure Network Load Balancer in AWS.

Gateway Load Balancer

The gateway load balancer (GWLB) uses the gateway load balancer endpoints to distribute the traffic across the endpoints. It is a VPC endpoint that provides connectivity between virtual machines. With GWLB Endpoint as a target, you can forward mirrored traffic from any subnet. You can monitor network traffic across multiple VPCs and accounts, with centralized traffic inspection in a single VPC across the entire organization.

In the architecture, you can see the deployment of GigaVUE Cloud Suite for AWS environments that have GWLB implementation for security appliances, such as firewalls. In such deployments, the applications and your appliances are in different VPCs. The workload VPC is configured with the Gateway load balancer endpoint while the service VPC is configured with the Gateway load balancer. Gigamon deployed VPC has the solution components, such asNodes, and the OOB tools, which consume the mirrored and decapsulated data.

In this deployment model, your workloads reside in one VPC, and the security appliances (such as firewalls) reside in another (called a service VPC). The workload VPC includes a GWLB Endpoint, while the service VPC hosts the actual GWLB and the GigaVUE Cloud Suite components, including:

  • GigaVUE-FM

  • GigaVUE V Series Nodes

  • Out-of-band (OOB) tools that analyze mirrored and decapsulated traffic

This design allows scalable, centralized inspection across your cloud environment.

For more details, refer to Configure a Gateway Load Balancer in AWS.