Features
ApsaraDB for MongoDB supports three instance architectures: replica set, sharded cluster, and standalone. Each architecture supports specific MongoDB versions and instance categories. Use this page to check feature availability for your instance configuration.
-
ApsaraDB for MongoDB stopped selling new Serverless (Provisioned) instances on July 11, 2022. For more information, see [Notice] ApsaraDB for MongoDB stops selling new Serverless (Provisioned) instances.
MongoDB 3.4 is discontinued. Instances running MongoDB 3.4 have been unavailable since January 1, 2023. For details, see Notice: End of sale for MongoDB 3.4 instances as of January 1, 2023.
Storage capacity, instance architecture, and storage engine cannot be changed in place. To decrease storage capacity, switch architectures, or change the storage engine, create a new instance. For details, see Change the configurations of an instance.
In the tables below,
means supported and
means not supported.
Instance architectures, versions, and categories
The instance category determines resource allocation. Cloud disk-based instances (MongoDB 4.4 and later) and local disk-based instances (MongoDB 4.2 and earlier) offer different category options.
| Instance architecture | Version | General-purpose (cloud disks) | Dedicated (cloud disks) | General-purpose (local disks) | Dedicated (local disks) | Dedicated host |
|---|---|---|---|---|---|---|
| Replica set instance | MongoDB 8.0 | |||||
| MongoDB 7.0 | ||||||
| MongoDB 6.0 | ||||||
| MongoDB 5.0 | ||||||
| MongoDB 4.4 | ||||||
| MongoDB 4.2 | ||||||
| MongoDB 4.0 | ||||||
| MongoDB 3.4 (discontinued) | ||||||
| Sharded cluster instance | MongoDB 8.0 | |||||
| MongoDB 7.0 | ||||||
| MongoDB 6.0 | ||||||
| MongoDB 5.0 | ||||||
| MongoDB 4.4 | ||||||
| MongoDB 4.2 | ||||||
| MongoDB 4.0 | ||||||
| MongoDB 3.4 (discontinued) | ||||||
| Standalone instance | MongoDB 4.0 | |||||
| MongoDB 3.4 (discontinued) |
Billing management
Manage billing method switches and subscription renewals.
Replica set instance
|
Feature |
MongoDB 8.0 |
MongoDB 7.0 |
MongoDB 6.0 |
MongoDB 5.0 |
MongoDB 4.4 |
MongoDB 4.2 |
MongoDB 4.0 |
MongoDB 3.4 |
|
|
Dedicated (Cloud Disk) |
General-purpose (Local Disk) Dedicated (Local Disk) Dedicated Physical Server |
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Sharded cluster instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Switch from pay-as-you-go to subscription | ||||||||
| Switch from subscription to pay-as-you-go | ||||||||
| Manually renew a subscription instance | ||||||||
| Enable auto-renewal |
Standalone instance
| Feature | 4.0 | 3.4 |
|---|---|---|
| Switch from pay-as-you-go to subscription | ||
| Switch from subscription to pay-as-you-go | ||
| Manually renew a subscription instance | ||
| Enable auto-renewal |
Instance management
Create, configure, upgrade, and manage instance lifecycles. Major version upgrades are not available for MongoDB 8.0 (already the latest) or 4.2. Standalone instances do not support version upgrades, zone migration, or node role switching.
Replica set instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 (discontinued) |
|---|---|---|---|---|---|---|---|---|
| Create a replica set instance | ||||||||
| Change instance configurations | ||||||||
| Enable or disable release protection | ||||||||
| Specify a maintenance window | ||||||||
| Configure database parameters | ||||||||
| Restart an instance, component, or node | ||||||||
| Release an instance | ||||||||
| Recycle bin | ||||||||
| Update the minor version | ||||||||
| Upgrade the major version | ||||||||
| Migrate to a different zone | ||||||||
| Trigger a primary/secondary switchover / Switch node roles |
Sharded cluster instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 (discontinued) |
|---|---|---|---|---|---|---|---|---|
| Create a sharded cluster instance | ||||||||
| Change instance configurations | ||||||||
| Enable or disable release protection | ||||||||
| Specify a maintenance window | ||||||||
| Configure database parameters | ||||||||
| Restart an instance, component, or node | ||||||||
| Release an instance | ||||||||
| Recycle bin | ||||||||
| Update the minor version | ||||||||
| Upgrade the major version | ||||||||
| Migrate to a different zone | ||||||||
| Configure a primary/secondary switchover / Switch node roles |
Standalone instance
Event management
View, manage, and subscribe to scheduled events and event notifications. Not supported for MongoDB 3.4.
Replica set instance
|
Feature |
MongoDB 8.0 |
MongoDB 7.0 |
MongoDB 6.0 |
MongoDB 5.0 |
MongoDB 4.4 |
MongoDB 4.2 |
MongoDB 4.0 |
MongoDB 3.4 |
|
|
Dedicated cloud disk edition |
General-purpose local disk edition Dedicated local disk edition Dedicated physical server |
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Standalone instance
| Feature | 4.0 | 3.4 (discontinued) |
|---|---|---|
| View and manage scheduled events / Subscribe to event notifications / Query historical events |
Tag management
Create, bind, filter by, and remove tags for organizing instances. Supported across all versions and architectures.
Replica set instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Create tags / Add existing tags / Use tags to filter instances / Remove or delete tags |
Standalone instance
| Feature | 4.0 | 3.4 |
|---|---|---|
| Create tags / Add existing tags / Use tags to filter instances / Remove or delete tags |
Serverless instance
|
Feature |
MongoDB 4.2 |
|
|
Account management
Manage database accounts through Data Management (DMS) or the mongo shell, and reset passwords. Supported across all versions and architectures.
Replica set instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Use DMS to manage database accounts | ||||||||
| Use the mongo shell to manage database accounts / Reset the password |
Sharded cluster instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Use DMS to manage database accounts | ||||||||
| Use the mongo shell to manage database accounts / Reset the password |
Standalone instance
| Feature | 4.0 | 3.4 |
|---|---|---|
| Use DMS to manage database accounts | ||
| Use the mongo shell to manage database accounts / Reset the password |
Connection management
Manage public and private endpoints, modify connection settings, and switch between classic network and VPC. Classic network features are available only for MongoDB 4.2 and earlier (local disk instances).
Replica set instance
Sharded cluster instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Apply for a public endpoint / Release a public endpoint (Not supported by DynamoDB-compatible instances.) | ||||||||
| Apply for a shard or ConfigServer endpoint / Release a shard or ConfigServer endpoint (Not supported by DynamoDB-compatible instances.) | ||||||||
| Modify the endpoint and port | ||||||||
| Switch from classic network to VPC / Configure hybrid access | ||||||||
| Change the retention period of classic network internal endpoints |
Standalone instance
Backup and restoration
Configure automatic and manual backups, download backup files, and restore data. For sharded cluster instances, database-level restoration requires MongoDB 4.4 or later.
Sharded cluster instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Configure automatic backup / Configure manual backup | ||||||||
| Download backup files | ||||||||
| Restore databases | ||||||||
| Restore to a new instance by point in time |
Standalone instance
| Feature | 4.0 | 3.4 |
|---|---|---|
| Configure automatic backup / Configure manual backup | ||
| Download backup files | ||
| Restore to a new instance by backup point |
Monitoring and alerting
Monitor instance metrics, configure alert rules, and set up alert callbacks. Supported across all versions and architectures.
Replica set instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Basic monitoring / Configure a threshold-triggered alert rule / Create an event-triggered alert rule / Manage alert rules / View alert history / Alert callback | ||||||||
| Delete alert rules / Disable alert rules |
Sharded cluster instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Basic monitoring / Configure a threshold-triggered alert rule / Create an event-triggered alert rule / Manage alert rules / View alert history / Alert callback | ||||||||
| Delete alert rules / Disable alert rules |
Standalone instance
Data security
Configure IP address whitelists, security groups, audit logs, SSL encryption, Transparent Data Encryption (TDE), and disk encryption. Disk encryption is available only for MongoDB 4.4 and later (cloud disk instances). SSL encryption is not supported for sharded cluster instances running MongoDB 4.2 and earlier. Standalone instances do not support audit logs, SSL, or TDE.
Replica set instance
Sharded cluster instance
Standalone instance
Log management
View slow query logs, operational logs, and error logs. Not available for standalone instances.
Replica set instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| View slow query logs / View operational logs / View error logs |
Standalone instance
| Feature | 4.0 | 3.4 |
|---|---|---|
| View slow query logs / View operational logs / View error logs |
CloudDBA
Use CloudDBA for performance diagnostics: performance trends, real-time monitoring, instance sessions, slow query analysis, and storage analysis. Standalone instances support only performance trends. Storage analysis is not available for MongoDB 3.4.
Standalone instance
| Feature | 4.0 | 3.4 |
|---|---|---|
| Performance trends | ||
| Real-time performance / Instance sessions | ||
| Storage analysis / Slow query logs |
Data migration
Migrate data from self-managed databases, third-party cloud services (MongoDB Atlas, Amazon DynamoDB), or between ApsaraDB for MongoDB instances. Migration to self-managed databases is available only for MongoDB 4.2 and earlier (local disk instances) on replica set instances and is not supported for sharded cluster instances. Cross-account migration for sharded clusters is available only for MongoDB 4.0.
Replica set instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Migrate from an ECS-hosted self-managed database | ||||||||
| Migrate from a self-managed replica set database by using Data Transmission Service (DTS) | ||||||||
| Migrate using mongodump and mongorestore | ||||||||
| Migrate from third-party cloud: MongoDB Atlas (mongodump/mongorestore) / MongoDB Atlas (DTS) / Amazon DynamoDB (NimoShake) | ||||||||
| Migrate from a standalone instance to a replica set or sharded cluster instance | ||||||||
| Between ApsaraDB for MongoDB instances: Replica set to sharded cluster / Cross-account / Cross-region | ||||||||
| Migrate to a self-managed database: Logical backup / Physical backup |
Sharded cluster instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Migrate from self-managed databases by using DTS: ECS-hosted sharded cluster / Self-managed sharded cluster | ||||||||
| Migrate using mongodump and mongorestore | ||||||||
| Migrate from third-party cloud: MongoDB Atlas (mongodump/mongorestore) / MongoDB Atlas (DTS) / Amazon DynamoDB (NimoShake) | ||||||||
| Cross-account migration | ||||||||
| Cross-region migration | ||||||||
| Migrate to a self-managed database: Logical backup / Physical backup |
Standalone instance
| Feature | 4.0 | 3.4 |
|---|---|---|
| Migrate from self-managed databases by using DTS: ECS-hosted standalone/replica set / Self-managed standalone (DTS) | ||
|
Migrate a database from a third-party cloud to ApsaraDB for MongoDB: Migrate a Huawei Cloud Document Database Service (DDS) database to ApsaraDB for MongoDB using DTS |
|
|
| Migrate using mongodump and mongorestore | ||
| Between ApsaraDB for MongoDB instances: Standalone to replica set/sharded cluster / Cross-account / Cross-region | ||
| Migrate to a self-managed database: Logical backup / Physical backup |
Serverless instances
|
Feature |
MongoDB 4.2 |
|
Migrate a self-managed database to ApsaraDB for MongoDB using DTS. |
|
|
Migrate a self-managed database to ApsaraDB for MongoDB using MongoDB tools. |
|
|
Migrate a database from a third-party cloud to ApsaraDB for MongoDB. |
|
|
Migrate data between ApsaraDB for MongoDB instances: Migrate data from a replica set instance to a sharded cluster instance |
|
|
Migrate data from an ApsaraDB for MongoDB instance to a self-managed MongoDB database. |
|
Data synchronization
Synchronize data between ApsaraDB for MongoDB instances by using Data Transmission Service (DTS) or MongoShake. MongoShake one-way synchronization is not available for MongoDB 8.0 and 7.0. Standalone instances do not support data synchronization.
Replica set instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Synchronize data by using DTS | ||||||||
| One-way synchronization by using MongoShake |
Sharded cluster instance
| Feature | 8.0 | 7.0 | 6.0 | 5.0 | 4.4 | 4.2 | 4.0 | 3.4 |
|---|---|---|---|---|---|---|---|---|
| Synchronize data by using DTS | ||||||||
| One-way synchronization by using MongoShake |
Standalone instance
| Feature | 4.0 | 3.4 |
|---|---|---|
| Data synchronization by using DTS / One-way synchronization by using MongoShake |