[00:00] In this lesson, I'll demonstrate how to create an Azure virtual machine preloaded with Ignition Cloud Edition. If you search for Ignition in the Azure marketplace, you should be able to find the Ignition Cloud Edition Marketplace listing, which I currently have opened. If you explore the different tabs of the listing, you can find an overview of Cloud Edition. You can view pricing details and you can view ratings and reviews. In order to use this image, I'll click the Get It Now button on the left side of the screen. Now I can click continue in this popup to start creating this app in Azure. This next page will have a lot of the same information from the marketplace listing with the addition of usage information and support information. However, now we can see some different deployment options. You can choose to start with a preset configuration, purchase a reservation through Azure, or deploy programmatically, but I'm gonna choose the standard create option, and this will take me to the VM creation wizard where I can start supplying the configuration options for my Cloud Edition VM.

[01:13] First, I'll need to provide some project details for billing and resource management purposes. My subscription is already selected, but I'll go ahead and create a resource group for my Cloud Edition resources. Next, I'll provide the instance details. I'll give my virtual machine a name. I'll leave the next two fields at the default values, but the region and availability options let you configure where the VM is hosted and manage the resiliency of your resources in case of data center outages or maintenance events. The image is the base operating system or application for the VM, and the Cloud Edition image will already be selected thanks to the steps we've already gone through. You can choose to modify the VM size to add or remove resources based on your needs, but I'm gonna leave this standard D2 VM with two virtual CPUs and eight gigabytes of memory selected.

[02:11] I'll need to configure an administrator account for when I wanna access my vm. I'm going to choose the SSH public key authentication type, and I'll leave the rest of these values alone. On the disks tab, you can configure the operating system disk or add additional disks, but I'm gonna leave these default values and move on to the networking options. The VM requires a virtual network. You can choose an existing one that you may have already created, or you can create a new one while creating your VM. Make sure that a subnet is selected, and you'll also need a public IP to access your gateway. When creating a network security group, this image will use pre-configured rules, and we can see these by clicking Create new under the Configure Network Security Group dropdown. Under Inbound Rules, ports 80, 443, and 22 will automatically be open to all sources. I would recommend modifying these after you create your vm, and you can do that by navigating to the network security group service in Azure, and you can make sure that these are only exposed to the IP addresses that need to access them. You can click the X to leave this window.

[03:19] The next page has VM management options. Then the following page allows you to enable alerts and diagnostics. The advanced page allows you to specify custom configurations or scripts for your vm, and then the tags page lets you add key value pairs to your vm that lets you group like resources. Finally, once we're done with our configuration options, we can go to the review and create page, and as long as the validation passes and the settings look correct, we can click create. Since I chose to authenticate with an SSH key, it'll prompt me to download the private key and create a resource. So I'll go ahead and do that. You won't be able to download this key again, so make sure you keep it somewhere safe.

[04:12] Once it's finished deploying, I'll click Go to Resource to see the details of my new vm. In order to access my gateway webpage and commission my gateway, I'll need the IP address of my vm, which can be found under the Essentials section or in the Networking properties. If I hover over the public IP address under Essentials, an icon to copy to clipboard will appear. So I'll go ahead and copy, and I'll paste that into a new browser tab. Cloud Edition is configured to bind to ports 80 and 443, the default HTTP and HTTPS ports as opposed to a standard installation which binds the Port 8088 and 8043, by default. You shouldn't need to specify port 80, but it's important to know this difference from a standard Ignition installation. The commissioning phase for Cloud Edition is shorter than a standard installation, so all I need to do is create my administrator user credentials, and then I can click Finish Setup, and then Start Gateway.

[05:16] And now I have Ignition Cloud Edition installed and running in the cloud on an Azure VM.