This section covers the steps to deploy a Avi Load Balancer Controller in Micorsoft Amazon Web Services.

Avi Load Balancer is available in Azure Marketplace as a Bring Your Own License (BYOL) offering.

  1. Access Azure Marketplace at https://azuremarketplace.microsoft.com/ and log in using your Azure credentials. Alternately, you can log in using your Azure credentials at https://portal.azure.com. Marketplace Link:

  2. Navigate to the Avi Load Balancer page on Azure Marketplace.

  3. Click Get it Now to start the deployment process. If the deployment is via the Azure portal then create a new VM and search for Avi Load Balancer Networks. The Avi Load Balancer VM will show up in the search results.

Provide the information requested under the Basics tab. Click on OK to continue to the next tab.

  1. Based on deployment scale considerations, choose an appropriate VM size. For more details on Controller sizing, see Avi Load Balancer Controller Sizing. Avi Load Balancer Controller recommends general purpose or compute/ memory optimized instances for running controllers. For instance, Standard_DS4_v2 for Small, Standard_DS5_v2 for Medium and Standard_F32s_v2 for Large. Burstable instances are not recommended for running controller virtual machines.

  2. Avi Load Balancer Controller recommends SE with minimum memory of 2 GB, and 1 vCPU.

For more information on the recommended hard disk size, see Allocating Disk Capacity.

Note:

Azure Cloud in Avi Load Balancer starts to use Azure Standard Load Balancer by default instead of Azure Basic Load Balancer for Service Engine placements. Azure Basic Load Balancer will be retired on 30 September 2025.

Controller Cluster having Azure cloud will have the following warning message on the Controller:

Azure Basic LB will be discontinued on September 30, 2025. If you plan on continuing to use Azure, we recommend using Standard ALB.

A migration guide for moving virtual services to a new SE group with standard ALB will be provided via a separate knowledge base article. These guides would not be tied to any release, and customers can plan these in any of the Avi releases they are running.

In the Settings tab, select the following options:

  1. Availability set: It is recommended to use an availability set for the Controllers.

  2. Storage: Select Yes for managed disks.

  3. Virtual network: Create a new VNet, or use an existing VNet.

  4. Subnet: Select a subnet for the Avi Load Balancer Controller management IP address to be allocated from.

  5. (Optional) Public IP address: Allocate an existing or new public IP address to the controller VM.

  6. Network security group (firewall): Apply an existing or new network security group to restrict traffic to the Controller.

  7. Click OK , followed by Purchase, to run final validations and initiate the deployment.

  8. (Optional) Create a Controller cluster.

To create a Controller cluster,

  • If deploying from the Microsoft Azure Marketplace, use the JSON template found here.

  • If deploying from a downloaded version of VHD, use the JSON template found here.

Initial Configuration for Avi Load Balancer Controller

Once the Controller is up, it can be configured through a web browser. The FQDN will be mentioned as an output of the template execution, as in this case, avicontrollerpubip.westus.cloudapp.azure.com.

Follow the given steps to complete the initial configuration.

  1. Provide credentials for the administrator account (Username: admin).

    Figure 1.

  2. Provide DNS and NTP Settings (Can be edited later).

    Figure 2.

  3. Provide an email address to be used for alerts from the Controller (Can be set up at a later stage).

    Figure 3.

  4. Select No Orchestrator to complete the initial configuration.

  5. Continue by clicking No for Support multiple Tenants (Multi-tenancy can be enabled later).

  6. Once the setup is completed, the browser will automatically refresh to the Avi Load Balancer Controller dashboard.

  7. The next step is to configure Microsoft Azure cloud on Avi Load Balancer.

    For more information, see Configuring the Avi Load Balancer Cloud Connector.

  8. Once the cloud is configured on Avi Load Balancer Controller, complete the steps for configuring virtual service.

    For more information, see Configuring Virtual Service.

Note:

To ensure complete redundancy, create a Avi Load Balancer Controller cluster. Creating the Controller cluster is an optional step.

Two additional Controller nodes can be added to create a 3-node Avi Load Balancer Controller cluster.