This topic describes the release notes for Message Queue for RabbitMQ and provides links to the relevant references.
|Message sending||Sending messages in the Message Queue for RabbitMQ console is supported.||Added feature|
|New region||The Message Queue for RabbitMQ service is available in the India (Mumbai) region.||Added feature|
|Dashboard||Various metric data of Message Queue for RabbitMQ instances, vhosts, exchanges, and queues can be viewed in monitoring reports on the dashboard. This helps you identify and locate issues at the earliest opportunity.||Added feature|
|Enterprise Edition instance||Instances of Message Queue for RabbitMQ Enterprise Edition are added.
Compared with Professional Edition instances, Enterprise Edition instances provide higher specifications. For example, Enterprise Edition instances support larger message sizes. You can select an instance edition based on your business requirements.
|New region||The Message Queue for RabbitMQ service is available in the China (Guangzhou) region.||Added feature|
|Updated console||The Message Queue for RabbitMQ console is updated to improve user experience.||Optimized feature||
|Open source rabbitmq_delayed_message_exchange plug-in||The open source rabbitmq_delayed_message_exchange plug-in is supported for delayed message delivery. To use this feature, you can declare an x-delayed-message exchange. This frees you from installing the plug-in.||Added feature|
|New regions||Message Queue for RabbitMQ is available in the following seven regions:
|Management of static usernames and passwords||Static usernames and passwords can be managed by RAM users.
Important To use this feature, RAM users must be granted the required permissions.
|Monitoring and alerting||The following metrics are supported:
|Service-linked role||The following service-linked roles are supported:
||Added feature||Service-linked roles|
|Increased limits on the clusters for an instance||Limits on the clusters for an instance can be increased free of charge.||Added feature|
|Downgrade of an instance specification||Instance specifications can be downgraded.||Added feature||Manage instances|
|Management of static usernames and passwords||Static usernames and passwords can be created in the Message Queue for RabbitMQ console based on the AccessKey pair and instance ID. You can use the created static usernames and passwords to access Message Queue for RabbitMQ from an open source RabbitMQ client.||Added feature|
|Cleanup of messages in a queue||Messages in a queue can be cleared in the Message Queue for RabbitMQ console.||Added feature||Mange queues|
|Metadata migration||The metadata of a Message Queue for RabbitMQ cluster can be imported to an instance in the Message Queue for RabbitMQ console.||Added feature|
|Monitoring and alerting||The following metrics are added:
||Optimized feature||Monitoring and alerting|
|Monitoring and alerting||
||Optimized feature||Monitoring and alerting|
|JMS||The Java Message Service (JMS) 1.1 specification is supported. JMS applications can access Message Queue for RabbitMQ from the JMS client library of Message Queue for RabbitMQ.||Added feature|
|Monitoring and alerting||The unit of metrics except for Accumulated Queue Messages is changed from counts/minute
Important The values in this unit are approximate average values that are calculated at 15-second intervals.
|Optimized feature||Monitoring and alerting|
|Exchange creation||amq. cannot be used as the prefix of an exchange name because amq. is a reserved field.||Optimized feature||Manage exchanges|
|Queue creation||amq. cannot be used as the prefix of a queue name because amq. is a reserved field.||Optimized feature||Mange queues|
|ListQueueConsumers||The ListQueueConsumers API operation can be used to query the consumers of a queue.||Added feature||ListQueueConsumers|
|Basic Edition not supported||Basic Edition instances are no longer provided. The purchased Basic Edition instances are still available.||Removed feature||Manage instances|
|Resource plans not supported||Resource plans for the pay-as-you-go billing method are no longer provided. The purchased resource plans are still in effect.||Removed feature||None|
|Pay-as-you-go billing method||The pay-as-you-go billing method is not supported. The existing pay-as-you-go instances are still billed based on the pay-as-you-go method.||Removed feature||None|
|GetMetadataAmount||The GetMetadataAmount API operation can be used to query the metadata of an instance.||Added feature||GetMetadataAmount|
|Subscription billing method||The subscription billing method is supported. This method helps you estimate the required fees before you use the service.||Added feature||Overview|
|Instantiation||The resources are instantiated. This helps isolate resources among multiple tenants. Each user is assigned a pay-as-you-go instance that is shared across all regions.||Added feature||Manage instances|