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, traffic can be forwarded 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.
The design shows how to deploy GigaVUE Cloud Suite fabric components in a centralized VPC where the target VMs of multiple AWS accounts are deployed behind an external AWS network load balancer. GigaVUE-FM creates Traffic Mirroring on the target VMs to mirror and forward the traffic to the load balancer. The load balancer then deploys or deletes additional GigaVUE V Series Nodes and distributes the traffic among them to aggregate, filter, and forward the traffic to the tools over the tunnel endpoint. In AWS, the Auto Scaling group monitors the load among all the GigaVUE V Series Nodes and adds or removes them via RESTful API integration with the GigaVUE-FM when the traffic load crosses or drops below a pre-defined threshold.
A typical AWS deployment to support the external load balancer requires the following components:
- GigaVUE-FM (GigaVUE-FM fabric manager)
- GigaVUE V Series Node
- AWS Network Load Balancer (uniformly distributes traffic from AWS target VMs to GigaVUE V Series Nodes)
Refer Configure Network Load Balancer in AWS section for more details on how to configure a Network Load Balancer.
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, mirrored traffic can be forwarded 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 as GigaVUE-FM, GigaVUE V Series Nodes, and the OOB tools, which consume the mirrored and decapsulated data.
Refer Configure a Gateway Load Balancer in AWS section for more details on how to configure Gateway Load Balancer.