--- title: "Auto-scale Virtual IPS Sensors" slug: "auto-scale-virtual-ips-sensors-1" tags: ["Product Usage", "vIPS 11.1x", "vIPS"] updated: 2026-09-11T20:53:15Z published: 2026-09-11T20:53:15Z canonical: "docs.trellix.com/auto-scale-virtual-ips-sensors-1" --- > ## 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. # Auto-scale Virtual IPS Sensors To launch auto-scaling for Virtual IPS Sensors from Azure, perform the following steps: 1. Click **All services** and then **Virtual machine scale set** under **COMPUTE** section. The **Virtual machine scale set** blade opens. 2. Click **+ Add**. The **Create a virtual machine scale set** window opens with the **Basics** tab. 3. On the **Basics** tab, enter the following details: | Option | Definition | | --- | --- | | **Project details** | **Subscription** - The subscription linked with your Azure account is selected by default. If you have multiple subscription accounts, select the subscription account in which you would like to launch the Virtual IPS Sensor scale set. **Resource group** - **Create new** - You can create a new resource group to be protected. - **Select existing** - Select the resource group to be protected. | | **Scale set details** | **Virtual machine scale ser name** - Type a name for the Virtual IPS Sensor scale set. **Region** - Select the region where the Virtual IPS Sensor must be created. **Availability zone** - [Optional] Select the availability zone for providing high availability to the Virtual IPS Sensor. | | **Instance details** | **Image** - Select the Virtual IPS Sensor image to be deployed as a virtual machine scale set. **Size** - Select the size of the Virtual IPS Sensor VM. | | **Administrator account** | **Authentication type** - Select **SSH** authentication type. > [!NOTE] > Note > > Only the SSH Public Key authentication type is supported for Sensors. **Username** - Enter the user name that must be used for the Virtual IPS Sensor virtual machine. **SSH public key store** - Select the Use existing public key option. > [!NOTE] > Note > > The private key file for the SSH public key must be in .pem format. > [!NOTE] > Note > > The Virtual IPS Sensor cannot validate the SSH key pair generated in the Azure portal. | > [!NOTE] > Note > > Azure validates the information you enter and a green tick appears against the fields where you enter details. 4. Click **Next: Disks >**. The **Disks** tab opens. Enter the following details: | Option | Definition | | --- | --- | | **Disk options** | **OS disk type** - The Premium SSD type is selected by default. Trellix recommends you use Premium SSD disk type for Virtual IPS Sensors for improved performance. | | **Data disks** | You can attach a new disk or an existing disk for your virtual machine. | | **Advanced** | **Use managed disks** - Select **Yes** for Azure to manage the disk availability automatically. | 5. Click **Next: Networking >**. The **Networking** tab opens. Enter the following details: | Option | Definition | | --- | --- | | **Virtual network** | Select the required virtual network. | | **Network interafce** | **Create new nic** - You can create a new network interface for the virtual machine. Or, Select the existing new network interface for the virtual machine. | 6. Click **Next: Scaling >**. The **Scaling** tab opens. Enter the following details: | Option | Definition | | --- | --- | | **Instance** | **Intial Instance Count** — Enter the number of active instances available in the virtual machine scale set at a time. | | **Scaling** | **Scaling policy** — Trellix recommends you select this option to scale the Sensor set based on any capacity or schedule. **Minimum number of VMs** — Enter the minimum number of Sensors to be available in the scale set. **Maximum number of VMs** — Enter the maximum number of Sensors to be available in the scale set. | | **Scale out** | **CPU threshold (%)** — Enter the CPU percentage threshold to start the **Scale out** for autoscale set. **Duration in minutes** — Enter the duration for which the samples are collected for the metric when auto scaling. **Number of VMs to increase by** — Enter the number of Sensors to be deployed newly when the autoscale reaches **Scale out** condition. | | **Scale in** | **CPU threshold (%)** — Enter the CPU percentage threshold to start the **Scale in** for autoscale set. **Number of VMs to decrease by** — Enter the number of Sensors to be deleted when the autoscale reaches **Scale in** condition. | 7. Click **Next: Management >**. The **Management** tab opens. Enter the following details: | Option | Definition | | --- | --- | | **Upgrade policy** | **Upgrade mode** — Select the **Manual - Existing instance must be manually upgraded** upgrade mode. | 8. Click **Next: Health >**. The **Health** tab opens. Enter the following details: | Option | Definition | | --- | --- | | **Health** | **Monitor application health** — Select **Disable** option for monitoring the health status. | 9. Click **Next: Advanced >**. The **Advanced** tab opens. Enter the following details: | Option | Definition | | --- | --- | | **Custom Data** | Enter the **Custom Data** for the Virtual IPS Sensor in the following format: ``` { "Primary Manager IP" : "IPS_PRIMARY_MANAGER_PRIVATE_IP", "Secondary Manager IP" : "IPS_SECONDARY_MANAGER_PRIVATE_IP", "Cluster Name" : "CLUSTER_NAME", "Sensor Shared Key" : "SHARED_KEY", "Traffic Source" : "GWLB" } ``` | Custom data parameters | Parameters | Description | | --- | --- | | `Primary Manager IP` | Private IP address of the primary Manager | | `Secondary Manager IP` | Private IP address of the secondary Manager | | `Cluster Name` | Name of the Cluster in the Manager | | `Sensor Shared Key` | Shared secret key to establish trust with the Sensor | | `Traffic Source` | Type of traffic source used for traffic inspection | 10. Click **Next: Tags >**. The **Tags** tab opens. On this tab, you can categorize resources by applying a tag name and value to multiple resources and resource groups. 11. Click **Next: Review + create >**. The **Review + create** tab opens. Validate the summary details which contain all the parameters selected. Make sure the validation is passed. 12. Click **Create**. The Virtual IPS Sensor virtual machine scale set is created. > [!TIP] > Tip > > To view the Virtual IPS Sensor virtual machine, go to **All services**, under the **Compute** section, and click **Virtual machines**. You are directed to the **Virtual machines** page where you can view or delete the Virtual IPS Sensor virtual machine. 13. Once the Virtual IPS Sensor virtual machine scale set is created, access the Gateway Load Balancer and perform the following steps: 1. Navigate to **Settings** and select **Backend pools**. The **-backend-pool** page is displayed. 2. In the **-backend-pool** page, go to **IP configurations** and click **Add**. The **Add IP configurations to backend pool** panel is displayed. 3. In the **Add IP configurations to backend pool** panel, go to **Virtual machine scale set**, select the required Virtual IPS Sensor scale set, and click **Add**. 14. After the Virtual IPS Sensor is deployed, go to **Devices** → **** → **Devices** → **** → **Summary** page in the Manager to validate the successful deployment of the Virtual IPS Sensor. If the Virtual IPS Sensor is deployed successfully, a green icon appears next to the Virtual IPS Sensor name. ![Device_Summary.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-41b80343-1172-01f7-9b11-665dca3edd60.png?sv=2026-02-06&spr=https&st=2026-11-20T16%3A43%3A14Z&se=2026-11-20T17%3A43%3A14Z&sr=c&sp=r&sig=TUpymE6JE%2FfoEzikq8xU5zgDp%2B%2FaHp2vzl4Wdjc%2BNMI%3D)