--- title: "Configuring Network Security network interfaces on AWS (manual method only)" slug: "configuring-network-security-network-interfaces-on-aws-manual-method-only" tags: ["Endpoint Security (HX)", "Product Usage"] updated: 2026-10-01T09:40:08Z published: 2026-10-01T09:40:08Z canonical: "docs.trellix.com/configuring-network-security-network-interfaces-on-aws-manual-method-only" --- > ## 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. # Configuring Network Security network interfaces on AWS (manual method only) The ether1 interface on the Network Security instance is the only interface that is created by default. If you are using the manual deployment method, you must create the optional submission interface (ether2) and the monitoring interfaces (pether3, pether4, and so on), and then attach them to the instance. Source and destination checking must be disabled on monitoring interfaces to ensure that all network traffic reaches the instance. The following table shows the mapping between AWS devices and Network Security interfaces. | AWS Device | Network Security Interface | Purpose | | --- | --- | --- | | eth0 | ether1 | Management interface, Submission interface to IVX cluster (Cloud MVX, IVX Smart Grid) | | eth1 | ether2 | (*Optional*) Dedicated submission interface to IVX cluster (Cloud MVX, IVX Smart Grid) | | eth2 | pether3 | Monitoring interface | | eth3 | pether4 | Monitoring interface | ### Creating Network Interfaces This section describes how to create a network interface for your Network Security instance if you are using the manual deployment method. To create a network interface: 1. Open the Amazon EC2 console. 2. In the left pane, select **Network & Security** > **Network Interfaces**. 3. Click **Create Network Interface**. ![AWS_CreateNetworkInterface_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-1c246fad-a2e0-bc5d-99a6-086180951a12.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A28%3A26Z&se=2026-11-20T11%3A28%3A26Z&sr=c&sp=r&sig=9f1PMvj%2Fs6UG9dXGfOxSJ7gsb%2Fju%2FflqcxCqzwe9XRo%3D) 4. Enter information that uniquely identifies the interface in the **Description** field. 5. Select the subnet for the interface in the **Subnet** drop-down list. ### Important Each interface must be in a separate subnet. 6. Select **Custom** to manually configure a static IPv4 address. 7. Enter the custom static IPv4 address in the **IPv4 address** field. 8. Complete the **Elastic Fabric Adapter** and **Security groups** fields as directed by your AWS administrator. 9. Click **Create**. 10. Repeat this procedure for each network interface. 11. Continue to [Attaching network interfaces](/network-and-platform/docs/configuring-network-security-network-interfaces-on-aws-manual-method-only#attaching_network_interfaces). ### Attaching Network Interfaces This section describes how to attach a network interface to your instance if you are using the manual deployment method. To attach a network interface: 1. Open the EC2 console. 2. Select **Instances** > **Instances** in the left pane. 3. Right-click the instance and then select **Networking** > **Attach Network Interface**. The **Attach Network Interface** dialog box opens. ![AWS_AttachInterface_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-174f4880-b7b0-6e69-7b9b-8158cad70715.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A28%3A26Z&se=2026-11-20T11%3A28%3A26Z&sr=c&sp=r&sig=9f1PMvj%2Fs6UG9dXGfOxSJ7gsb%2Fju%2FflqcxCqzwe9XRo%3D) 4. Select the interface with the lowest number in the **Network Interface** drop-down list (for example, ether2) and then click **Attach**. 5. Repeat the previous step for each network interface. ### Important Attach the interfaces in numeric order. For example, attach pether3 before pether4. 6. Disable source and destination checks on each monitor interface. 1. Select the interface. 2. Right-click and select **Change Source/Dest. Check**. The **Source/Dest. Check** dialog box opens. 3. Select **Disabled** and then click **Save**. ![AWS_SourceDestCheck_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-639db0ef-9d07-4624-b215-9a1d58925149.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A28%3A26Z&se=2026-11-20T11%3A28%3A26Z&sr=c&sp=r&sig=9f1PMvj%2Fs6UG9dXGfOxSJ7gsb%2Fju%2FflqcxCqzwe9XRo%3D) 7. Stop the instance: 1. Select **Instances** in the navigation pane. 2. Select the instance, right-click, and then select **Instance State** > **Stop**. 8. Restart the instance: - Select the instance, right-click, and then select **Instance State** > **Start**. ### Important Do not perform this step if you plan to perform the following optional procedure ([Configuring the activation code and initial admin password](/network-and-platform/docs/configuring-the-activation-code-and-initial-admin-password-manual-method-only)). ### Note Network interfaces are placed in the following VRF namespaces: - ether1, ether2—vrf0 - pether3, pether4—vrfA - pether5, pether6—vrfB - pether7, pether8—vrfC - pether9, pether10—vrfD For details about virtual routing and forwarding (VRF), see the "Layer 3 Forwarding Using VRF Instances" information in the *Network Security System Administration Guide*. :