0
We are building an Industrial IoT solution which for some connectivity reasons needs to communicate with the MQTT Broker using TCP 443.
We already do this with a RabbitMQ broker which works well but needs to have a consumer to push into an EventHub.
We would like to migrate onto a IoTHub Solution which is totally integrated in the Azure Environnement but are facing a problem with this incoming TCP Port.
Azure IoTHub allows incoming connections as follows:
- MQTT on Port 8883
- MQTT over WebSocket on Port 443.
- And some more connections with AMQP
Unfortunately the Industrial Device we do use is not compatible with WebSockets.
I thought about using some Firewall/Load Balancer NAT rules to redirect incoming TCP Connections on 443 to IoTHub's 8883.... Only solutions I found are only limited to redirect onto VMs, not the IoT Hub.
If someone has an idea, that would be great!