New way of enriching MQTT messages using AWS IoT Core šØ
AWS added propagating attributes - contextual metadata from thing attributes or connection details.
What does it mean?
Previously, we had to configure and deploy IoT Rule to extract the
Client Id and include it into the MQTT Message Payload. I used it during various scenarios as it was a convenient way to enforce the tight security posture of IoT deployment.
According to AWS documentation, propagating attributes deliver the same enrichment without executing the IoT Rule. As a result, the operational cost of AWS IoT infrastructure should be reduced. šø
I have yet to test this feature. I'll be sure to share my findings with you in the future. š§
š What do you think about the recent changes to the AWS IoT service suite? To be honest, I am very positively surprised.
Please share your thoughts!
1 Reply
Same here, excited to try and use propagating attributes. What I understand is we can enrich IoT data by avoiding the complexity of managing republishing configuration and designing complex rule based system. I welcome this feature and looking forward to explore how MQTT5 users can use it. Happy to hear more on this. Thank's for the update!