Create a Standard Load Balancer with Azure CLI

Note: When setting up the Azure CLI, if you have trouble using the existing storage account, choose to create a new storage account with a unique name.

You've been provided with one VM with this hands-on lab, which is the VM that hosts your application now. You will create a network interface for the two new VMs you are to create that will be load balanced. You will then create the VMs with the appropriate network interfaces attached. Use the following cloud-init script to install the packages during the deployment:

#cloud-config
package_upgrade: true
packages:
  - nginx
  - nodejs
  - npm
write_files:
  - owner: www-data:www-data
  - path: /etc/nginx/sites-available/default
    content: |
      server {
        listen 80;
        location / {
          proxy_pass http://localhost:3000;
          proxy_http_version 1.1;
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection keep-alive;
          proxy_set_header Host $host;
          proxy_cache_bypass $http_upgrade;
        }
      }
  - owner: azureuser:azureuser
  - path: /home/azureuser/myapp/index.js
    content: |
      var express = require('express')
      var app = express()
      var os = require('os');
      app.get('/', function (req, res) {
        res.send('Hello World from host ' + os.hostname() + '!')
      })
      app.listen(3000, function () {
        console.log('Hello world app listening on port 3000!')
      })
runcmd:
  - service nginx restart
  - cd "/home/azureuser/myapp"
  - npm init
  - npm install express -y
  - nodejs index.js

Once you've deployed the VMs, create a standard load balancer with a frontend and backend pool. The load balancer should also have rules for port 80 going to the frontend pool.