Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Click the blue 'Create' button near the top of the screen. This will bring up the following Azure VM wizard to guide you through the Chariot MQTT Server VM creation.


Note
On the top portion of the Basics step, make sure to set Security type to Standard and the VM Image named standard - x64 Gen1 with the Chariot logo next to it. This will install the Cirrus Link provided Ubuntu Linux VM image with the Chariot MQTT Server preloaded. You do not have the option to chose another OS type via any other VM image provided.

It will take some time and within a few minutes the effective date and expiration date should get set. Once this is done, click the orange 'Continue to Configuration' button in the upper right section of the screen as shown below.

Image Removed

Now in the 'Fulfillment option' field, select 'CloudFormation Template' as shown below. This will set up the defaults including the 'Chariot MQTT Server Template' field, the version, and the region. Select your preference for the region also as shown below.

Image Removed

Now click the orange 'Continue to Launch' button in the upper right corner. This will bring up the following screen.

Image Removed

Finally, click the orange 'Launch' button shown in the screenshot above. This will bring up the CloudFormation stack creation page shown below. Note the template associated with the Chariot MQTT Server is automatically populated for you. This is also shown below.

Image Removed

Click 'Next' in the lower right in the screen capture above. This will bring up the stack configuration page shown below.

Image Removed

Set the following properties for the stack:

...

  • This is a friendly name that will allow you to easily identify the stack in your AWS account

...

  • The instance size to use for the deployment. Note the size will affect the costs associated with your deployment.

...

  • This is the EC2 keypair that you created at the beginning of this process. If you missed it, instructions to create it are here.

...

  • This is the IP address or addresses that will be whitelisted to allow SSH access to the EC2 instance. The example '0.0.0.0/0' will allow SSH access from anywhere. This is not recommended for production environments but will allow access from anywhere initially. This can be changed later as well. A more secure option would be to use your IP address. For example, '47.123.53.23/32' would be used if your IP address is '47.123.53.23'.

...

After setting the properties, click the 'Next' button in the lower right of the Window. This will bring up the following screen.

Image Removed


Configure anything else that may be required here. Generally, nothing must be set here given that the user you are logged in as has the permissions to create everything that will created as part of the Cloud Formation deployment. Also, the 'Roll back all stack resources' should be selected in case there is a failure in deployment. This will ensure no resources get created and left in place should any portion of the stack creation fail. After setting any additional configuration here, click the 'Next' button in the lower right corner. This will bring up the review screen as shown below.

Image Removed

Double-check the configuration and finally click 'Submit' in the bottom right corner of the screen to kick off the stack creation. You should now see the 'CREATE_IN_PROGRESS' status as shown below.

Image Removed

This will begin the stack deployment. You can check on the progress by clicking both the Events and Resources tab as shown below. Deployment takes a few minutes to complete. When it completes, you should see something similar to what is shown below with all of the resources showing 'CREATE_COMPLETE' for the status.

Image Removed

Deployments can fail for multiple reasons, including AWS account resource limitations. By clicking the 'Events' page, you can see more information about what failed during deployment.

If this happens during deployment, note the 'Status reason' column on the right side of the events tab. Typically, the following steps are necessary to resolve the issue.

  1. Delete the stack using the 'Delete' button at the top of the stack's page
  2. Resolve the issue resulting in the failure. Often these are AWS account resource limits. If so, request an AWS resource limit increase via an AWS support ticket.
  3. Repeat this procedure to deploy the stack.

After the AWS Infrastructure has been deployed via the AWS Marketplace 1-click procedure, the application must be configured. In order to configure the application, you must be able to access the Chariot MQTT Server Web UI using your web browser. Use the following URL and credentials to login into your Chariot MQTT Server Web UI:

We recommend changing your Chariot admin password upon first login.


More information on configuring the Chariot MQTT Server can be found here.

...