ApsaraMQ for RocketMQ Enterprise Platinum Edition instances use subscription billing. This topic describes how to create, upgrade or downgrade, renew, and unsubscribe from an instance.
Create an instance
Create an Enterprise Platinum Edition instance from the ApsaraMQ for RocketMQ console.
Log on to the ApsaraMQ for RocketMQ console. In the left-side navigation pane, click Instances. In the top navigation bar, select a region.
On the Instances page, click Create Instance and configure the following settings:
Parameter Value Instance Version V4.0 Instance Type Enterprise Platinum Edition Product Type Subscription (default)
Upgrade or downgrade configurations
Scale an existing Enterprise Platinum Edition instance up or down to match changing workloads.
Adjustable configurations
| Configuration | Description |
|---|---|
| Peak TPS | Maximum transactions per second |
| Maximum topics | Upper limit on topics |
| Message storage space | Total message storage capacity |
Changes take effect in the current subscription cycle.
Billing impact
| Operation | Billing |
|---|---|
| Upgrade | The system calculates the price difference. Pay the difference to complete the upgrade. |
| Downgrade | The system refunds the amount that exceeds the price of the new configuration. |
Availability impact
During an upgrade or downgrade, expect the following behavior:
| Impact | Details |
|---|---|
| Transient connections | Second-level transient connections may occur in the ApsaraMQ for RocketMQ console and each service node of the cluster. The automatic retry mechanism on clients handles these in most cases. However, exception logs are generated and message delay can occur. |
| Message duplication | Messages may be duplicated. Implement message idempotence in advance. For more information, see Message idempotence. |
| Resource management | Do not create, delete, or modify resources such as topics in the console. |
| HTTP access | For HTTP-based connections, transient connections or rejected requests may occur for less than 1 minute. Configure a reconnection mechanism on clients. |
Set up CloudMonitor to track instance status and metrics during the upgrade or downgrade. For more information, see Configure monitoring and alerting for risk warning.
Procedure
Log on to the ApsaraMQ for RocketMQ console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your instance resides.
On the Instances page, click the name of the target instance. In the upper-right corner of the Instance Details page, click Upgrade or Downgrade.
Renew an instance
Renewal applies only to Enterprise Platinum Edition instances. Choose between auto-renewal and manual renewal.
Auto-renewal
Auto-renewal keeps your instance running without manual intervention. Once enabled, the system renews the instance before it expires so that resources and data are preserved.
How auto-renewal works
| Behavior | Details |
|---|---|
| Trigger window | Auto-renewal is triggered nine days before the instance expires. If the first attempt fails, the system retries once a day until it succeeds or until one day before expiration. |
| Daily schedule | The renewal process starts at 08:00 (UTC+8) each day. An instance is typically renewed no later than 18:00 on the same day. |
| Activation delay | Auto-renewal is not triggered immediately after you enable it. It runs only at the scheduled times described above. |
Expiration time example: if an instance expires at 00:00 on December 11, the day before the expiration date starts at 00:00 on December 10, and the sixth day after the expiration date starts at 00:00 on December 17.
Timing requirements
Enable auto-renewal before the instance expires. Enabling it after expiration has no effect.
If you enable auto-renewal after 08:00 on the day before expiration, the renewal may not take effect in time. Enable auto-renewal well before the expiration date.
Enable auto-renewal
Select Auto-renewal when purchasing the instance.
Manual renewal
Manually renew an instance if auto-renewal is not enabled.
Limits
| Limit | Details |
|---|---|
| Instance expiration | An instance that has been expired for more than seven days cannot be renewed. |
| Renewal duration | One to nine months, one year, two years, or three years. |
Procedure
Log on to the ApsaraMQ for RocketMQ console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where your instance resides.
On the Instances page, click the name of the target instance. In the upper-right corner of the Instance Details page, click Renew.
Unsubscribe from an instance
Post-expiration behavior
The Post-expiration Action parameter controls what happens after an instance expires or is unsubscribed:
| Post-expiration Action value | Behavior |
|---|---|
| Delete Resource (default) | The instance and all its resources are deleted immediately. |
| Downgrade to Standard Edition | The instance is downgraded to Standard Edition and billed on a pay-as-you-go basis. For more information, see Change an instance from Enterprise Platinum Edition to Standard Edition. |
View or modify the Post-expiration Action parameter on the Instance Details page in the ApsaraMQ for RocketMQ console.
Refund rules
Enterprise Platinum Edition instances support partial refund. For details, see Rules for unsubscribing from resources.
Procedure
Go to the Unsubscriptions page in the Expenses and Costs console.
Set the Type parameter to Partial Refund and find the ApsaraMQ for RocketMQ instance.
Click Unsubscribe Resource in the Actions column and follow the on-screen instructions.