ApsaraMQ for MQTT:Changes in instance management

Change description

ApsaraMQ for MQTT V3.x.x implements independent data storage. After you purchase and activate an ApsaraMQ for MQTT instance of version 3.x.x, you can create resources on the instance without the need to bind the instance to other Alibaba Cloud services. You can better understand this matter when you send and receive messages by using only the MQTT protocol.

For more information, see Changes in resource use.

Operation changes in the console

Compared with ApsaraMQ for MQTT V2.x.x, ApsaraMQ for V3.x.x implements independent data storage. You do not need to bind an ApsaraMQ for MQTT instance to an ApsaraMQ for RocketMQ instance before you can use the ApsaraMQ for MQTT instance. The process for creating an ApsaraMQ for MQTT instance varies based on the version. The following section describes the creation processes. Screenshots are provided to help you better understand the process.

• V2.x.x

  1. Create an ApsaraMQ for MQTT instance

     After you create an ApsaraMQ for MQTT instance, you must bind the instance to an ApsaraMQ for RocketMQ instance. At this point, you cannot obtain the endpoint of the ApsaraMQ for MQTT instance.

  2. Bind the ApsaraMQ for MQTT instance to an ApsaraMQ for RocketMQ instance

     You must select the ApsaraMQ for RocketMQ instance to be bound.

• V3.x.x

  After you create an ApsaraMQ for MQTT instance of version 3.x.x, you can use the instance to send and receive messages without the need to bind the instance to an ApsaraMQ for RocketMQ instance.

  Note

  If you want to exchange data between ApsaraMQ for MQTT and other Alibaba Cloud services, you must create data exchange rules. For more information, see Data exchange across cloud services.

References

For more information about how to manage instances in the ApsaraMQ for MQTT console, see Manage instances.