The modern industrial world is getting highly specialized — companies hone in their expertise based on core competencies and outsource the rest. You can hardly expect any complex product to originate from a single manufacturer. The Boeing 787’s 2.3 million parts come from 5400 suppliers around the globe! Same is true in the virtual (or software) world.
In this article, we will connect a tracking device manufactured by Galileosky in Russia, to the US-based Amazon Web Services through the flespi platform developed in Belarus.
But before we go any further, let’s clarify why we need this. Think of the standard features of a modern telemetry device:
The above set of requirements is not abstract — it is a partial tech-specs list for Galileosky devices. Yesterday’s unique and advanced features are the must-have of today. And proactive companies are on the look-out for new goodies that will impress the customers tomorrow. One of the promising directions for GPS hardware manufacturers is integrability into third-party platforms.
Here are the perks that Amazon cloud can add to your tracker’s functionality:
Now, let’s start connecting a Galileosky device to AWS. To make it more exciting, consider the following scenario. We have a remote server-room, where we are going to set up access control and temperature monitoring. We install there a Galileosky tracker with a 1-wire temperature sensor and iButton lock. What advantages can we get from the Galileosky → flespi → AWS union?
The overall goal here is to connect a physical Galileosky tracker to the flespi platform via a channel over the galileosky protocol. Use the flespi panel to walk through the next actions:
See a more detailed step-by-step guide with screenshots in a flespi test drive article.
Now that we have the avatar of out Galileosky tracker in the flespi platform, most setup will take place on the Amazon side. Open AWS IoT section of the AWS console. To configure a valid entry point for MQTT stream from flespi follow these steps:
Click Register a thing button on the Manage things tab and type a thing name.
thing-private.pem.keycertificates to later use for MQTT stream setup
AWS policies allow to manage permissions for different things. We can simply grant full permissions for testing purposes. It looks like:
4. Attach thing and policy to the certificate
NOTE: there is a shortcut for the above four steps. You can simply click the Onboard tab and select Get started button in Configuring a device section. Then follow intuitive steps to have your device set up.
Now we’ve got everything to set up an AWS stream for our flespi device:
If done right, you will see the updated thing shadow and will be able to subscribe to MQTT topic from your device. Now you can see all Galileosky device parameters in the thing shadow and read live messages by subscription to the MQTT topic.
Now let’s set up some notifications for our server monitoring device. This is how to set up rule specification with AWS SQL-like language:
The list of possible actions is really long, so you can write very flexible and specific rules.
For testing let’s pick SQS (Simple Queue Service) — it allows setting up simple messages queue in a couple of clicks and receiving live messages if the rule triggers. We’ll use the following SQL-like rule to monitor our server room ibutton access:
Where 164446398 is allowed code and 0 is a default value if no keys were used (for regular messages). “<>” is a NOT EQUAL sign. It is possible to use many operations in SQL-like rules; the full list is available in AWS documentation.
Conclusions and benefits
As a result, we can conclude that a high-level solution based on high-quality Galileosky hardware with popular and flexible Amazon Web Services through flespi platform takes just mouse clicks and a few fast and clear operations.
More broadly this case illustrates how flespi helps eliminate boundaries for hardware manufacturers:
Stay tuned for more practical cases. Use us to open new horizons for your business.