Prerequisites for Private Network Installs ​

You can install Yellowbrick using a VNet with a private network that you create prior to, and for the express purpose of, the installation. The VNet must adhere to a number of prerequisites. Your organization may have a hub-and-spoke environment, in which the "hub VNet" is at the corporate level, and a number of "spoke VNets" are created for individual applications, such as Yellowbrick.

Before installing Yellowbrick into an existing VNet, make sure it meets the following network requirements.

Private DNS Zone ​

You must create a private DNS zone for your Yellowbrick deployment using the Azure DNS service, which determines how traffic is routed within an Azure VNet (as opposed to internet routing).

A DNS zone assigns a custom domain name in your VNet and provides access to that domain as a subnet within the domain managed by your identify service provider (IDP). Yellowbrick requires the ability to register DNS records for many of the services that are created (CDWM, observability, and so on), so they are reachable by DNS name. When creating a private DNS zone, it is important to configure DNS forwarding to the appropriate corporate DNS servers so that these services can be resolved by the end user's network. This also has implications for certificates that are used to encrypt all network communication between components of the Yellowbrick Data Warehouse and terminate with the back end nodes themselves.

See To Create the Private DNS Zone.

azure-cli ​

You must have a current version of the azure-cli tool available on the client system to create the azure-installer template. For more information, see General Prerequisites.

Parent topic:Preparing for a New Installation