iot:tutorial:aws-integration
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| iot:tutorial:aws-integration [2020/07/07 13:25] – Unfinished DDB, Lambda atolstov | iot:tutorial:aws-integration [2021/07/22 07:32] (current) – ↷ Links adapted because of a move operation atolstov | ||
|---|---|---|---|
| Line 238: | Line 238: | ||
| ==== JSON formatted payload ==== | ==== JSON formatted payload ==== | ||
| It is widely used MQTT payload format JSON. | It is widely used MQTT payload format JSON. | ||
| - | Let’s write a small script which will use inbuild [[: | + | Let’s write a small script which will use inbuild [[lua: |
| Here is the code example to encode a string type message with Amazon Web Services (AWS) [[https:// | Here is the code example to encode a string type message with Amazon Web Services (AWS) [[https:// | ||
| Line 420: | Line 420: | ||
| Append to DDB should triggers that new Lambda function, which will repost the data to ElasticSearch instance. To check it, just go to Kibana and click search button. If there is no data in one minute after posting from WH, so something get wrong. The more likely with IAM. There is a CloudWatch logs to investigate problem. | Append to DDB should triggers that new Lambda function, which will repost the data to ElasticSearch instance. To check it, just go to Kibana and click search button. If there is no data in one minute after posting from WH, so something get wrong. The more likely with IAM. There is a CloudWatch logs to investigate problem. | ||
| - | <del> | ||
| - | __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 (demo visualisation)</ | ||
iot/tutorial/aws-integration.1594128302.txt.gz · Last modified: 2020/07/07 13:25 by atolstov