Permissions and Privileges (AWS)

GigaVUE-FM requires access to AWS EC2 APIs to deploy the solution. IAM allows you to control the actions that GigaVUE-FM can take on your EC2 resources.

To configure the components, you must first enable the permissions listed below and attach the policies to an IAM role. You must then, attach the IAM role to the GigaVUE-FM instance running in AWS. If the GigaVUE-FM is running outside the AWS, then you must use the access keys and secret keys.

The following topics lists the minimum permissions that are required for traffic acquisition:

• GigaVUE-FM Instance Multi Account Support Using Amazon STS

• Example: Traffic Acquisition using the UCT-V

• Example: Traffic Acquisition using the Customer Orchestrated Source

• Example: Traffic Acquisition using the Customer Orchestrated Source with GwLB

• Example: Traffic Acquisition using the Customer Orchestrated Source with NwLB

• Example: Traffic Acquisition using VPC Mirroring

• Example: Traffic Acquisition using VPC Mirroring with Network Load Balancer

• Example: Traffic Acquisition using VPC Mirroring and GwLB