Fortinet white logo
Fortinet white logo
7.4.0

Connecting to the FortiNDR-VM

Connecting to the FortiNDR-VM

To connect to the FortiNDR-VM, you need your login credentials and its public DNS address.

The default username is admin and the default password is the instance ID.

  1. You can find the public DNS address in the EC2 management console. Click Instances and locate the Public DNS (IPv4) field in the lower pane. If you do not see the DNS address, you may need to enable DNS host assignment on your VPC. In this case, go back to the VPC management console, click Your VPCs, and select your VPC. Select
  2. Open an HTTPS session using the public DNS address of the FortiNDR-VM in your browser (https://). You will see a certificate error message from your browser, which is normal because the default FortiNDR certificate is self-signed and isn’t recognized by browsers. Proceed past this error. You can upload a publicly signed certificate at a later time to avoid this error. Log in to the FortiNDR-VM with your username and password (the login credentials mentioned above).
  3. If you are using a BYOL license, upload your license (.lic) file to activate the FortiNDR-VM. The FortiNDR-VM will automatically restart. After it restarts, log in again. You will now see the FortiNDR-VM dashboard. Depending on your license type, the information in the license widget on the dashboard may vary.
  4. Go to Network > Interfaces, and edit the interfaces, if required. If the IP address or subnet mask is missing for port 1 or port 2, configure these values.

Connecting AWS/On Premise sensor to AWS center

Please ensure the public IPv4 address was assigned to the AWS Center. Both on-premise and AWS sensors can use the Center’s public IP to connect.

Connecting to the FortiNDR-VM

Connecting to the FortiNDR-VM

To connect to the FortiNDR-VM, you need your login credentials and its public DNS address.

The default username is admin and the default password is the instance ID.

  1. You can find the public DNS address in the EC2 management console. Click Instances and locate the Public DNS (IPv4) field in the lower pane. If you do not see the DNS address, you may need to enable DNS host assignment on your VPC. In this case, go back to the VPC management console, click Your VPCs, and select your VPC. Select
  2. Open an HTTPS session using the public DNS address of the FortiNDR-VM in your browser (https://). You will see a certificate error message from your browser, which is normal because the default FortiNDR certificate is self-signed and isn’t recognized by browsers. Proceed past this error. You can upload a publicly signed certificate at a later time to avoid this error. Log in to the FortiNDR-VM with your username and password (the login credentials mentioned above).
  3. If you are using a BYOL license, upload your license (.lic) file to activate the FortiNDR-VM. The FortiNDR-VM will automatically restart. After it restarts, log in again. You will now see the FortiNDR-VM dashboard. Depending on your license type, the information in the license widget on the dashboard may vary.
  4. Go to Network > Interfaces, and edit the interfaces, if required. If the IP address or subnet mask is missing for port 1 or port 2, configure these values.

Connecting AWS/On Premise sensor to AWS center

Please ensure the public IPv4 address was assigned to the AWS Center. Both on-premise and AWS sensors can use the Center’s public IP to connect.