You are now ready to connect to the MQTT Broker in AWS.ġ5. Enter the name and select MQTT Client. In my example, I’m using AWSMQTT as the name.ġ6. Navigate to the AWS IOT Platform and select Certificatesġ1. Select the Certificates by clicking itġ2. Select Policies and click Actions > Attach Policyġ3. Select the Policy created earlier and click attach Supply these actions (or * for everything) and click create if you are creating a new one.ġ0.
KEPWARE IOT GATEWAY DOWNLOAD
To download the rootCa, right click > Save as > your preferred locationĨ. Select an existing policy that enables iot:connect, iot:receive, iot: publish, and iot:subscribe or choose Create a new policyĩ. Note: This is the only chance to download the private key, it is inaccessible after creation. By default, AWS signs their certificate with a Symantec root certificate that is trusted by windows so you don’t need the root certificate in most cases. Note the endpoint and copy it somewhere.Ī.comĦ. Click Create certificate under One-click certificate.ħ. Download the thing certificate and private key. The primary method to connect to AWS is through MQTT and here’s the stepsģ. The following section will assume you already have machines or assets already connected and are ready to send the data to AWS. Traditionally, we are leveraged and well known as an OPC Server. This guide assumes you are familiar with Kepware (but if you are not, Kepware’s flagship product KEPServer EX allows you to connect data from industrial assets like sensors, PLCs, CNC machines and many more.
The aim of this guide is to provide you a step-by-step instructions to send data from Kepware to AWS.