In this video, learn about the method to create an Azure application gateway by using the Azure portal site.
- Well let's create an application gateway using the Azure portal. First of all, we are going to create a new resource group for that application gateway. We will click on resource groups Add. I'm going to name it "App GW-RG" "Application Gateway Resource Group". And I will select the West US Region. Click on 'review' and 'create' and create the resource group. Now that the resource group is created, we can add one new application gateway. We can click on 'add' and then search for 'application gateway.' And click on 'create. In the 'create an application gateway' wizard, there are many different pages that we need to fill out. In this video we will be filling out some of these settings as default. We are going to name the application gateway "AppGW" and set it for the "West US" region. There are different tiers for the application gateway. Standard and Standard V2 are the regular application gateways. Version 2 is the one that we are going to be using now. Which enable auto-scaling. We are going to leave the minimum auto-scale instances to 'zero' and 'maximum' to ten. Support for "HTTP/2" disabled. Now we need to select one virtual network where we have to place the application gateway. We will select our scale set "Vnet". And we need to create a new subnet for the application gateway. So we will click on 'manage subnet configuration'. Click on 'create a new subset". And we will name it "AppGW-subnet". We will set it in the '10.0.100.0/24' address range and click on 'okay'. Now that the subnet is created, we can go back to the 'create an application gateway' wizard and select that subnet. We will click on 'next', and for the front end, we will select 'public'. And create a new public IP address. I will name it 'AppGW-PIP'. Public IP Okay. We will click on 'next', 'backends' and we need to add a backend pool for the application gateway. The backend pool will be the receiving service for the application gateway. I'm going to name is 'BE1" and I will add the backend pull without targets. This will be done in future videos. We'll click on 'add'. And we will click 'next' on "configuration'. We need to add some routing rules to create the application gateway. These routing rules will be mostly default for this video and we will modify them in future videos. I will create this rule as 'Rule 1' with a listener name 'Listener 1'. The frontend IP will be the public IP we created. And we will leave 'protocol ports', 'listener types', and the rest of the options as 'default'. And we will click on 'backend targets" select our backend target as "BE1" and create a new 'HTTP setting' "HTTP1" and leave all of the options as 'default'. And we will click on 'add'. We can then click 'next' on "Tags" Next, to "review and create". And we will click on 'create'. Now we need to wait for a little while for the application gateway to be created. Perfect! We can see that the deployment succeeded and we can click on the details on "AppGW". From here, we can see that the application gateway was correctly created, in the location "West US", with a new front end public IP "AppGW-PIP" that we created as well.
- External and internal load balancers
- Configuring a load balancer front end and back end
- Configuring load balancing rules
- Creating load balancers using PowerShell
- Creating application gateways using PowerShell
- Configuring a web application firewall