Now we enable the KEPServerEx device to send messages to the AWS IoT cloud. KepServer should now appear in the Devices list of your Greengrass group.
Be aware that this is the only step in the process when you can download keys (so make sure you download them here or you will have to create a new AWS IoT device).
Open the AWS IoT console and choose Greengrass, Groups, MyFirstGroup, and then Cores, you should see your core device:.The resources you create in these procedures should be created in the same AWS Region. The core device should be able to communicate with AWS IoT Core. If you followed the steps in the Getting Started modules, you should also have a Greengrass group (for example, MyFirstGroup) with one core device (for example, MyFirstGroup_Core) configured.
You should now have the AWS IoT Greengrass Core software running on a gateway.
Module 1: Environment Setup for AWS IoT Greengrass.Follow the instructions in the AWS IoT Greengrass Developer Guide to install AWS IoT Greengrass Core software on Linux or Rasberry Pi:.You can download and install the current JRE from here. For the Kepware IoT gateway to run, the server requires a working 32-bit JRE.
By the end of the post, you should have enough information to create a secure and reliable process for real-time industrial data so everyone from the shop floor to the top floor can make smarter decisions.įirst, we show you how to connect and configure KEPServerEX with AWS IoT Greengrass Core. In this blog post, we discuss how customers can address the industrial protocol challenges by using KepServerEX at the edge for industrial protocol conversion, AWS IoT Greengrass for edge processing, and AWS IoT for data ingestion into AWS. There might be many different devices on a manufacturing floor, each with its own protocol. When managing Industrial Internet of Things (IIoT) data, it can be challenging to collect and send this data to the cloud for processing and advanced analytics (for example, to predict quality or equipment failure).