--- title: "Performing the initial Network Security configuration using AWS" slug: "performing-the-initial-network-security-configuration-using-aws" tags: ["Endpoint Security (HX)", "Product Usage"] updated: 2026-10-02T13:40:12Z published: 2026-10-02T13:40:12Z canonical: "docs.trellix.com/performing-the-initial-network-security-configuration-using-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. # Performing the initial Network Security configuration using AWS The management interface is the port through which the virtual sensor is managed and administered. It is also the port through which integration of the Central Management System appliance and a managed sensor is managed. With the single-port address type, the management interface is also the port through which a managed sensor requests and downloads software updates from the DTI network. Initial settings need to be configured to set up the management interface and to allow access to the network, change the default administrator password, and so on. To perform the initial configuration of a virtual Network Security appliance: 1. Connect to the sensor through an SSH client. 2. At the login prompt, enter `admin`. 3. Do one of the following: - Use the` ssh -i `command to use the private key file to establish the SSH session. For example,` ssh -i /path/<my-key-pair>.pem admin@<instance>`. When prompted, change the password using the` username admin password <new password> `command. You will be logged out. Log in again using the new password. - At the password prompt, enter the initial password you configured in [Configuring the activation code and initial admin password](/network-and-platform/docs/configuring-the-activation-code-and-initial-admin-password-3). 4. Accept the license agreement. The configuration jump-start wizard begins. 5. Answer the wizard questions as described in the following table. ### Important If you want to configure a static IP address instead of using DHCP, see [Configuring a static IP address for the ether1 interface](/network-and-platform/docs/configuring-a-static-ip-address-for-the-ether1-interface-2). ### Note If you enter **yes** in the "Use DHCP on ether1 interface?" step, the ether1 interface will obtain its IP address from the AWS eth0 device. | Step | Response | | --- | --- | | Hostname? | Enter the hostname for the appliance. | | Admin password? | (Optional) Enter a new administrator password. | | Confirm admin password? | Re-enter the new administrator password. | | Enable remote access for 'admin' user? | Enter **yes** to enable the administrator to log in to the appliance remotely. Enter **no** to disable remote access. | | Enable IPv4 for the management interface (ether1) | Enter **yes** to enable the IPv4 protocol. If you enter **no**, IPv4 setup is skipped and you are redirected to the IPv6 configuration, where you can enable or configure IPv6 instead. | | Use DHCP on ether1 interface? | Enter **no** to manually configure your IP address and network settings. | | Use zeroconf on ether1 interface? | Enter **yes** to use zero-configuration (zeroconf) networking. Enter **no** to specify a static IP address and network mask. (If you specify **yes**, the next step is skipped.) **NOTE**: Do not use zeroconf on the primary interface. | | Primary IPv4 address and masklen? | Enter the IPv4 address for the management interface in A.B.C.D format and enter the network mask (for example, **1.1.1.2 /24**). | | Default gateway? | Enter the gateway IP address for the management interface. | | Primary DNS server? | Enter the IP address of the DNS server. | | Include HOMENET private IP range | Enter yes to configure the following homenet IP range for Snort rules. For further configuration, use the CLI homenet command or Web UI. - 10.0.0.0 - 10.255.255.255 (10/8 prefix) - 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) - 192.168.0.0 - 192.168.255.255 (192.168/16 prefix) HOMENET is a default variable in the Snort rules (snort.conf) supported by the standard libpcap library where you can specify IP addresses that are to be protected. The Network Security appliance allows the configuration of the HOME_NET variable the CLI and WebUI. | | Include HOMENET private IPv6 range | Enter yes to configure the following homenet IP range for Snort rules. For further configuration, use the CLI homenet command or Web UI. - FC00::/7 HOMENET is a default variable in the Snort rules (snort.conf) supported by the standard libpcap library where you can specify IP addresses that are to be protected. The Network Security appliance allows the configuration of the HOME_NET variable the CLI and WebUI. | | Enable IPv6 on management interface (ether1) | Enable IPv6 on management interface (ether1) ### Note **Enable Incident Response** or **Compromise Assessment** features are not supported when IPv6 is selected as yes. | | Enable IPv6 autoconfig (SLAAC) on ether1 interface? | Enter **yes** to enable configuration. Enter **no** to disable configuration. The default setting is **no**. | | Enable DHCPv6 on ether1 interface? | Enter **yes** to enable configuration. Enter **no** to disable configuration. The default setting is **no**. | | Primary IPv6 address and masklen (connection may be lost upon change)? | Enter the IPv6 address in X:X:X:X:X:X:X:X format and the prefix length. Example: 2001:db8::1/64. | | IPv6 Default gateway | Enter the gateway IPv6 address for the management interface. | | Primary DNS server? | Enter the IPv6 address in X:X:X:X:X:X:X:X format. Example: 2001:db8::1. | | IPv6 Primary DNS server | Enter the IPv6 address of the DNS server. | | Domain name? | Enter the domain for the management interface (for example, **it.acme.com**). | | Enable Incident Response or Compromise Assessment? | Enter **no**. These features are not supported in virtual NX deployments. | | Enable fenet service? | Enter **yes** to enable access to the DTI network. | | Enable fenet license update service? | Enter **yes** to enable the licensing service to automatically download your licenses from the DTI network and install them. (If licenses are downloaded and installed successfully, the wizard skips the step that prompts for the product license key and the step that prompts for the security-content updates key.) | | Sync appliance time with fenet? | Enter **yes** to synchronize the appliance time with the DTI server time. If you enabled the licensing service, synchronization prevents a feature from being temporarily unlicensed due to a time gap. The wizard makes three attempts to perform this step before it gives up and moves to the next step. | | Update licenses from fenet? | Enter **yes** to download and install your licenses. The wizard makes three attempts to perform this step before it gives up and moves to the next step. | | Enable NTP? | Enter **yes** to enable automatic time synchronization with one or more Network Time Protocol (NTP) servers. Enter **no** to manually set the time and date on the appliance. (This step is skipped if you entered yes in the "Sync appliance time with fenet?" step.) If you enter no, specify the time and date in subsequent steps. | | Set date(//
)? | Enter the appliance date in Greenwich Mean Time (GMT) (UTC+0). | | Set time (::)? | Enter the appliance time in Greenwich Mean Time (GMT) (UTC+0). (This step and the next step are skipped if you entered **yes** in the "Sync appliance time with fenet?" or "Enable NTP?" step.) | | Submission: Configure Interface? | Press Enter to accept ether1 as the interface through which sensors and brokers communicate. Otherwise, enter the name of the other interface. (If you accept ether1, the next three steps are skipped.) | | Submission: Interface? | Enter the name of the other interface. ### Note To keep management and data traffic separate, Trellix recommends that you use another management interface, such as ether2, and not a monitoring interface. | | Submission: Use DHCP on interface? | Enter **yes** to use Dynamic Host Configuration Protocol (DHCP) to configure the submission interface IP address and other network parameters. Enter **no** to manually configure the IP address and network settings. (If you enter **yes**, the static IP addressing steps are skipped.) | | Submission: IP address and masklen? | Enter the IP address for the submission interface in A.B.C.D format and enter the network mask (for example, **10.1.1.1 /24**). | | Submission: Default IPv4 gateway? | Enter the gateway IP address for the submission interface. | | Product license key? | Enter the product license key you obtained from Trellix, or press Enter to install a 15-day evaluation license. (This step and the next step are skipped if you entered **yes** in the "Enable fenet license update service?" step and if licenses were successfully installed as a result.) | | Security-content updates key? | Enter the security-content license key you obtained from Trellix, or press Enter to skip this step and install the license later. | | Send a request to be managed by CMS | Enter **yes** to add Network Security to Central Management System. | | CMS Address | Enter Central Management System IPv4 or IPv6 address. | | CMS Server username | Enter the Central Management System server username. (Example: admin) | | CMS Server password | Enter the admin password for Central Management System server. | | CMS Port? | Enter the port number for the Central Management System appliance | | Appliance Reachable to CMS? | Enter yes/no. | | Authetication type | Choose the required authentication type. - Password authentication - SSH-DSA2 and SSH-RSA2 authentication. | :