NFO could be installed in your data center or in Amazon AWS, Microsift Azure, or in GCP cloud.
To install NFO in your AWS environment using AMI visit: https://aws.amazon.com/marketplace/pp/B084SNHSXH/.
To install NFO in your GCP environment, create a virtual machine (VM) instance in your Azure Cloud. Minimum requirements:
Machine type: Any with 4 vCPU, 8 GB RAM, 20 GB disk
20 GB disk space
To install NFO in your GCP environment, create a virtual machine (VM) instance in your Google Cloud. Minimum requirements:
Machine type: E2 (
20 GB disk space
Please visit https://docs.netflowlogic.com/netflow_optimizer/installation-and-administration-guide for details.
To install NFO in your data center, visit: https://docs.netflowlogic.com/netflow_optimizer/installation-and-administration-guide
If NFO is installed in your data center you have a choice:
EDFN is installed with NFO. Use this choice if you want to collect and enrich *flows from your routers, switches, and firewalls in your data center, in addition to collecting VPC Flow logs
Install EDFN in AWS or GCP environment. Use this option if want to collect only VPC Flow logs
EDFN installed with NFO connects to NFO automatically.
If you install EDFN separately from NFO (e.g. on an EC2 instance in one of your AWS accounts or GCP VM instance in your Google Cloud), visit: https://docs.netflowlogic.com/netflow_optimizer/external-data-feeder-for-nfo-installation-guide.
Change uri parameter in updater.properties file located in /opt/nfi-updater/conf to IP address of NetFlow Optimizer. See https://docs.netflowlogic.com/netflow_optimizer/external-data-feeder-for-nfo-installation-guide/installing-external-data-feeder-for-nfo for details.
One EDFN instance could be configured to ingest VPC Flow logs from multiple accounts / VPCs /S3 buckets.