# Creating an MQTT bridge via PubSub+ Cloud

**URL:** <https://community.solace.com/t/creating-an-mqtt-bridge-via-pubsub-cloud/2041>\
**Category:** Solace Event Broker\
**Tags:** solace-cloud, mqtt, bridge, broker, solacepubsub\
**Created:** [October 4, 2024, 9:33am UTC](https://community.solace.com/t/creating-an-mqtt-bridge-via-pubsub-cloud/2041 "2024-10-04T09:33:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mo\_ben\_massey](https://avatars.discourse-cdn.com/v4/letter/m/e36b37/32.png) [@mo\_ben\_massey](https://community.solace.com/u/mo_ben_massey)\
**Post date:** [October 4, 2024, 9:33am UTC](https://community.solace.com/t/creating-an-mqtt-bridge-via-pubsub-cloud/2041/1 "2024-10-04T09:33:39Z")

</div>

Hi everyone.

We’re looking to utilise MQTT bridges on our event broker which is deployed on the PubSub+ Cloud. We’ve read up about the MQTT connector and wondered if this is possible to utilise for the cloud-deployed event broker via the Mission Control’s Cluster Manager in some way, or if we need to take a different approach?

> **[MQTT | PubSub+ Integration Hub | Solace](https://solace.com/integration-hub/mqtt-bridge-connector/)**
>
> This Micro-Integration enables the flow of messages both from an MQTT broker endpoint to a PubSub+ endpoint and from PubSub+ to MQTT. MQTT is an OASIS

Thanks. ?

---

<div class="post-metadata">

**Author:** ![amackenzie](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/amackenzie/32/1168_2.png) [@amackenzie](https://community.solace.com/u/amackenzie)\
**Post date:** [October 4, 2024, 11:24am UTC](https://community.solace.com/t/creating-an-mqtt-bridge-via-pubsub-cloud/2041/2 "2024-10-04T11:24:04Z")

</div>

Hello,

PubSub+ doesn’t support MQTT server-to-server bridges and external MQTT brokers cannot be part of an event mesh cluster.

The MQTT connector integrates a PubSub+ queue/topic with an MQTT broker topic using 2 clients, an SMF client on the PubSub+ side and an MQTT Paho client on the MQTT broker side. The source client acts as a consumer and the target client acts as a publisher.

---

<div class="post-metadata">

**Author:** ![Aaron](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/aaron/32/843_2.png) [@Aaron](https://community.solace.com/u/Aaron)\
**Post date:** [October 16, 2024, 4:49am UTC](https://community.solace.com/t/creating-an-mqtt-bridge-via-pubsub-cloud/2041/3 "2024-10-16T04:49:16Z")

</div>

So it’s like a “software bridge”… a client app connected to both sides? But the MQTT connector / micro-integration component can be run in the cloud, right? And at some point will/can be fully managed by Solace, as a “CaaS” (connector as a service? haha), correct?