--- title: "Use case scenario 2: Deploying a Network Security instance in AWS between internal Web Servers and a NAT device" slug: "use-case-scenario-2-deploying-network-security-instance-aws" tags: ["Endpoint Security (HX)", "Product Usage"] updated: 2026-09-09T22:45:42Z published: 2026-09-09T22:45:42Z canonical: "docs.trellix.com/use-case-scenario-2-deploying-network-security-instance-aws" --- > ## 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. # Use case scenario 2: Deploying a Network Security instance in AWS between internal Web Servers and a NAT device This section describes how to deploy a virtual Network Security instance in a scenario in which a Network Security instance is deployed inline in Amazon Web Services (AWS) between Web servers in a private subnet and a Network Address Translation (NAT) device. In this scenario, the NAT device acts as a third-party virtual firewall and performs the address translation between the public Internet and the private subnet hosting the Web servers. Web clients connect to the Web servers through the public IP address of the NAT device. The traffic between the Web clients and Web servers flows through the Network Security instance, which protects the Web servers. ### Note This procedure assumes that security groups and network access control lists are already configured in AWS. The network mask of the IP addresses in this scenario is 255.255.255.224 (10.88.9.*xxx*/27). ![Use_Case-2.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-b5e7c73b-9205-1ce4-5f50-dd18962b32d6.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A34%3A25Z&se=2026-11-20T11%3A34%3A25Z&sr=c&sp=r&sig=sQh8PDcKOnk6S2bYAW%2Bb24Z31VE3k5Vtqfcr0BYNjsI%3D) This scenario involves the following components: - **NAT device**—An Ubuntu Linux EC2 instance with destination network address translation (DNAT) configured and IP forwarding enabled to translate a public destination IP address to a private destination IP address. - **Web servers**—Web servers on a private subnet. External Web clients connect to the Web servers through the public IP address configured on the NAT device. - Network Security **instance**—A Network Security EC2 instance deployed inline. Port pair A is the inline port pair. One monitoring interface is connected to the same subnet as the NAT instance and the other monitoring interface is connected to the private subnet that hosts the Web servers. - **Web clients**—External Internet-connected devices that attempt to connect to the Web servers using the public DNS domain names of the Web servers. A DNS server resolves the domain names to the public IP addresses. Perform the following tasks to configure this deployment scenario. 1. [Configure a Network Security monitoring Interface as the default gateway for the Web Servers](/network-and-platform/docs/use-case-scenario-2-deploying-network-security-instance-aws#UUID-da7af949-8f8b-4643-d11e-10ec967a68c5_id_configur) 2. [Configure the NAT private IP address as the default gateway for the other monitoring interface](/network-and-platform/docs/use-case-scenario-2-deploying-network-security-instance-aws#UUID-da7af949-8f8b-4643-d11e-10ec967a68c5_id_configur2) 3. [Configure an HTTP proxy device for management port connectivity](/network-and-platform/docs/use-case-scenario-2-deploying-network-security-instance-aws#UUID-da7af949-8f8b-4643-d11e-10ec967a68c5_id_configur3) 4. [Configure the NAT instance](/network-and-platform/docs/use-case-scenario-2-deploying-network-security-instance-aws#UUID-da7af949-8f8b-4643-d11e-10ec967a68c5_id_configur4) ### Configure a Network Security monitoring interface as the default gateway for the Web Servers A Network Security monitoring interface must be the default gateway for the Web servers hosted on the private subnet. This allows the Web servers to send traffic to the Network Security instance. To configure the monitoring interface as the default gateway: 1. Add a default route in the route table associated with the private subnet that hosts the Web servers. 2. Set the destination to 0.0.0.0/0. 3. Set the target to the Network Security network interface (also known as elastic network interface, or ENI) that is connected to the private subnet (pether4 in this example). The following illustration shows the example AWS route table configuration. ![AWS_InlineNXRouteTable.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-9506ce14-1f04-1a04-664e-3af3da472c84.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A34%3A25Z&se=2026-11-20T11%3A34%3A25Z&sr=c&sp=r&sig=sQh8PDcKOnk6S2bYAW%2Bb24Z31VE3k5Vtqfcr0BYNjsI%3D) For more information about route tables and detailed instructions for implementing them, see the Amazon AWS VPC route table documentation. ### Configure the NAT private IP address as the default gateway for the other Network Security monitoring interface The private IP address of the NAT instance must be configured as the default gateway for the other Network Security monitoring interface. This procedure creates a static IP default gateway and removes the DHCP default gateway from the configuration. To configure the NAT private IP address as the default gateway: 1. Configure a default gateway to point to the NAT instance public IP address through the monitoring port interface (pether3 in this example) connected on that subnet. In this example,` <NAT ether1 IP> `is 10.88.9.79. `nx-hostname (config) # ip route vrf vrfA 0.0.0.0 /0 <NAT ether1 IP> ` 2. Verify your changes. `nx-hostname (config) # show ip route` 3. Save your changes. `nx-hostname (config) # write memory` The following Network Security routing table shows that the static gateway is the only default gateway that exists on the instance. ``` nx-hostname (config) # show ip route Destination     Mask              Gateway       Interface     Source default         0.0.0.0           10.88.9.79    pether3       static 10.88.9.64      255.255.255.224   0.0.0.0       pether3       interface 10.88.9.96      255.255.255.224   0.0.0.0       pether4       interface 10.88.9.192     255.255.255.224   0.0.0.0       ether1        interface        Custom table routes Destination     Mask              Gateway       Interface     Table nx-hostname (config) #   ``` ### Configure an HTTP proxy device for management port connectivity This procedure describes how to configure an HTTP proxy device on a Network Security instance to establish management port connectivity for services that operate over the management interface and require access to the Internet. ### Important The HTTP proxy device must have a public IP address that can communicate with the Network Security ether1 interface IP address. ### Note If the Network Security instance is managed by a Central Management System appliance, this procedure must be performed on the Central Management System appliance instead of the Network Security instance. To configure and enable an HTTP proxy device: 1. Configure the proxy device hostname or IP address, and the port (if you do not want to use the default port 8080): ``` nx-hostname (config) # fenet proxy host :[] ``` 2. Enable the proxy device: `nx-hostname (config) # fenet proxy enable` 3. Verify your changes: `nx-hostname (config) # show fenet` 4. Save your changes: `nx-hostname (config) # write memory` For details about configuring an HTTP proxy on a Network Security instance or Central Management System appliance, see the *Network Security* *System Administration Guide* or the *Central Management System* *Administration Guide*. ### Configure the NAT instance The NAT instance must simulate a third-party firewall that provides NAT functionality. In addition to configuring DNAT and enabling IP forwarding, you should create a static route in the NAT configuration that allows the Web servers to use the IP address of the Network Security monitoring interface configured for the NAT instance (pether3 in this example) as the next-hop gateway. The following is an excerpt from the routing table for the NAT instance used in this example. In this excerpt, 10.88.9.107 and 10.88.9.111 are the Web server IP addresses and 10.88.9.77 is the Network Security pether3 IP address. ``` Kernel IP routing table Destination     Gateway ... 10.88.9.107     10.88.9.77 10.88.9.111     10.88.9.77 ... ``` For details about using an Amazon Linux AMI as a NAT instance, see the Amazon AWS VPC NAT instance documentation. :