[00:00] In this lesson, I'll demonstrate how to create an AWS EC2 instance preloaded with Ignition Cloud Edition. Before I get started with the EC2 instance, I need to create a network, or VPC, in AWS for the instance to reside in. This allows me to configure the isolated part of the AWS Cloud were my instance is so that I can control who has access to it and ensure that I have access myself. Within the VPC service in AWS, I'll click create VPC. If I were to select VPC only, I'd have to go and manually create each other component of the network to fit my needs. This gives me ultimate control over the network and lets me customize it to my liking. However, to keep this lesson brief, I'm gonna choose the VPC and more option as this will automatically create public and private subnets, routing tables, and an internet gateway so that I can quickly connect to my device. Check out AWS's documentation, to learn more about networking resources in AWS. I'll quickly name the resources in this VPC. Then, I'll leave the rest of the options at the defaults and click create VPC.

[01:05] But just know that this network can be configured differently. Now that I have a VPC for my installation, I can head over to the EC2 service and I'll click launch instance. This form is gonna let me start configuring my instance. First, I'll give it a name. Then I need to choose the AMI for this instance, AMIs are templates that contain operating systems and applications for instantiating an EC2 instance. I'm gonna click this browse more AMIs option to search for the cloud edition AMI. I'll change tabs to AWS marketplace AMIs to search the marketplace listings, and I'll type ignition into the search bar. Ignition Cloud Edition by Inductive Automation should show up, and I can click the select button. In order to use this AMI, I'll need to subscribe to it, which can be done from this popup window. You can click these tabs to learn more about things like pricing and usage info, but I'm ready to click subscribe.

[02:06] Now once it's subscribed, the EC2 instance will be configured to start up with Ubuntu in Ignition Cloud Edition preloaded, and I can continue with the rest of the form. Choosing the correct instance type is going to depend on the needs of your application, and you can change that through this dropdown, but I'm gonna keep mine at this default selection. If you've created a key pair with an AWS, you can use it to securely connect to your instance, or you can proceed without one. Click edit to the right of network settings to make sure that these settings are correct. I'm gonna confirm that the VPC is set to the one I just created, which was tchaney-ignition-project. I also wanna make sure that this is put into one of my public subnets. Then I want to enable auto-assign public ip. The default option is to create a security group, which I'll leave this on, and it'll automatically create security rules to expose ports 80 and 443. If you end up using an existing security group, make sure that those are configured correctly on your end.

[03:06] The source type lets me configure the IP addresses that can access this port. I'm just gonna choose to expose this to all IP addresses, again for simplicity, but I'd highly recommend setting this up to only allow connections from IP addresses that you know and trust. Under configure storage, I can see the volumes that are associated with my instance and how much data they can store. The root volume is for the operating system data and this EBS volume here is for the ignition data. On First Startup, the AMI is going to automatically link the ignition data folder to this volume for you. If I expand advanced details, this allows me to specify even more options for this instance, such as Recovery Options, what the instance does when it stops, and down at the bottom, I can add scripts to the user data field if I wanted to insert some commands for the instance to run when it's created. I'm gonna leave everything else on the default values and I'll click Launch instance on the right. Once the instance is running, I can click it for more information.

[04:06] I'll wanna find the public IPv4 address, or public DNS record. I can copy that and I'll open a new tab and paste it. Normally, the default ignition port of a standard install would be port 8088, but the AMIs configured to start up with Port 80, so I'll add that and hit enter. If you're using SSL, the Cloud Edition port will be 443 instead of 8043. The commissioning phase for cloud edition is shorter and will only prompt you for the admin username and password, so I'll create a user real quick. Once it's done starting up, you can see that I now have my own cloud edition installation. Once you have your network carefully set up to be as secure as it can be while still providing the proper Access Ignition Cloud Edition can quickly and easily be set up.