You can configure the Message Queue for MQTT to customize data flow from other Alibaba Cloud products to Message Queue for MQTT. This topic describes the principles and application scenarios of cross-product data inflows, and Message Queue for MQTT mapping to resources of other Alibaba cloud products.

How it works

To import data from other Alibaba cloud products, Message Queue for MQTT, you need to create a data inflow rule. This rule reads data from the Alibaba Cloud product that you have configured and pushes the data to the MQTT client by using the MQTT Protocol. In this way, the Alibaba Cloud product API is called directly to send data to the MQTT client.

Notice Currently, you can only set Message Queue for Apache RocketMQ data import Message Queue for MQTT.


Instruction delivery scenarios

The background control service deployed on the cloud sends commands to Message Queue for Apache RocketMQ, Message Queue for MQTT based on the configured rules, Message Queue for Apache RocketMQ To MQTT topics and then push the corresponding data to the target MQTT device.

Resource Mapping methods

Data flow rules are mapped at the granularity of Message Queue for MQTT the parent Topic of maxcompute, that is, the data of a resource of other Alibaba Cloud products can be imported to Message Queue for MQTT in the parent Topic of log service. You can use other extension properties to configure subtopics that are pushed by the MQTT protocol.

Table 1. Mapping
MQTT resources Other Alibaba Cloud products Other Alibaba cloud resources Packet definition
MQTT Topic Message Queue for Apache RocketMQ Message Queue for Apache RocketMQ The Topic Message structure mappings between Message Queue for MQTT and Message Queue for Apache RocketMQ


For more information about console operations, see Manage data inbound rules.