Page History

...

• UUID.certificate.pem.crt
• UUID.private.pem.key
• AmazonRootCA1.pem

For this example we'll be using MQTT Engine. However, the steps are very similar for MQTT Transmission with regard to connection establishment. Using the Ignition Gateway Web UI, browse to the Igntion 'Config → MQTT Engine/Transmission settings page'. Now click the 'Certificates' tab as shown below:

Image Added

Now click the 'Create new Certificate' link. Then upload one of the three files previously downloaded when creating the IoT Core 'Thing'. Once completed, your Certificates page should look similar to the following with all three files.

Image Added

Now, click the 'Servers' tab as shown below.

Image Added

If you are only going to be connecting to AWS IoT Core, edit the existing 'Chariot SCADA' setting. Otherwise, create a new MQTT Server Setting. This should bring up the following page.

Image Added

Set the following.

• Name
  • AWS IoT Core
• URL
  • The URL that was captured from the AWS IoT Core setting page. It should be of the form: ssl://ENDPOINT_URL:8883
  • Example: ssl://a33fdj134jkj10-ats.iot.us-east-1.amazonaws.com:8883
• Username
  • Blank
• Password
  • Blank
  • Note if a password was previously set, make sure to click the 'Change Password' checkbox and ensure the password fields are empty
• CA Certificate File
  • The 'Root CA' that was downloaded from AWS IoT Core
• Client Certificate File
  • The 'Client Cert' that was downloaded from AWS IoT Core
• Client Private Key File
  • The 'Client Private Key' that was downloaded from AWS IoT Core.

Leave all other fields blank and submit the configuration. If everything was set up properly, the 'Status' should show 'Connected' when complete.

For MQTT Engine, you must also set the 'reordering timeout' due to timing issues related to IoT Core message delivery. To do this, set the Custom Properties on the MQTT Engine General tab to: { "reorderingTimeout" : 3000 } as shown below and save the changes. This will allow MQTT Engine to buffer messages and reorder them should they be delivered out of order within a 3 second window. Generally 3 seconds seems to be plenty of time for the reordering with AWS IoT Core.

Image Added