AWS Tutorials - Understanding Device Shadow Service in AWS IoT Core

A device shadow is a JSON document that is used to store and retrieve device state information. The device shadow is associated with AWS IoT thing object. Any application or service which wants to know the device state; can access the device shadow irrespective whether the device is connected to AWS IoT or not. Shadow communications use request/response model using the publish/subscribe communication model of MQTT. Every shadow action consists of a request topic, a successful response topic (accepted), and an error response topic (rejected).

In this workshop, you perform update, get and delete actions on the device shadow document using MQTT based communication. You will use MQTT client as part of AWS IoT Service to complete the workshop.

[anupamapeddi]

I am literally searching for this. Thank u

[undercrackers]

Thank you. Your video does a good job of explaining WHAT AWS IoT Shadows are for. I am confused at HOW it does it. If AWS IoT is using MQTT protocol then all nodes will Publish (send) data or Subscribe (be open to receiving) data. My understanding is that when a device reconnects after being disconnected it does not "request" anything. It is merely listening (Subscribed) to any messages Published to a particular topic. It would be the job of the MQTT Broker to retain a messages and transmit them when Subscribers registered for that topic are connected. Does AWS IoT work differently to standard MQTT? Can anyone answer please?

[ag]

So do IOT devices need to publish telemetry data to Shadown topics and not the actual topics ? can someone clear my doubt here. :(

[karmadipdodiya]

One question: Do we need to create separate things for each devices?
i.e i have 10 same kind of devices, then i need to create 10 thing or i can use <deviceID> in topic.

[abeehahussain]

Dear sir can you make a video how to send and receive data from device shadow to Desktop based application i.e. C#