Scalability

1. Provision VMSS with LB

Overview This exercise will walk you through creating an Azure VM Scale Set (VMSS) using the Azure Portal. You will: configure Nginx on each VM instance through a cloud-init script set up a Load Balancer (LB) with public IP configure Network Security Group (NSG) rules to allow HTTP and SSH. By the end of this exercise, you will have a scalable group of VMs behind a Load Balancer (this is a level 4 load balancer) »

2. Provision an Application Gateway.

Overview In this exercise, you will extend the environment you created in the previous Provision VMSS with LB by adding an Azure Application Gateway (AGW)—a Layer 7 load balancer. The AGW will distribute HTTP traffic to the VM instances created earlier. You will create a new subnet specifically for the AGW and configure it to route requests to the VMSS backend. 💡 Prerequisite Make sure you have completed the Provision VMSS with LB exercise, including its Resource Group, VNet, and VM Scale Set. »

3. Enabling HTTPS with a Self-Signed Certificate

Overview In this exercise, you will enable HTTPS on the Azure Application Gateway (AGW) created in the previous exercise. You will generate a self-signed certificate, upload it to the Application Gateway’s HTTP settings, and create an HTTPS listener. 💡 Prerequisite You must have an Application Gateway and VM Scale Set already set up, as described in the previous exercises. Step 1: Generate a Self-Signed Certificate (Local Machine or Cloud Shell) You can generate a self-signed certificate using OpenSSL (or PowerShell, if on Windows). »

4. Build a Scalable Solution in Azure

Note! This exercise can be rather costly, so please do not forget to decommission everything when you are done. Don´t leave it overnight. Overview In this exercise, you will create a secure, multi-tier architecture in Azure using the Azure Portal. You will set up: A Virtual Network (VNet) with four subnets for different tiers: AppGateway, Application, Database and BastionHost. An Azure Bastion Host for secure remote access to resources within the VNet. »