2 Answers
- Newest
- Most votes
- Most comments
1
Hi Frank. I'm going to mention the device SDK again. It's what a device, implemented in Java, would normally use.
Stepping outside of Java, we have similar samples in most of our other-language device SDKs. We also have the Device Client: https://github.com/awslabs/aws-iot-device-client
You can use pretty much any MQTT client though. You could even use mosquitto_pub: https://manpages.debian.org/testing/mosquitto-clients/mosquitto_pub.1.en.html
0
Thanks, I have that and I think I see how it can work with certificates. I guess that when a thing updates it's "shadow" it's just posting to a queue with a reserved name, correct? Does the "thing" need to tell its own name to IoT or does IoT figure that out from its certificate?
answered 2 years ago
Relevant content
- asked 2 months ago
- asked 5 months ago
- asked 5 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
The reserved topic includes the thing name, e.g. $aws/things/THING_NAME/shadow/update