--- title: "Launch the Virtual IPS Sensor AMI instance" slug: "launch-the-virtual-ips-sensor-ami-instance-1" tags: ["Product Usage", "vIPS 11.1x", "vIPS"] updated: 2026-09-11T20:53:15Z published: 2026-09-11T20:53:15Z canonical: "docs.trellix.com/launch-the-virtual-ips-sensor-ami-instance-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. # Launch the Virtual IPS Sensor AMI instance As part of Trellix vIPS deployment, you have to launch an instance of the Virtual IPS Sensor in the AWS environment. The Sensor image provided to you in the form of an AMI is the template AMI. ****Prerequisite:**** You must obtain the AMI image by contacting Trellix support with your AWS account number and region name. ****Steps:**** To launch an instance using the template AMI, perform the following: > [!NOTE] > Note > > Sensors can be launched as part of an AWS Auto Scaling group. You should create a Launch Configuration similar to the settings provided below. See [Create an auto-scaling group for Virtual IPS Sensors in AWS](/network-and-platform/docs/create-an-auto-scaling-group-for-virtual-ips-sensors-in-aws) for more information on how to use sensor auto-scaling. 1. Log in to the AWS console, and navigate to **Services** → **Compute** → **EC2**. 2. In the left panel, under **IMAGES**, click **AMIs**. 3. Search for the **AMI Name** of the Virtual IPS Sensor (`Trellix_vIPS_Sensor_11.1.7.x`) and click **Launch**. 4. Under the **Choose an Instance type** step, select the instance type as **c5.xlarge** (vCPUs: 4, Memory 8GB), and click **Next: Configure Instance Details**. 5. In the **Configure Instance Details** step, from the drop-down lists for **Network** and **Subnet**, choose the Management network and the corresponding subnet. 6. The **User Data** to launch the Sensor instance. In the **Advanced area**, enter the **User data** to register the Sensor with the Manager. An example of user data is given below: ``` { "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" : "PROBE" } ``` > [!NOTE] > Note > > - Only for an MDR pair, the secondary Manager IP is required. > - The **Sensor Shared Key** provided in the Manager must be the same as **Sensor Shared Key** provided during Sensor deployment. User data parameters | Parameters | Description | | --- | --- | | `Primary Manager IP` | Primary 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 where the auto scale group will be launched | | `Sensor Shared Key` | Shared secret key to establish trust with the Sensor | | `Traffic Source` | Mode of traffic source | ![GUID-A0D29576-F4BB-4AC1-8D0D-8D60FA6A1965-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-d30b3344-ec2a-d366-5f1a-453ba379d07a.png?sv=2026-02-06&spr=https&st=2026-11-20T17%3A43%3A23Z&se=2026-11-20T18%3A43%3A23Z&sr=c&sp=r&sig=wMqsPsUDWw9VFTMqhUoKqmxP7n8nXEfkex3SwfBVyKA%3D) For more information on **User Data**, see the section [Custom/User data for establishing trust](/network-and-platform/docs/custom-user-data-for-establishing-trust). 7. Under the **Add Storage** step, use the default Size (64 GiB), and click **Next: Add Tags**. ![GUID-BEF819BF-A3D0-436C-B8A9-5FDA57C14C65-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a3c42632-424e-d386-5507-37037b4df9bf.png?sv=2026-02-06&spr=https&st=2026-11-20T17%3A43%3A23Z&se=2026-11-20T18%3A43%3A23Z&sr=c&sp=r&sig=wMqsPsUDWw9VFTMqhUoKqmxP7n8nXEfkex3SwfBVyKA%3D) 8. Define a tag for your Sensor instance, and click **Next: Configure Security Group**. ![GUID-2C0DCFB8-9A79-483E-A34C-C392C72B1A40-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-d592e014-c383-72a5-5c7c-b98e409774b2.png?sv=2026-02-06&spr=https&st=2026-11-20T17%3A43%3A23Z&se=2026-11-20T18%3A43%3A23Z&sr=c&sp=r&sig=wMqsPsUDWw9VFTMqhUoKqmxP7n8nXEfkex3SwfBVyKA%3D) 9. In the **Configure Security Group** page, you can create a new Security Group to define the firewall rules to control traffic to the Sensor or choose an existing Security group. ![GUID-34EF4F53-A0FE-4261-82F2-1FAEADE436D1-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-3f47d555-7558-8edd-56e8-5d5d773e6ed0.png?sv=2026-02-06&spr=https&st=2026-11-20T17%3A43%3A23Z&se=2026-11-20T18%3A43%3A23Z&sr=c&sp=r&sig=wMqsPsUDWw9VFTMqhUoKqmxP7n8nXEfkex3SwfBVyKA%3D) Once you have configured the Security Group, click on **Review and Launch**. 10. Under the **Review Instance Launch** step, review the details provided for the creation of the instance. You can either edit specific details, or click on **Launch** to assign a key pair to your Sensor instance. ![GUID-043E8707-8876-4DAA-AE92-E0171A3CC71E-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-616845cb-dbde-006d-c16a-2d37407934da.png?sv=2026-02-06&spr=https&st=2026-11-20T17%3A43%3A23Z&se=2026-11-20T18%3A43%3A23Z&sr=c&sp=r&sig=wMqsPsUDWw9VFTMqhUoKqmxP7n8nXEfkex3SwfBVyKA%3D) 11. In the **Select an existing key pair or create a new key pair** window, you can either choose an existing key pair or create a new key pair, and click **Launch instances**. The instance is now launched. ![GUID-2E8FDAA0-6E7A-4A2C-86EC-BB1A6B15F096-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-7c44ae59-9d1a-4d1f-4a66-82bda75d4d41.png?sv=2026-02-06&spr=https&st=2026-11-20T17%3A43%3A23Z&se=2026-11-20T18%3A43%3A23Z&sr=c&sp=r&sig=wMqsPsUDWw9VFTMqhUoKqmxP7n8nXEfkex3SwfBVyKA%3D) > [!NOTE] > Note > > Even though you provide a key pair, you cannot login to the Sensor instance using the key pair. You should use the Sensor's user account to login.