# MQTT Broker combinations

**URL:** <https://forum.inductiveautomation.com/t/mqtt-broker-combinations/97948>\
**Category:** Ignition\
**Created:** [October 30, 2024, 11:50am UTC](https://forum.inductiveautomation.com/t/mqtt-broker-combinations/97948 "2024-10-30T11:50:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Henrique\_Santos](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/henrique_santos/32/69139_2.png) [@Henrique\_Santos](https://forum.inductiveautomation.com/u/Henrique_Santos)\
**Post date:** [October 30, 2024, 11:50am UTC](https://forum.inductiveautomation.com/t/mqtt-broker-combinations/97948/1 "2024-10-30T11:50:37Z")

</div>

Hi everyone,

I was reading the articles on architecture options and I got a little confused at the [Subscriber part](https://www.docs.inductiveautomation.com/docs/8.1/system-architectures/iiot-architecture#subscriber)

Am I able to use a MQTT-enabled device with the Distributed module? Or does the distributed module only works with Ignition Edge MQTT?

I'm thinking about the red line possibility:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/2/f2d20e680402b5645f5435ec6604ae9eb8227c55.jpeg)

This is my first topic so if I'm messing with the rules of the forum, please let me know.

---

<div class="post-metadata">

**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\
**Post date:** [October 30, 2024, 12:02pm UTC](https://forum.inductiveautomation.com/t/mqtt-broker-combinations/97948/2 "2024-10-30T12:02:31Z")

</div>

Welcome to the forum.

I'm not an Architect level IIOT guru (yet), but my thoughts are you would go:

MQTT publishing with SparkPlug B -\> Broker -\> Ignition Server with Engine.

If you move your red line above the 3rd party broker, then it would be Broker -\> Engine.

You need minimum one Edge node, to a broker, and finally Ignition full edition with Engine so that Ignition can make sense of that data.

So far as it is all talking a common language on the wire (e.g. SparkPlug B), then you can go Edge IIOT (Transmission) to e.g. AWS Broker (3rd party) to Ignition Engine.

---

<div class="post-metadata">

**Author:** ![TChenier](https://avatars.discourse-cdn.com/v4/letter/t/d6d6ee/32.png) [@TChenier](https://forum.inductiveautomation.com/u/TChenier)\
**Post date:** [October 30, 2024, 1:46pm UTC](https://forum.inductiveautomation.com/t/mqtt-broker-combinations/97948/3 "2024-10-30T13:46:56Z")

</div>

Distributor is an MQTT v3.1.1 compliant broker. It will work with any client/device that follows that version of specification.

So, yes, you can connect non-Ignition-Edge devices to Distributor.