Differences

This shows you the differences between two versions of the page.

--- iot:tutorial:aws-integration [2020/06/16 07:35] – [Create ES] atolstov
+++ iot:tutorial:aws-integration [2020/07/06 11:48] – atolstov
@@ Line 232: / Line 232: @@
 {{ iot:aws:wh:wh_test_via_mqttfx_connections.png?direct |}}
-For know, it is WebHMI can post the data from real devices to various AWS Things, visualise with QuickSight tool and store this data in DynamoDB with possibility to import as .csv file to S3 bucket for example.
+For know, it is WebHMI can post the data from real devices to AWS MQTT Client, which allow update to various AWS Thing's Shadow. The data could be visualised data with QuickSight tool and stored this data in DynamoDB with possibility to import as .csv file to S3 bucket for example.
@@ Line 309: / Line 309: @@
 **//Decimation code://**
 \\
-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>
 a1,a2,a3,a4 = 0,0,0,0
@@ Line 359: / Line 359: @@
 ==== Next steps ====
-==== Create ES ====
+==== Create visualisation environment ====
-To use Kibana visualisation firstly you need to have an ElasticSearch engine deployed on virtual machine. Fortunately, there is a detached Menu item in Analytics AWS Services group.
+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, there is a detached Menu item in Analytics AWS Services group.
 {{ :iot:tutorial:aws_es_service.png?direct |}}
 So, crete a new one instance with following settings.
 {{ :iot:tutorial:es_type.png?direct |}}
-Specify domain name and instance type(size, e.g. t2.small).
+Specify domain name and instance type (size, e.g. t2.small).
 {{ :iot:tutorial:es_domain.png?direct |}}
 Specify the access policy, the good practice is a public one, but there is should IP resctiction be specified.
@@ Line 383: / Line 384: @@
 At this moment, you will have access to Kibana plugin, the following link is provided above.
 {{ :iot:tutorial:es_kibana_loaded.png?direct |}}
+==== Create a DynamoDB to Elasticsearch bridge using Lambda function ====
 <del>
-) Create Lambda function, set up destinations, triggers and 2) test function successfully.
+) formulate the payload in JSON and clarify the DDBv2 rule
+) Create Lambda function, set up destinations, triggers
+) test function successfully.
 )check Kibana metric created.