aws-iot

问题 I am trying to configure AWS IoT to use with AWS Amplify. I always see error as " AMQJS0008I Socket closed. ” and CloudWatch says “ AUTHORIZATION_FAILURE ”. This is what I configured I AM policy for authenticated Cognito Identity Pool { "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [ "cognito-identity:*", "mobileanalytics:PutEvents", "cognito-sync:*", "iot:Connect", "iot:Publish", "iot:Subscribe", "iot:Receive", "iot:GetThingShadow", "iot

问题 I am working on a project to install 100+ nodes of temperature sensors in an area, all of which perform the same function. The data they publish is the sensor id and the reading. I am using AWS-IOT for the backend. Now, to do so, I think I will need to create 1 'thing' per node in aws-iot which I believe is extremely hard to maintain and unscalable. So my question here is, how to connect multiple nodes to same 'thing' in AWS-IOT so that the cluster is easy to manage. Is there any alternate

问题 I am working on a project to install 100+ nodes of temperature sensors in an area, all of which perform the same function. The data they publish is the sensor id and the reading. I am using AWS-IOT for the backend. Now, to do so, I think I will need to create 1 'thing' per node in aws-iot which I believe is extremely hard to maintain and unscalable. So my question here is, how to connect multiple nodes to same 'thing' in AWS-IOT so that the cluster is easy to manage. Is there any alternate

问题 I am working on a project to install 100+ nodes of temperature sensors in an area, all of which perform the same function. The data they publish is the sensor id and the reading. I am using AWS-IOT for the backend. Now, to do so, I think I will need to create 1 'thing' per node in aws-iot which I believe is extremely hard to maintain and unscalable. So my question here is, how to connect multiple nodes to same 'thing' in AWS-IOT so that the cluster is easy to manage. Is there any alternate

问题 I have two result topics where messages arrive from different sources "almost nearly at the same time". Topic: sensor1/result --receiving payload--> { "output_from_sensor1": {"result":"OK"} } Topic: sensor2/result --receiving payload--> { "output_from_sensor2": {"result":"OK"} } I would like to create an AWS IoT Rule which scans these two topics "simultaneously in one query" and take an action. I am not sure if AWS IoT SQL support "scanning multiple topics" in one query. No such references

问题 I'm trying to connect a NodeMCU ESP8266 and upload a shadow. I am following the tutorial from IoT Design Pro. When i first ran it, I did see the shadow updated on AWS. On subsequent loops, it stopped updating. Now i get a message "can't setup SSL connection". Here are my code and the serial output window: #include <ESP8266WiFi.h> #include <AmazonIOTClient.h> #include "ESP8266AWSImplementations.h" Esp8266HttpClient httpClient; Esp8266DateTimeProvider dateTimeProvider; AmazonIOTClient iotClient

问题 I am trying to understand Amazon AWS IoT and I see there is a Device Gateway connected between Sensors/Actuators and AWS (Rules Engine). I understand Sensors/Actuators are MQTT Clients which can Publish/Subscribe to the topics. Device Gateway also supports Publish/Subscribe pattern is that means Device Gateway is also a MQTT Client ? Then where is the MQTT broker? OR Device Gateway is Broker + communication interface to AWS-IoTservices? I have attached an Image Amazon presentation on AWS IoT

问题 I am trying to understand Amazon AWS IoT and I see there is a Device Gateway connected between Sensors/Actuators and AWS (Rules Engine). I understand Sensors/Actuators are MQTT Clients which can Publish/Subscribe to the topics. Device Gateway also supports Publish/Subscribe pattern is that means Device Gateway is also a MQTT Client ? Then where is the MQTT broker? OR Device Gateway is Broker + communication interface to AWS-IoTservices? I have attached an Image Amazon presentation on AWS IoT

问题 I am trying to use 'Authenticate using Cognito-Identity with Cognito user pool' in my Android application. My Cognito user pool authentication works well, when I run that separately and I had seen a JWTToken as well. When I run the the 'PubSub' sample application with Unauthenticated role, it worked as expected. When I integrate these two features in one application, the application threw following error. W/System.err: MqttException (0) - java.io.IOException: Already connected W/System.err:

问题 I want my backend to be able to directly send messages to authenticated users. Which means I need to limit the users to only subscribe on topics under their own identifiers. Ideally, to my currently limited understanding, I would have a policy that has the user sub as a variable: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "iot:Connect", "iot:Publish", "iot:Receive", "iot:GetThingShadow", "iot:UpdateThingShadow", "iot:DeleteThingShadow" ], "Resource": "*" }, {