Differences

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

--- iot:tutorial:aws-integration [2020/06/15 13:52] – atolstov
+++ iot:tutorial:aws-integration [2020/06/15 15:37] – atolstov
@@ Line 273: / Line 273: @@
 The next step is to reconfigure MQTT topics from ''iot-test'' to Thing's Shadow ''.../update'' topic.
 {{ :iot:aws:wh:wh_to_aws_update_and_trigger.png?direct |}}
-This will lead the message to IoT Core Rules processing, and in the end hitting to DynamoDB table.
+There is a trigger to run script, by the register's value change to post a message to AWS.
 {{ :iot:aws:wh:wh_to_aws_update_scripts.png?direct |}}
+This settings will lead the message to AWS IoT Core Rules processing, and in the end hitting to DynamoDB table.
 ==== Setting up trigger script  ====
-There should be a trigger to change the register's value to post a message to AWS.
+There should be a trigger to change the register's value to post a message to AWS, because of too short duration of scan and superfluity of update frequincy for cloud data processing.
-{{ :iot:aws:wh:wh_to_aws_update_triggered.png?direct |}}
 For the testing purpose you can do this manually.
+{{ :iot:aws:wh:wh_to_aws_update_triggered.png?direct |}}
+After that, check the DynamoDB Table's Item append.
 {{ :iot:aws:wh:ddb_update.gif?direct |}}
 When you ensure, that data comes to DynamoDB triggered by auxilary WebHMI register change, you can set up the trigger's toggle by script.
@@ Line 355: / Line 358: @@
 </code>
-Create ES
+==== Next steps ====
+==== Create ES ====
+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.
+{{ :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).
+{{ :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.
+{{ :iot:tutorial:es_security.png?direct |}}
+[[https://www.myip.com/|To check IP use myip.com]].
+{{ :iot:tutorial:es_myip_blur.com.png?direct |}}
+The first line has your current IP.
+As a CIDR block you can rewrite you IP as XXX.XXX.XXX.XXX/16, where 16 is a number or bit, that can be changed to still satisfy the condition, so that will form a IP adresses range, which will protect your from ISP pool IP mascarading.
+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.
+{{ :iot:tutorial:es_review.png?direct |}}
+After the creation, in several minutes it will be endpoint adress created
+{{ :iot:tutorial:es_success_loading.png?direct |}}
+Wait until it would be done.
+{{ :iot:tutorial:es_active.png?direct |}}
+At this moment, you will have access to Kibana plugin, the following link is provided above.
+{{ :iot:tutorial:es_kibana_loaded.png?direct |}}
 check Kibana metric created.
 Work with Kibana