Page History

Export the Chariot configuration through the Chariot Web UI from the left hand menu under System > Backup/Restore
If configured for SSL, copy Download/backup the certificates from the existing instance of the Chariot MQTT Server for AWS or Azure as listed below:
Chariot Private Key located in /opt/chariot/conf/rsa_key.p8

Chariot Certificates located in /opt/chariot/certs/* if you have any certificates in this folder

ssl.jks keystore from <OLD_chariot_install_folder>/security directory

Deploy the latest version of the AWS Chariot MQTT Server or Azure Chariot MQTT Server
Stop the Chariot MQTT Server service on the existing instance of the Chariot MQTT Server
For Chariot MQTT Server versions version 2.4.1 and newer
sudo systemctl stop chariot
For IoT Bridge for Snowflake Chariot MQTT Server versions prior to 2.4.1
sudo /etc/init.d/chariot stop
Copy the backed up config from Step 1 above to the new instance of the Chariot MQTT Server created in Step 2
If configuring SSL, copy ssl.jks keystore from Step 2 to <NEW_chariot_install_folder>/security
Warning
If you fail to do the copy BEFORE you start Chariot for the first time, the certs will not get picked up dynamically.
Start the Chariot MQTT Server service on the new instance of the Chariot MQTT Server created in Step 23
For Chariot MQTT Server version 2.4.1 and newer
sudo systemctl start chariot
For Chariot MQTT Server versions prior to 2.4.1
sudo /etc/init.d/ibsnow startchariot start
Restore the backed up config from Step 1 above to the new instance of the Chariot MQTT Server using the Chariot Web UI from the left hand menu under System > Backup/Restore
Confirm clients can connect successfully Confirm clients are able to successfully connect to the new instance of the Chariot MQTT Server created in Step 2
Stop and terminate/delete the old instance of the Charot Chariot MQTT Server.

Versions Compared