iot:tutorial:aws-integration
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
iot:tutorial:aws-integration [2020/06/15 13:44] – [__Ensure, that data comes to DDB.__ by WH register change, using auxiliary register.] atolstov | iot:tutorial:aws-integration [2020/07/06 11:48] – atolstov | ||
---|---|---|---|
Line 232: | Line 232: | ||
{{ iot: | {{ iot: | ||
- | For know, it is WebHMI can post the data from real devices to various | + | For know, it is WebHMI can post the data from real devices to AWS MQTT Client, which allow update to various AWS Thing' |
Line 268: | Line 268: | ||
===== Testing and Next Steps ===== | ===== Testing and Next Steps ===== | ||
- | ==== To make it possible to post to AWS Broker set up topic for mqtt_pubslish as update and mqtt_get as get. (fix topic' | + | ==== Testing |
Okay, so now it is working AWS MQTT communication and tested successfully. | Okay, so now it is working AWS MQTT communication and tested successfully. | ||
The next step is to reconfigure MQTT topics from '' | The next step is to reconfigure MQTT topics from '' | ||
{{ : | {{ : | ||
- | This will lead the message | + | There is a trigger |
{{ : | {{ : | ||
+ | This settings will lead the message to AWS IoT Core Rules processing, and in the end hitting to DynamoDB table. | ||
+ | |||
==== Setting up trigger script | ==== Setting up trigger script | ||
- | There should be a trigger to change the register' | + | There should be a trigger to change the register' |
+ | For the testing purpose you can do this manually. | ||
{{ : | {{ : | ||
+ | After that, check the DynamoDB Table' | ||
{{ : | {{ : | ||
+ | When you ensure, that data comes to DynamoDB triggered by auxilary WebHMI register change, you can set up the trigger' | ||
+ | |||
As an example there is two practices such as time dependent (oscillator) or quantity depended (decimation) trigger. \\ | As an example there is two practices such as time dependent (oscillator) or quantity depended (decimation) trigger. \\ | ||
| | ||
**// | **// | ||
If there is a neccesity to post with predefined frequency, for example 15 second can be done with following script. | If there is a neccesity to post with predefined frequency, for example 15 second can be done with following script. | ||
+ | |||
<code lua> | <code lua> | ||
a1,a2,a3,a4 = 0,0,0,0 | a1,a2,a3,a4 = 0,0,0,0 | ||
Line 302: | Line 309: | ||
**// | **// | ||
\\ | \\ | ||
- | If there is several target register, such us (//counter, counter2, etc.//), but if it changes too often, this code will help to decimate the output trigger signal. | + | If there is several target register, such as //counter, counter2, etc.//, but if it changes too often, this code will help to decimate the output trigger signal. |
<code lua> | <code lua> | ||
a1,a2,a3,a4 = 0,0,0,0 | a1,a2,a3,a4 = 0,0,0,0 | ||
Line 351: | Line 358: | ||
</ | </ | ||
- | Create | + | ==== Next steps ==== |
- | check Kibana metric created. | + | ==== Create |
- | Work with Kibana | + | To use Kibana visualisation firstly you need to run an ElasticSearch engine deployed on virtual machine. |
+ | So the idea is to create ElasticSearch Instance with Kibana plugin on-board. | ||
+ | Fortunately, | ||
+ | {{ : | ||
+ | So, crete a new one instance with following settings. | ||
+ | {{ : | ||
+ | Specify domain name and instance type (size, e.g. t2.small). | ||
+ | {{ : | ||
+ | Specify the access policy, the good practice is a public one, but there is should IP resctiction be specified. | ||
+ | {{ : | ||
+ | [[https:// | ||
+ | {{ : | ||
+ | The first line has your current IP. | ||
+ | As a CIDR block you can rewrite you IP as XXX.XXX.XXX.XXX/ | ||
+ | Otherwise, copy your IP to field as is. | ||
+ | \\ | ||
+ | In the end, this will lead your to this settings. Review it and confirm creation if it fine. | ||
+ | {{ : | ||
+ | After the creation, in several minutes it will be endpoint adress created | ||
+ | {{ : | ||
+ | Wait until it would be done. | ||
+ | {{ : | ||
+ | At this moment, you will have access to Kibana plugin, the following link is provided above. | ||
+ | {{ : | ||
+ | ==== Create a DynamoDB to Elasticsearch bridge using Lambda function ==== | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | 0) formulate the payload in JSON and clarify the DDBv2 rule | ||
+ | 1) Create Lambda function, set up destinations, | ||
+ | |||
+ | 2) test function successfully. | ||
+ | |||
+ | 3)check Kibana metric created. | ||
+ | |||
+ | 4) Work with Kibana | ||
iot/tutorial/aws-integration.txt · Last modified: 2021/07/22 07:32 by atolstov