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 key id and secret access keys. Refer to IAM roles for Amazon EC2 in the AWS Documentation for more details.

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

• GigaVUE-FM Instance Multi Account Support Using Amazon STS
• Minimum Permissions Required for Acquiring Traffic using the UCT-V
• Minimum Permissions Required for Acquiring Traffic using the Customer Orchestrated Source
• Minimum Permissions Required for Acquiring Traffic using the Customer Orchestrated Source with GwLB
• Minimum Permissions Required for Acquiring Traffic using the Customer Orchestrated Source with NwLB
• Minimum Permissions Required for Acquiring Traffic using Traffic Mirroring
• Minimum Permissions Required for Acquiring Traffic using Traffic Mirroring with Network Load Balancer
• Minimum Permissions Required for Acquiring Traffic using Traffic Mirroring and GwLB