I'm taking a 15-minute look at their IoT developer guide (https://docs.aws.amazon.com/iot/latest/developerguide/what-is-aws-iot.html https://docs.aws.amazon.com

I'm taking a 15-minute look at their IoT developer guide (https://docs.aws.amazon.com/iot/latest/developerguide/what-is-aws-iot.html https://docs.aws.amazon.com/iot/latest/developerguide/what-i...) to get a feel for what, exactly, this service is providing. My guess is that they're trying to compete with Thingspeak, DeviceHub, etc. I'm not totally sure I'm capturing this right, because their documentation isn't great at "getting to the point", but here's my read: 1. Internet-connected stuff needs to be able to talk, so awsiot needs to support messaging. So it looks like they're currently offering http (publish only) and mqtt (bidirectional pub/sub). They give each awsiot account a unique IoT internet endpoint (some-random-string.iot.us-east-1.amazonaws.com), and then parse everything into a stored state in the cloud (that's the device "shadow") 2. Ideally you'd be doing this securely. awsiot appears to be generating its own x509 certs here, -- are they then an intermediate CA? Not clear on this. The documentation here is terribly vague and I have no idea what's going on. Not good for transparency. I can't even tell if they're forcing security, or if it's optional. 3. State management. awsiot cloud-stores the state of devices, allowing you to check them (or to issue commands to either from a third-party device like a phone app). 4. Communication between devices. They're claiming some kind of wholly undocumented authentication system for access to and control over device state. At any rate, they have a concept of device-based identity, and then based on that identity, devices are (or aren't) allowed to talk to each other. I've done some IoT development, and though it's a bit hard to tell by their terribly inadequate documentation, I'm pretty sure this is intended for enterprise developers with massive IoT product offerings and very high product volume. AWS is much too complicated for a lot of the small device manufacturers, at least the ones coming in from the hardware side. To use this scalably (especially given you can only access it from CLI) with reasonable product volumes is going to require a lot of setup scripting to register devices, and I don't think companies will be able to afford the tooling cost until they're enterprise-level.