Points to Note for GigaVUE Cloud Suite for AWS

Considerations when deploying GigaVUE Cloud Suite:

• We recommend to deploy the GigaVUE-FM on the AWS to manage AWS workload.
• If the GigaVUE-FM is deployed outside of the AWS, then the GigaVUE-FM encrypts and stores the access key and the secret key in its database.
• Always attach an IAM role to the instance running GigaVUE-FM in AWS to connect it to your AWS account.
• If you are launching the GigaVUE-FM instance from the AWS Marketplace, you need to have only the IAM roles.
• Deployment of GigaVUE fabric components through a third-party orchestrator is supported on Linux and Windows platforms.
• Fragmentation in the network should be avoided from UCT-V to GigaVUE V Series Node and from GigaVUE V Series Node to tool by setting appropriate MTU for the interfaces. If the tool VM MTU is less than that of GigaVUE V Series Node, then GigaVUE V Series Node fragments the packets. This results in packet loss as ENA (Elastic Network Adapter) of AWS drops all fragments over 200 packet per second.
• Set appropriate MTU for the interfaces to avoid fragmentation in the network from UCT-V to GigaVUE V Series Node and from GigaVUE V Series Node to tool.
• If the tool VM MTU is less than that of GigaVUE V Series Node, then GigaVUE V Series Node fragments the packets. Fragment packets are reordered on arrival at the V-series node.
• When GigaVUE-FM and GigaVUE V Series Nodes are deployed on different cloud platforms, then you must add the GigaVUE-FM public IP address to the Data Notification Interface as the Target Address in the Event Notifications page. For details, refer to the Configuration Settings section .
• When GigaVUE-FM and the workload VMs requiring monitoring are in different AWS accounts (cross-account) and AWS Traffic Mirroring is the Traffic Acquisition Method, you must either configure a Network Load Balancer or Gateway Load Balancer. For details, refer to Configure AWS Elastic Load Balancing.