--- title: "Launch the Virtual IPS Sensor AMI instance for AWS GWLB Traffic Mirroring" slug: "launch-the-virtual-ips-sensor-ami-instance-for-aws-gwlb-traffic-mirroring-2" tags: ["Product Usage"] updated: 2026-11-19T12:27:57Z published: 2026-11-19T12:27:57Z canonical: "docs.trellix.com/launch-the-virtual-ips-sensor-ami-instance-for-aws-gwlb-traffic-mirroring-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. # Launch the Virtual IPS Sensor AMI instance for AWS GWLB Traffic Mirroring 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 Sensor 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-3) 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**. **Launch configuration**![Launch configuration](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-87353b90-d7bc-b8b8-16cc-1a1e301d6dc3(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A41%3A00Z&se=2026-11-20T16%3A41%3A00Z&sr=c&sp=r&sig=pqaibCWgBklgmPo%2FHUygrNrK72MkLsp9e%2BDcCJd1phs%3D) 4. Provide the **Name** in **Name and tags** section. You can also define a tag for your Sensor instance by selecting **Add additional tags**. **Name and tags**![Name and tags](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-3f15eea2-f573-d914-008d-0ee2c576daa5(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A41%3A00Z&se=2026-11-20T16%3A41%3A00Z&sr=c&sp=r&sig=pqaibCWgBklgmPo%2FHUygrNrK72MkLsp9e%2BDcCJd1phs%3D) 5. Go to **Instance type**, and select the instance type as **c7i.xlarge**. **Instance type details**![Instance type details](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-57b2fa65-74cf-5051-5a4c-844e35a7afce(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A41%3A00Z&se=2026-11-20T16%3A41%3A00Z&sr=c&sp=r&sig=pqaibCWgBklgmPo%2FHUygrNrK72MkLsp9e%2BDcCJd1phs%3D) 6. Go to **Key pair (login)**, you can either choose an existing key pair or create a new key pair. To add an existing key pair, select the required key pair name from the drop-down. **Key pair (login) details**![Key pair (login) details](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-553ed774-764e-0a05-666e-ae3d7efcddc0(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A41%3A00Z&se=2026-11-20T16%3A41%3A00Z&sr=c&sp=r&sig=pqaibCWgBklgmPo%2FHUygrNrK72MkLsp9e%2BDcCJd1phs%3D) To create a new key pair, select **Create a new key pair**. A **Create key pair** dialog box is displayed. Provide the **Key pair name**, **Key pair type** as **RSA**, and **Private key file format** as **.pem**. Now, select **Create key pair**. Ensure to store this key pair in a secured location as you will need this key pair to connect to your instance. **Create key pair dialog box**![Create key pair dialog box](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-1ffcd102-88e5-0a1e-c410-e2dcd89aeadd(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A41%3A00Z&se=2026-11-20T16%3A41%3A00Z&sr=c&sp=r&sig=pqaibCWgBklgmPo%2FHUygrNrK72MkLsp9e%2BDcCJd1phs%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 details along with a key pair to login. 7. Go to **Network settings** and click **Edit**. From the **VPC - required** drop-down, choose the required VPC network and corresponding subnet. You can create a new Security Group to define the firewall rules to control traffic to the Sensor or choose an existing Security group. **Network settings details**![Network settings details](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-3c6b2aa3-d226-e5bd-9086-f27051488fbd(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A41%3A00Z&se=2026-11-20T16%3A41%3A00Z&sr=c&sp=r&sig=pqaibCWgBklgmPo%2FHUygrNrK72MkLsp9e%2BDcCJd1phs%3D) 8. Go to **Configure storage** , provide 1***64** GiB, and select **gp2** from Root volume drop-dow. **Configure storage details**![Configure storage details](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a3c42632-424e-d386-5507-37037b4df9bf(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A41%3A00Z&se=2026-11-20T16%3A41%3A00Z&sr=c&sp=r&sig=pqaibCWgBklgmPo%2FHUygrNrK72MkLsp9e%2BDcCJd1phs%3D) 9. Go to **Advanced details**, and provide the **User Data** to register the Sensor with the Manager. Login to the required Manager setup. Go to **Devices** → **** → **Global** → **Device Manager**. Select the **vIPS Clusters** tab. Select the hyperlink of a required cluster. The **Cluster Details** panel will display all **Sensor User Data** details. An example of user data is given below: ``` Sensor User Data: { "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 Mirroring" } ``` > [!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 the **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` | Type of traffic source used for traffic inspection. | **User data details**![User data details](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-49bc5143-45c3-c47a-395f-ce5d48d4ebef(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A41%3A00Z&se=2026-11-20T16%3A41%3A00Z&sr=c&sp=r&sig=pqaibCWgBklgmPo%2FHUygrNrK72MkLsp9e%2BDcCJd1phs%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-3). 10. Go to **Summary**, and review the details provided for the creation of the instance. You can either edit specific details or click on **Launch instance** to launch the Sensor instance. **Summary details**![Summary details](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-616845cb-dbde-006d-c16a-2d37407934da(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A41%3A00Z&se=2026-11-20T16%3A41%3A00Z&sr=c&sp=r&sig=pqaibCWgBklgmPo%2FHUygrNrK72MkLsp9e%2BDcCJd1phs%3D)