The Infoblox Data Connector works with various components in a hybrid cloud environment to deliver source data to configured destinations. To deploy the end-to-end Data Connector solution, set up your environment, sources, data types, destinations, data filters, and traffic flows according to the requirements and instructions that Infoblox provides.
Note
This release of Data Connector supports only IPv4 addresses.
To deploy the end-to-end Data Connector solution, do the following:
- Review the prerequisites and requirements, then set up your environment and components. For details, see Data Connector Deployment Requirements.
- If you do not already have a join token, then create one. For details, see Managing Join Tokens for Data Connectors.
- Set up a Data Connector VM (virtual machine) by using either the Docker or OVA package (for container and VM) that Infoblox provides, and connect the virtual machine to the Cloud Services Portal using the join token. For information on all installer packages, including the installers for Docker or the OVA package, see Downloading BloxOne Apps. All installer packages are available In https://csp.infoblox.com at Administration > Downloads. Within the Cloud Services Portal, all available installer packages are listed in the drop-down menu of the On-Prem Hosts section of the page.
You deploy a Data Connector VM as an on-prem host running the Data Connector service in BloxOne DDI and BloxOne Threat Defense Cloud. For details, see Deploying the Data Connector VM.
4. Log in to the Cloud Services Portal, locate the on-prem host or the Data Connector VM, rename the host, and enable the Data Connector service on it. For details, see Viewing and Modifying Data Connector Configuration.
5. Before you configure traffic flows for Data Connector, you must first set up the sources from which you want Data Connector to collect data.
BloxOne Threat Defense Cloud is preconfigured as the source and destination, and BloxOne DDI is preconfigured as the source. No configuration is required on your part. For details, see Configuring Sources.
6. You must also configure the destinations to which you want Data Connector to send source data. For details, see Configuring Destinations.
7. Optionally, you can add ETL (Extract, Transform, Load) filters to extract specific source data before Data Connector sends the data to the configured destinations.
For details, see Configuring ETL filters.
8. Once you have configured sources, destinations, and ETL filters, you can configure not only the traffic flows that define the types of source data that will be collected from the sources but also the destinations to which the data will be sent. For details, see Configuring Traffic Flows.