--- title: "Components of Trellix vIPS for public cloud" slug: "components-of-trellix-vips-for-public-cloud-2" tags: ["Product Usage", "vIPS 11.1x", "vIPS"] updated: 2026-09-11T20:53:29Z published: 2026-09-11T20:53:29Z canonical: "docs.trellix.com/components-of-trellix-vips-for-public-cloud-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Components of Trellix vIPS for public cloud In order to deploy vIPS in public cloud environment, you require the following components: ****Trellix Intrusion Prevention System Manager**** software has a web-based user interface for configuring and managing Trellix vIPS. Users connect to the Manager server from a supported client using a supported browser. The Manager functions are configured and managed through a GUI application which includes complementary interfaces for alerts, system status, system configuration, report generation, and fault management. The Manager is deployed directly in the cloud environment. It acts as a single pane of glass to manage Sensors deployed in the cloud. ****Virtual IPS Sensor**** is Trellix's next-generation vIPS product. ****Internal/External Controller**** is the central enforcement point for all network and security policies. It is a centralized manager that controls all vIPS Probes installed on the instances in the cloud environment. It can be configured in the IPS Manager. - ****vIPS Cluster**** — It is a collection of Virtual IPS Sensors that inspect traffic directed to them by the instances. - ****vIPS Protected group**** — It is a collection of instances that redirect their traffic to a vIPS Cluster for inspection. ****vIPS Probes**** are installed on all instances that need to be secured by the Virtual IPS Sensor. The vIPS Probe intercepts all traffic before it reaches its destination and then forwards it to the Virtual IPS Sensor for scanning. > [!NOTE] > Note > > Controller and probe are not needed in case you are using a Gateway Load Balancer (GWLB) based solution.