#8 Are AWS IoT core, Azure IoT hub or Google Cloud supported?

None
2021-05-16
2021-02-05
h-hermsen
No

No support for non compliant MQTT v3.1.1 server/services

The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub and Google Cloud IoT Core is that
they are NOT 100% MQTT v3.1.1 compliant.

Usage of Sparkplug for MQTT demands a 100% MQTT v3.1.1 compliant server/service.
Key concepts of the Sparkplug standard like retained Server STATE messages, will not work in such an environment. Because of the lacking compliancy we cannot support any NON compliant MQTT v3.1.1 compatible MQTT servers or cloud services.

AWS, Microsoft and Google lack support of even basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These basic MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are mandatory (not optional). This means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are fully compliant to the full MQTT v3.1.1 specification.

If you are using AWS, Azure Or Google Cloud infrastructure, a possibility is to host a self built VM in AWS, Azure or Google Cloud which leverages the service. A sidestep could be to go for a Mosquitto cloud server or HiveMQ Cloud which is now free for 100 clients + 10GB/Month + No SLA.

Amazon AWS IoT core non compliancy statement

https://docs.aws.amazon.com/iot/latest/developerguide/mqtt.html

MQTT is a lightweight and widely adopted messaging protocol that is designed for constrained devices. AWS IoT support for MQTT is based on the MQTT v3.1.1 specification, with some differences. For information about how AWS IoT differs from the MQTT v3.1.1 specification, see AWS IoT differences from MQTT version 3.1.1 specification.

See https://docs.aws.amazon.com/iot/latest/developerguide/mqtt.html#mqtt-differences for further details.

Microsoft Azure IoT hub non compliancy statement

https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support

IoT Hub is not a full-featured MQTT broker and does not support all the behaviors specified in the MQTT v3.1.1 standard. This article describes how devices can use supported MQTT behaviors to communicate with IoT Hub.

Google Cloud IoT core non compliancy statement

https://cloud.google.com/iot/docs/requirements#mqtt_bridge

This page lists Cloud IoT Core requirements and related information.

MQTT version 3.1.1 is required.

The following features are not supported:

MQTT QoS 2
Arbitrary MQTT topics and subscriptions. For topic requirements, see the section on connecting devices using MQTT
Last Will and Testament (LWT)
Retained messages
Persistent sessions

Answers

  • h-hermsen

    h-hermsen - 2021-02-05
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,4 @@
    -# No, we do not support any non 100% compliant MQTT v3.1.1 server/service
    +# No, we can not support any non 100% compliant MQTT v3.1.1 server/service
     The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub or Google Cloud IoT Core is that they are NOT 100% MQTT v3.1.1 compliant. AWS, Microsoft and Google lack support of basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are not optional but mandatory, which means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are compliant to the MQTT specification.
    
     Usage of Sparkplug for MQTT demands a 100% MQTT v3.1.1 compliant server /service. So, because of the lacking compliancy we decided that we will NOT support any NON compliant MQTT v3.1.1 compatible MQTT servers or cloud service. 
    
    • status: --> open
     
  • h-hermsen

    h-hermsen - 2021-02-05
    • summary: Support for AWS IoT core, Azure IoT hub or Google Cloud supported? --> Are AWS IoT core, Azure IoT hub or Google Cloud supported?
     
  • h-hermsen

    h-hermsen - 2021-02-05
    • labels: --> Sparkplug, aws, iot, azure, google, cloud, hub, mqtt, v3.1.1, compliancy, non, core
     
  • h-hermsen

    h-hermsen - 2021-02-05
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,4 @@
    -# No, we can not support any non 100% compliant MQTT v3.1.1 server/service
    + # Sadly we can not support any non 100% compliant MQTT v3.1.1 server/service
     The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub or Google Cloud IoT Core is that they are NOT 100% MQTT v3.1.1 compliant. AWS, Microsoft and Google lack support of basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are not optional but mandatory, which means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are compliant to the MQTT specification.
    
     Usage of Sparkplug for MQTT demands a 100% MQTT v3.1.1 compliant server /service. So, because of the lacking compliancy we decided that we will NOT support any NON compliant MQTT v3.1.1 compatible MQTT servers or cloud service. 
    
     
  • h-hermsen

    h-hermsen - 2021-02-05
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,5 @@
      # Sadly we can not support any non 100% compliant MQTT v3.1.1 server/service
    + 
     The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub or Google Cloud IoT Core is that they are NOT 100% MQTT v3.1.1 compliant. AWS, Microsoft and Google lack support of basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are not optional but mandatory, which means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are compliant to the MQTT specification.
    
     Usage of Sparkplug for MQTT demands a 100% MQTT v3.1.1 compliant server /service. So, because of the lacking compliancy we decided that we will NOT support any NON compliant MQTT v3.1.1 compatible MQTT servers or cloud service. 
    
     
  • h-hermsen

    h-hermsen - 2021-02-05
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,4 @@
    - # Sadly we can not support any non 100% compliant MQTT v3.1.1 server/service
    + #Sadly we can not support any non 100% compliant MQTT v3.1.1 server/service
    
     The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub or Google Cloud IoT Core is that they are NOT 100% MQTT v3.1.1 compliant. AWS, Microsoft and Google lack support of basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are not optional but mandatory, which means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are compliant to the MQTT specification.
    
     
  • h-hermsen

    h-hermsen - 2021-02-05
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,4 @@
    - #Sadly we can not support any non 100% compliant MQTT v3.1.1 server/service
    +#Sadly we can not support any non 100% compliant MQTT v3.1.1 server/service
    
     The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub or Google Cloud IoT Core is that they are NOT 100% MQTT v3.1.1 compliant. AWS, Microsoft and Google lack support of basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are not optional but mandatory, which means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are compliant to the MQTT specification.
    
     
  • h-hermsen

    h-hermsen - 2021-02-05
    • labels: core, non, google, Sadly, hub, iot, aws, mqtt, Sparkplug, v3.1.1, compliancy, azure, cloud --> core, non, google, hub, iot, aws, mqtt, Sparkplug, v3.1.1, compliancy, azure, cloud
     
  • h-hermsen

    h-hermsen - 2021-02-05
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,6 +1,6 @@
     #Sadly we can not support any non 100% compliant MQTT v3.1.1 server/service
    
    -The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub or Google Cloud IoT Core is that they are NOT 100% MQTT v3.1.1 compliant. AWS, Microsoft and Google lack support of basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are not optional but mandatory, which means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are compliant to the MQTT specification.
    +The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub or Google Cloud IoT Core is that they are NOT 100% MQTT v3.1.1 compliant. AWS, Microsoft and Google lack support of basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are not optional but mandatory, which means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are fully compliant to the MQTT specification.
    
     Usage of Sparkplug for MQTT demands a 100% MQTT v3.1.1 compliant server /service. So, because of the lacking compliancy we decided that we will NOT support any NON compliant MQTT v3.1.1 compatible MQTT servers or cloud service. 
    
     
  • h-hermsen

    h-hermsen - 2021-02-05
    • labels: core, non, google, hub, iot, aws, mqtt, Sparkplug, v3.1.1, compliancy, azure, cloud -->
    • status: open --> wont-fix
     
  • h-hermsen

    h-hermsen - 2021-02-06
    • status: wont-fix --> open
     
  • h-hermsen

    h-hermsen - 2021-02-28
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,11 +1,12 @@
    -#Sadly we can not support any non 100% compliant MQTT v3.1.1 server/service
    - 
    -The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub or Google Cloud IoT Core is that they are NOT 100% MQTT v3.1.1 compliant. AWS, Microsoft and Google lack support of basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are not optional but mandatory, which means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are fully compliant to the MQTT specification.
    +# no support for non compliant MQTT v3.1.1 server/services
    +The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub and Google Cloud IoT Core is that they are **NOT 100% MQTT v3.1.1 compliant**.
    
    -Usage of Sparkplug for MQTT demands a 100% MQTT v3.1.1 compliant server /service. So, because of the lacking compliancy we decided that we will NOT support any NON compliant MQTT v3.1.1 compatible MQTT servers or cloud service. 
    +Usage of Sparkplug for MQTT **demands** a 100% MQTT v3.1.1 compliant server/service.
    +Key concepts of the Sparkplug standard like retained Server STATE messages, will not work in such an environment. Because of the lacking compliancy we cannot support any NON compliant MQTT v3.1.1 compatible MQTT servers or cloud services.
    
    -Some of the key concepts of the Sparkplug standard (e.g. retained Server STATE messages) will not work. If you are stuck with AWS, Azure Or Google Cloud infrastructure, a sidestep could be to go for a Mosquitto server.
    +AWS, Microsoft and Google lack support of even basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These basic MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are mandatory (not optional). This means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are fully compliant to the full MQTT v3.1.1 specification.
    
    +If you are using AWS, Azure Or Google Cloud infrastructure, a sidestep could be to go for a Mosquitto cloud server.
    
     ## Amazon AWS IoT core non compliancy statement
    
     
  • h-hermsen

    h-hermsen - 2021-02-28
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,4 @@
    -# no support for non compliant MQTT v3.1.1 server/services
    +# No support for non compliant MQTT v3.1.1 server/services
     The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub and Google Cloud IoT Core is that they are **NOT 100% MQTT v3.1.1 compliant**.
    
     Usage of Sparkplug for MQTT **demands** a 100% MQTT v3.1.1 compliant server/service.
    
     
  • h-hermsen

    h-hermsen - 2021-02-28
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,5 +1,6 @@
     # No support for non compliant MQTT v3.1.1 server/services
    -The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub and Google Cloud IoT Core is that they are **NOT 100% MQTT v3.1.1 compliant**.
    +The key issue with Amazon AWS IoT core, Microsoft Azure IoT hub and Google Cloud IoT Core is that 
    +they are **NOT 100% MQTT v3.1.1 compliant**.
    
     Usage of Sparkplug for MQTT **demands** a 100% MQTT v3.1.1 compliant server/service.
     Key concepts of the Sparkplug standard like retained Server STATE messages, will not work in such an environment. Because of the lacking compliancy we cannot support any NON compliant MQTT v3.1.1 compatible MQTT servers or cloud services.
    
     
  • h-hermsen

    h-hermsen - 2021-05-16
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -7,7 +7,7 @@
    
     AWS, Microsoft and Google lack support of even basic MQTT features such as QoS 2, Retained Messages and guaranteed message ordering. These basic MQTT features are often used to implement business critical systems. In fact, in order to be MQTT compliant these features are mandatory (not optional). This means neither AWS nor Microsoft Azure IoT Hub or Google Cloud are fully compliant to the full MQTT v3.1.1 specification.
    
    -If you are using AWS, Azure Or Google Cloud infrastructure, a sidestep could be to go for a Mosquitto cloud server.
    +If you are using AWS, Azure Or Google Cloud infrastructure, a possibility is to host a self built VM in AWS, Azure or Google Cloud which leverages the service. A sidestep could be to go for a Mosquitto cloud server or HiveMQ Cloud which is now free for 100 clients + 10GB/Month + No SLA. 
    
     ## Amazon AWS IoT core non compliancy statement
    
     

Log in to post a comment.