# AWS MQTT Broker vs Cirrus Link MQTT Ignition Broker Module

**URL:** <https://forum.inductiveautomation.com/t/aws-mqtt-broker-vs-cirrus-link-mqtt-ignition-broker-module/49156>\
**Category:** Ignition\
**Created:** [July 23, 2021, 8:58pm UTC](https://forum.inductiveautomation.com/t/aws-mqtt-broker-vs-cirrus-link-mqtt-ignition-broker-module/49156 "2021-07-23T20:58:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 23, 2021, 9:10pm UTC](https://forum.inductiveautomation.com/t/aws-mqtt-broker-vs-cirrus-link-mqtt-ignition-broker-module/49156/2 "2021-07-23T21:10:53Z")

</div>

I’ve seen @wes0johnson explicitly recommend _not_ using AWS IoT because it doesn’t work properly with the CL modules: [What MQTT Versions Does Ignition Support? - #3 by wes0johnson](https://forum.inductiveautomation.com/t/what-mqtt-versions-does-ignition-support/46473/3)

---

_[View the full topic](https://forum.inductiveautomation.com/t/aws-mqtt-broker-vs-cirrus-link-mqtt-ignition-broker-module/49156)._