WebHMI Docs

User Tools

Site Tools

iot:aws:config:iot-core

Differences

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

Link to this comparison view

Next revision		Previous revision
iot:aws:config:iot-core [2020/06/11 13:52] – created atolstoviot:aws:config:iot-core [2020/06/12 12:16] (current) – ↷ Links adapted because of a move operation atolstov
Line 1: Line 1:
 ===== Configure AWS IoT Core =====  ===== Configure AWS IoT Core ===== 
-{{ :wiki:iot:aws:aws_console_no_login.png?direct |}}+{{ iot:aws:aws_console_no_login.png?direct |}}
 The AWS Management Console is a browser-based GUI for Amazon Web Services through which a customer can manage their cloud computing, cloud storage and other resources running on the Amazon Web Services infrastructure.  The AWS Management Console is a browser-based GUI for Amazon Web Services through which a customer can manage their cloud computing, cloud storage and other resources running on the Amazon Web Services infrastructure. 
 ==== Log in to your AWS Console ==== ==== Log in to your AWS Console ====
 To get started, sign up for an account on AWS or log in to your existing account at [[https://console.aws.amazon.com/|AWS Console]]. To get started, sign up for an account on AWS or log in to your existing account at [[https://console.aws.amazon.com/|AWS Console]].
-{{ :wiki:iot:aws:aws_console.png?direct |}}+{{ iot:aws:aws_console.png?direct |}}
 Then go to AWS IoT Core. Then go to AWS IoT Core.
-{{ :wiki:iot:aws:aws_console_iot_core.png?direct |}}+{{ iot:aws:aws_console_iot_core.png?direct |}}
 ==== Create a new 'Thing' ==== ==== Create a new 'Thing' ====
 AWS IoT Core refers to devices that connect to the platform as Things (as a unit of Internet of Things). AWS IoT Core refers to devices that connect to the platform as Things (as a unit of Internet of Things).
Line 13: Line 13:
 \\  \\ 
 Go to Manage, Things submenu and let's create a new Thing. Go to Manage, Things submenu and let's create a new Thing.
-{{ :wiki:iot:aws:aws_console_iot_create_thing_0.png?direct |}}+{{ iot:aws:aws_console_iot_create_thing_0.png?direct |}}
 Pick the single Thing to be created. Pick the single Thing to be created.
-{{ :wiki:iot:aws:cert:aws_console_iot_create_thing.png?direct |}}+{{ iot:aws:cert:aws_console_iot_create_thing.png?direct |}}
 Fill in the required fields, such as Thing's name. Remember that the name can't be changed. But Tags inside that Thing can be edited.  Fill in the required fields, such as Thing's name. Remember that the name can't be changed. But Tags inside that Thing can be edited. 
-{{ :wiki:iot:aws:cert:aws_console_iot_create_thing_1.png?direct |}}+{{ iot:aws:cert:aws_console_iot_create_thing_1.png?direct |}}
 At the moment it would be convenient to create a [[aws-integration#create_a_new_thing_type|Thing Type]] which is a template for new Things. \\  At the moment it would be convenient to create a [[aws-integration#create_a_new_thing_type|Thing Type]] which is a template for new Things. \\ 
 \\  \\ 
 Select the "one-click certificate creation". Select the "one-click certificate creation".
-{{ :wiki:iot:aws:cert:aws_console_iot_create_thing_cert.png?direct |}}+{{ iot:aws:cert:aws_console_iot_create_thing_cert.png?direct |}}
 As a result you should see notifications in the top-right corner about successfully created certificates. As a result you should see notifications in the top-right corner about successfully created certificates.
-{{ :wiki:iot:aws:cert:aws_console_iot_create_thing_cert_done.png?direct |}}+{{ iot:aws:cert:aws_console_iot_create_thing_cert_done.png?direct |}}
 Download and secure the following files. Download and secure the following files.
-Root CA selection and downloading will be shown [[:aws-integration#create_a_certificates|here]].+Root CA selection and downloading will be shown [[iot:tutorial:aws-integration#create_a_certificates|here]].
 ==== Create a new Thing Type ==== ==== Create a new Thing Type ====
 To effectively create a bunch of 'Things' the best practice is to create a template. Such a template is a 'Thing Type'. It is also a good representation of real-world devices of the same model. To effectively create a bunch of 'Things' the best practice is to create a template. Such a template is a 'Thing Type'. It is also a good representation of real-world devices of the same model.
Line 34: Line 34:
 \\  \\ 
    
-{{ :wiki:iot:aws:cert:aws_console_iot_cert_ca.png?direct |aws_console_iot_cert_ca}}+{{ iot:aws:cert:aws_console_iot_cert_ca.png?direct |aws_console_iot_cert_ca}}
 The last step is to activate Thing's certificate in the IoT console, Manage menu entry, Things, select the Thing and go to Security, select linked certificate and click Actions in top right corner and click "Activate". The last step is to activate Thing's certificate in the IoT console, Manage menu entry, Things, select the Thing and go to Security, select linked certificate and click Actions in top right corner and click "Activate".
  
  
-{{ :wiki:iot:aws:cert:aws_console_iot_cert_activate.png?direct |}}+{{ iot:aws:cert:aws_console_iot_cert_activate.png?direct |}}
 The certificate status in the top left corner must change to "ACTIVE". The certificate status in the top left corner must change to "ACTIVE".
-{{ :wiki:iot:aws:cert:aws_console_iot_cert_activated.png?direct |}}+{{ iot:aws:cert:aws_console_iot_cert_activated.png?direct |}}
  
 ==== Create a Policies ==== ==== Create a Policies ====
 To establish connection it is policies should be configured. To establish connection it is policies should be configured.
 If there is no policies during Thing creation generated, let's do this manually. If there is no policies during Thing creation generated, let's do this manually.
-{{ :wiki:iot:aws:policy:aws_console_iot_create_thing_cert_policy_no_foundh.png?direct |}}+{{ iot:aws:policy:aws_console_iot_create_thing_cert_policy_no_foundh.png?direct |}}
 Go to IoT Core Manage, select your Thing, then Secure, Policies. Let's create a new one. Go to IoT Core Manage, select your Thing, then Secure, Policies. Let's create a new one.
-{{ :wiki:iot:aws:policy:AWS_console_iot_create_thing_secure_no_policy.png?direct |}}+{{ iot:aws:policy:aws_console_iot_create_thing_secure_no_policy.png?direct |}}
 Use the following setting to test connection. Wildcard symbol **//*//** represents all of availiable ARNs and subaction such as "iot:Publish", "iot:Subcribe" etc. Use the following setting to test connection. Wildcard symbol **//*//** represents all of availiable ARNs and subaction such as "iot:Publish", "iot:Subcribe" etc.
-{{ :wiki:iot:aws:policy:AWS_console_iot_create_thing_secure_create_policy_best_practise.png?direct |}}+{{ iot:aws:policy:aws_console_iot_create_thing_secure_create_policy_best_practise.png?direct |}}
 So now it is created. So now it is created.
-{{ :wiki:iot:aws:policy:AWS_console_iot_create_thing_secure_create_policy_success.png?direct |}}+{{ iot:aws:policy:aws_console_iot_create_thing_secure_create_policy_success.png?direct |}}
 So going back to Thing, Certificate, Policies and select the policy that created. So going back to Thing, Certificate, Policies and select the policy that created.
-{{ :wiki:iot:aws:policy:aws_console_iot_create_thing_cert_policy_selected.png?direct |}}+{{ iot:aws:policy:aws_console_iot_create_thing_cert_policy_selected.png?direct |}}
 That's how it is should looks like at the final. That's how it is should looks like at the final.
-{{ :wiki:iot:aws:policy:AWS_console_iot_create_thing_cert_policy_attached.png?direct |}}+{{ iot:aws:policy:aws_console_iot_create_thing_cert_policy_attached.png?direct |}}
 ==== Interact with AWS IoT Device Shadow ==== ==== Interact with AWS IoT Device Shadow ====
  
Line 62: Line 62:
 This is the current state of AWS Thing's Shadow. It is representation of last reported state of Thing. It is strict formatted, to found out more follow the link: [[https://docs.aws.amazon.com/iot/latest/developerguide/device-shadow-document-syntax.html|AWS Shadow format]] This is the current state of AWS Thing's Shadow. It is representation of last reported state of Thing. It is strict formatted, to found out more follow the link: [[https://docs.aws.amazon.com/iot/latest/developerguide/device-shadow-document-syntax.html|AWS Shadow format]]
  
-{{ :wiki:iot:aws:shadow:aws_console_iot_shadow_arn.png?direct |}}+{{ iot:aws:shadow:aws_console_iot_shadow_arn.png?direct |}}
 The "Interact" tab is shows to us all of MQTT topics, so that we can see which metric we shound use to interact with and the responses read from. Also here is endpoint, it is MQTT broker address for our connection. The "Interact" tab is shows to us all of MQTT topics, so that we can see which metric we shound use to interact with and the responses read from. Also here is endpoint, it is MQTT broker address for our connection.
-{{ :wiki:iot:aws:shadow:aws_console_iot_interact_topics.png?direct |}}+{{ iot:aws:shadow:aws_console_iot_interact_topics.png?direct |}}
  
 ==== Test connection via PC client ==== ==== Test connection via PC client ====
Line 75: Line 75:
  
 In the end, this leads us to these settings in MQTT.fx to test the connection. In the end, this leads us to these settings in MQTT.fx to test the connection.
-{{ :wiki:iot:aws:cert:mqttfx_to_aws_settings.png?direct |}}+{{ iot:aws:cert:mqttfx_to_aws_settings.png?direct |}}
  
 Click the Apply and try to connect to AWS MQTT Broker. If settings are correct the connection will be established and indicator will be green.  Click the Apply and try to connect to AWS MQTT Broker. If settings are correct the connection will be established and indicator will be green. 
Line 81: Line 81:
 Let's test shadow change:  Let's test shadow change: 
 Copy the "...update" MQTT topic from [[http://docs.webhmi.com.ua/_media/wiki:iot:aws:shadow:aws_console_iot_interact_topics.png|Interact]] tab to "Publish" form.  Copy the "...update" MQTT topic from [[http://docs.webhmi.com.ua/_media/wiki:iot:aws:shadow:aws_console_iot_interact_topics.png|Interact]] tab to "Publish" form. 
-{{ :wiki:iot:aws:shadow:aws_console_iot_interact_topics_upd_topic_cr.png?direct |}}+{{ iot:aws:shadow:aws_console_iot_interact_topics_upd_topic_cr.png?direct |}}
 And construct the JSON formatted message to update the shadow.  And construct the JSON formatted message to update the shadow. 
 <code - MQTT Publish shadow update.json> <code - MQTT Publish shadow update.json>
Line 94: Line 94:
 } }
 </code> </code>
-{{ :wiki:iot:aws:shadow:mqttfx_to_aws_connected.png?direct |}}+{{ iot:aws:shadow:mqttfx_to_aws_connected.png?direct |}}
 In case of mistake in the JSON format it will be received to "...rejected" topic message: In case of mistake in the JSON format it will be received to "...rejected" topic message:
-{{ :wiki:iot:aws:shadow:mqttfx_subscribe_aws_console_iot_shadow_manual_upd_rejected.png?direct |}}+{{ iot:aws:shadow:mqttfx_subscribe_aws_console_iot_shadow_manual_upd_rejected.png?direct |}}
 When everything is configured well, the publish to "...update" topic will lead to "...update/accepted" message with retelling of your payload. When everything is configured well, the publish to "...update" topic will lead to "...update/accepted" message with retelling of your payload.
-{{ :wiki:iot:aws:shadow:mqttfx_subscribe_aws_console_iot_shadow_manual_upd_accepted.png?direct |}}+{{ iot:aws:shadow:mqttfx_subscribe_aws_console_iot_shadow_manual_upd_accepted.png?direct |}}
 So that, you can notice that Shadow is holds last manual reported state. So that, you can notice that Shadow is holds last manual reported state.
-{{ :wiki:iot:aws:shadow:aws_console_iot_shadow_changed.png?direct |}}+{{ iot:aws:shadow:aws_console_iot_shadow_changed.png?direct |}}
  
  
Line 110: Line 110:
  
 Go to AWS IoT Core, Act, Rules. By default, there is no any rules pre-created.  Go to AWS IoT Core, Act, Rules. By default, there is no any rules pre-created. 
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_no_rules.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_no_rules.png?direct |}}
 Click at "Create a rule", fill in Name. Be careful, it is unchangeable after the creation process.  Click at "Create a rule", fill in Name. Be careful, it is unchangeable after the creation process. 
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_create.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_create.png?direct |}}
  
 Just fill in the wildcard in the **SELECT** clause and topic in the **FROM**. In our case it is: Just fill in the wildcard in the **SELECT** clause and topic in the **FROM**. In our case it is:
Line 119: Line 119:
  
 By using wildcard symbol we skip the SQL processing, but we will consider it later. For now, click at "Add action". By using wildcard symbol we skip the SQL processing, but we will consider it later. For now, click at "Add action".
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_iot_republish.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_iot_republish.png?direct |}}
 To test action is working let's just republish the whole JSON payload in the another MQTT topic. Using SQL query it will be possible to filter and even reformat it. So that rule has potential power.  To test action is working let's just republish the whole JSON payload in the another MQTT topic. Using SQL query it will be possible to filter and even reformat it. So that rule has potential power. 
 Fill in a new for testing purposes MQTT topic just to republish the whole message. "''//iot-test//''" for example. Fill in a new for testing purposes MQTT topic just to republish the whole message. "''//iot-test//''" for example.
-{{ :wiki:iot:aws:act:AWS_IoT_Core_Thing_Act_create_republish_topic_name.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_create_republish_topic_name.png?direct |}}
 To be able to __publish__ messages it is a role should be applied with a policy that allows it attached. Click at "Create role" and fill in the name for it. It can be renamed, so do not think a lot, try to work out the namespace regular expressions and make the naming process systematic.  To be able to __publish__ messages it is a role should be applied with a policy that allows it attached. Click at "Create role" and fill in the name for it. It can be renamed, so do not think a lot, try to work out the namespace regular expressions and make the naming process systematic. 
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_iot_analytics_republish_role.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_iot_analytics_republish_role.png?direct |}}
 After the role created and appropriate policy attached, you will see the "Policy attached" label, which indicates that rule will work with this action and IAM will not prevent action according to this rule, in our case which is republishing message. After the role created and appropriate policy attached, you will see the "Policy attached" label, which indicates that rule will work with this action and IAM will not prevent action according to this rule, in our case which is republishing message.
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_iot_analytics_republish_policy_attached.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_iot_analytics_republish_policy_attached.png?direct |}}
  
 Also, to indicate that something went wrong, but the IAM configured well, let's create an //error action//, same republish but in an "//error MQTT branch//", such as ''iot-error''. Also, to indicate that something went wrong, but the IAM configured well, let's create an //error action//, same republish but in an "//error MQTT branch//", such as ''iot-error''.
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_iot_analytics_republish_error_rule.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_iot_analytics_republish_error_rule.png?direct |}}
 When those configurations are done, let's test it and pursue that it is working fine. When those configurations are done, let's test it and pursue that it is working fine.
 This time, we will use AWS MQTT Client, which can be found in IoT Core, Test. This time, we will use AWS MQTT Client, which can be found in IoT Core, Test.
 To start testing you need to subscribe to all of three topics that you use in your rule. It shound be ''iot-test'', ''iot-error'', and ''$aws/things/WebHMI_Dnipro_1/shadow**/update**'' topics. To start testing you need to subscribe to all of three topics that you use in your rule. It shound be ''iot-test'', ''iot-error'', and ''$aws/things/WebHMI_Dnipro_1/shadow**/update**'' topics.
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_iot_analytics_republish_rule_test.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_iot_analytics_republish_rule_test.png?direct |}}
 Test algorithm is to post JSON formatted message to ''.../update'' message and see that it is reposted either to ''iot-test'' or ''iot-error'' topics, which will indicate that rule is applied and actions triggered by rule is not prevented to execute according to IAM.  Test algorithm is to post JSON formatted message to ''.../update'' message and see that it is reposted either to ''iot-test'' or ''iot-error'' topics, which will indicate that rule is applied and actions triggered by rule is not prevented to execute according to IAM. 
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_republish_test.gif?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_republish_test.gif?direct |}}
 When to whole message is republished, so now you can configure SQL query filtering. To explicit define the type of the payload variables, you can use CAST function like this.  When to whole message is republished, so now you can configure SQL query filtering. To explicit define the type of the payload variables, you can use CAST function like this. 
 <code sql>SELECT cast(state.reported.number as DECIMAL) as digits,  <code sql>SELECT cast(state.reported.number as DECIMAL) as digits, 
Line 141: Line 141:
 FROM '$aws/things/WebHMI_Dnipro_1/shadow/update'</code> FROM '$aws/things/WebHMI_Dnipro_1/shadow/update'</code>
  
-{{ :wiki:iot:aws:act:AWS_IoT_Core_Thing_Act_SQL.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_sql.png?direct |}}
 As it is tested, let's get use of the data by guiding them to IoT Analytics. Click one more time at "Add action" button. As it is tested, let's get use of the data by guiding them to IoT Analytics. Click one more time at "Add action" button.
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_iot_analytics.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_iot_analytics.png?direct |}}
 Select "Quick create IoT Analytics recouses". Fill in the prefix, which will describe either you rule or the Thing to which that rule is applied.  Select "Quick create IoT Analytics recouses". Fill in the prefix, which will describe either you rule or the Thing to which that rule is applied. 
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_iot_analytics_settings.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_iot_analytics_settings.png?direct |}}
 By clicking at "Quick create" you will see that it is done so that you are can click "Add action".  By clicking at "Quick create" you will see that it is done so that you are can click "Add action". 
-{{ :wiki:iot:aws:act:aws_iot_core_thing_act_iot_analytics_resoursed_succeed.png?direct |}}+{{ iot:aws:act:aws_iot_core_thing_act_iot_analytics_resoursed_succeed.png?direct |}}
  
  
Line 162: Line 162:
 When it is done, open the IoT Analytics service and interact with data.  When it is done, open the IoT Analytics service and interact with data. 
 Click "New Analysis button" in the top-left corner. Click "New Analysis button" in the top-left corner.
-{{ :wiki:iot:aws:act:aws_iot_analytics_quicksight_dashboard_new_analysis.png?direct |}}+{{ iot:aws:act:aws_iot_analytics_quicksight_dashboard_new_analysis.png?direct |}}
 Then click "New data set". Then click "New data set".
-{{ :wiki:iot:aws:act:aws_iot_analytics_quicksight_dashboard_new_analysis_new_dataset.png?direct |}}+{{ iot:aws:act:aws_iot_analytics_quicksight_dashboard_new_analysis_new_dataset.png?direct |}}
 Pick the "AWS IoT Analytics" new dataset data source. Pick the "AWS IoT Analytics" new dataset data source.
-{{ :wiki:iot:aws:act:aws_iot_analytics_quicksight_dashboard_new_analysis_new_dataset_source.png?direct |}}+{{ iot:aws:act:aws_iot_analytics_quicksight_dashboard_new_analysis_new_dataset_source.png?direct |}}
 If it is the same with IoT Core region, such as USA, N.Virginia. (US-East-1) which is are free region at the time of writing, you will see that there is one source ready to import. Put the radio button and click "Create data source". If it is the same with IoT Core region, such as USA, N.Virginia. (US-East-1) which is are free region at the time of writing, you will see that there is one source ready to import. Put the radio button and click "Create data source".
-{{ :wiki:iot:aws:act:aws_iot_analytics_quicksight_dashboard_new_analysis_new_dataset_source_iot_analytics.png?direct |}}+{{ iot:aws:act:aws_iot_analytics_quicksight_dashboard_new_analysis_new_dataset_source_iot_analytics.png?direct |}}
  
 The next step will indicate how much storage is available. For the first time it is near 1 GB SPICE (disk quota) available. Click "Visualize". The next step will indicate how much storage is available. For the first time it is near 1 GB SPICE (disk quota) available. Click "Visualize".
-{{ :wiki:iot:aws:act:aws_iot_analytics_quicksight_dashboard_new_analysis_new_dataset_source_iot_analytics_import_finished.png?direct |}}+{{ iot:aws:act:aws_iot_analytics_quicksight_dashboard_new_analysis_new_dataset_source_iot_analytics_import_finished.png?direct |}}
 It is possible to create a various visualisation of your data. Look at the sample dashboard.  It is possible to create a various visualisation of your data. Look at the sample dashboard. 
-{{ :wiki:iot:aws:act:aws_iot_analytics_quicksight_dashboard.png?direct |}}+{{ iot:aws:act:aws_iot_analytics_quicksight_dashboard.png?direct |}}
  
 At that point, you can visualize the data from any reporting Thing. At that point, you can visualize the data from any reporting Thing.
Line 179: Line 179:
 DDB DDB
 To store the data and be able to query it, you would like to pull in the database. There is AWS DynamoDB integrated for that purpose. Let's create a blank table.  To store the data and be able to query it, you would like to pull in the database. There is AWS DynamoDB integrated for that purpose. Let's create a blank table. 
-{{ :wiki:iot:aws:act:ddb_create.png?direct |}}+{{ iot:aws:act:ddb_create.png?direct |}}
 It is primary key notion. It is like the main column in the table. The best practise it is SQL-timestamp-formatted-string with timestamp use as primary key. It is primary key notion. It is like the main column in the table. The best practise it is SQL-timestamp-formatted-string with timestamp use as primary key.
 As we do not have the timestamp in the sample data, the name will be used. As we do not have the timestamp in the sample data, the name will be used.
-{{ :wiki:iot:aws:act:ddb:DDB_create_settings.png?direct |}}+{{ iot:aws:act:ddb:ddb_create_settings.png?direct |}}
 This is the blank table. There is no any Items yet.  This is the blank table. There is no any Items yet. 
-{{ :wiki:iot:aws:act:ddb:DDB_created.png?direct |}}+{{ iot:aws:act:ddb:ddb_created.png?direct |}}
 Let's guide some data to DynamoDB. Go back to the Rule and "Add action" to it, with __"Split message into multiply columns of a DynamoDB table (DynamoDBv2)"__.  Let's guide some data to DynamoDB. Go back to the Rule and "Add action" to it, with __"Split message into multiply columns of a DynamoDB table (DynamoDBv2)"__. 
-{{ :wiki:iot:aws:act:ddb:aws_iot_core_thing_act_ddb_rule.png?direct |}}+{{ iot:aws:act:ddb:aws_iot_core_thing_act_ddb_rule.png?direct |}}
 Fill in the name, select Role and click "Update Role". The green label will indicate that everything is fine and IAM configured well. Fill in the name, select Role and click "Update Role". The green label will indicate that everything is fine and IAM configured well.
-{{ :wiki:iot:aws:act:ddb:aws_iot_core_thing_act_ddb_rule_policy_updated.png?direct |}}+{{ iot:aws:act:ddb:aws_iot_core_thing_act_ddb_rule_policy_updated.png?direct |}}
 The Rule should look like this. The Rule should look like this.
-{{ :wiki:iot:aws:act:ddb:aws_iot_core_thing_act_ddb.png?direct |}}+{{ iot:aws:act:ddb:aws_iot_core_thing_act_ddb.png?direct |}}
 This time, you can practice to post message through MQTT.fx or use AWS MQTT Client as you wish. The MQTT.fx client will be considered below. This time, you can practice to post message through MQTT.fx or use AWS MQTT Client as you wish. The MQTT.fx client will be considered below.
-{{ :wiki:iot:aws:act:ddb:mqttfx_publish_to_ddb.png?direct |}}+{{ iot:aws:act:ddb:mqttfx_publish_to_ddb.png?direct |}}
 In the final, you will see that you data appear in the your Table in Items tab, if everything is configured well.  In the final, you will see that you data appear in the your Table in Items tab, if everything is configured well. 
-{{ :wiki:iot:aws:act:ddb:ddb_items_added.png?direct |}}+{{ iot:aws:act:ddb:ddb_items_added.png?direct |}}
 Otherwise, you will see the ''iot-error'' reported an error with caused reason. That will help you to diagnose the problem and fix it.  Otherwise, you will see the ''iot-error'' reported an error with caused reason. That will help you to diagnose the problem and fix it. 
iot/aws/config/iot-core.1591883521.txt.gz · Last modified: 2020/06/11 13:52 by atolstov
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki