aws-device-gateway-signed-url VS mqtt.org

There is also another option that doesn't seem to be documented; a pre-signed url! I found a library that does the trick perfectly. To control what the user can do you must create a IAM user for it with the right permissions on iot:Connect, iot:Subscribe, iot:Receive and iot:Publish and use that to sign the request. Your client can then simply connect to the pre-signed url and do it's thing. The pre-signed url is reusable for multiple users which means you can cache it on your CDN. Keep in mind this does give every user the same permissions but in some cases this is exactly what you need.

MQTT (optional): If you're aiming for advanced customization, familiarity with MQTT (a lightweight messaging protocol) will be beneficial for communicating between the toy and the server.

The MQTT protocol is widely used in IoT applications because of its simplicity and ability to connect different data sources to applications using a publish/subscribe model. While many MQTT brokers support persistent sessions and can store message history as long as an MQTT client is not available, there may be cases where data needs to be stored for a longer period. In such cases, it is recommended to use a time series database. There are many options available, but if you need to store unstructured data such as images, sensor data, or Protobuf messages, consider using ReductStore. It is a time series database specifically designed for storing large amounts of blob data and optimized for IoT and edge computing.

https://mqtt.org is more popular, but its more complex. You will unlikely write your own mqtt while you can easily write own stomp broker.

I wanted to share my latest package (published on NuGet) implementing the MQTT v5 protocol.

I jumped onto https://mqtt.org/ to try to answer my usual use-case question about non-Kafka messaging, which is: "Do the messages get saved anywhere so you can come back and read them later?" Still not entirely sure about it.

But I did see:

    This is why MQTT has 3 defined quality of service levels: 0 - at most once, 1- at least once, 2 - exactly once

rumqttd is a high performance, embeddable MQTT broker that we wrote in Rust. MQTT is extremely lightweight publish/subscribe messaging transport for the Internet of Things (IoT).