--- title: "High-level steps for configuring Trellix vIPS with AWS Gateway Load Balancer" slug: "high-level-steps-for-configuring-trellix-vips-with-aws-gateway-load-balancer-2" tags: ["Product Usage"] updated: 2026-11-19T12:29:40Z published: 2026-11-19T12:29:40Z canonical: "docs.trellix.com/high-level-steps-for-configuring-trellix-vips-with-aws-gateway-load-balancer-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. # High-level steps for configuring Trellix vIPS with AWS Gateway Load Balancer We assume that your VPCs and Availability Zones are configured in line with your organization's requirements. The Virtual IPS Sensor can be installed in the same VPC as your Manager. Before installing the Manager, ensure that you have selected the appropriate region in the AWS console. For recommendations on the various deployment options, see the topic [Use case scenarios](/network-and-platform/docs/use-case-scenarios-26). This section provides the high-level steps for deploying individual Trellix vIPS components in the AWS environment. > [!NOTE] > Note > > For an existing deployment, you can deploy the GWLB-based solution after meeting the prerequisites. Any upgrade from Probe to GWLB is not supported. All the routes for protected VM have to be added to forward the traffic to GWLBe. Recommendation for deployment: - It is recommended that you follow the steps below to configure Trellix vIPS in the AWS environment. After installing the Manager, you can deploy any of the remaining components. - For each account you wish to secure, Trellix recommends you create a separate protected group for different accounts. In the event of an attack, this will help in identifying the account that was attacked. ![High-level_steps_for_configuring_Trellix_vIPS_in_AWS_envir_GUID-83CA8368-8A36-4E00-AAD2-1D5299BED6ED_1_en-us_Source.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-b24a9c5f-716d-ea7d-063f-53cebb706133(2).png?sv=2026-02-06&spr=https&st=2026-11-20T14%3A20%3A45Z&se=2026-11-20T15%3A20%3A45Z&sr=c&sp=r&sig=3S6mr1be65K5jPNKHO89c01K4ZOnCUD1atS3tqEPIX0%3D) 1. Launch the Trellix IPS Manager. For more information, see [Install the Trellix Intrusion Prevention System Manager](/network-and-platform/docs/install-the-trellix-intrusion-prevention-system-manager-13). 2. Configure a Cluster for a Protected Group with GWLB traffic source. For more information, see [Create a Cluster in the Manager for AWS using GWLB-based solution](/network-and-platform/docs/install-the-trellix-intrusion-prevention-system-manager-13). 3. Create Protected Groups for instance. For more information, see [Create a Protected Group for AWS cloud using GWLB-based solution](/network-and-platform/docs/install-the-trellix-intrusion-prevention-system-manager-13). 4. (Optional) Configure a Local controller with an IAM role, if autoscaling is needed. Also, configure a Cloud Account in Controller for AWS Cloud Discovery. For more information, see [Configure a Controller in the Manager](/network-and-platform/docs/install-the-trellix-intrusion-prevention-system-manager-13). 5. Launch the Virtual IPS Sensor instance/Autoscale group of Sensors with GWLB traffic source. For more information, see [Launch the Virtual IPS Sensor AMI instance using GWLB-based solution](/network-and-platform/docs/install-the-trellix-intrusion-prevention-system-manager-13). 6. Once the Sensor instance is active, add it to the **Target Group** on the AWS console. For more information, see [Create a Target group](/network-and-platform/docs/install-the-trellix-intrusion-prevention-system-manager-13). 7. Launch the protected VM in the workload VPC for the associate traffic inspection to GWLBe.