You can migrate data from a self-managed MongoDB database to an ApsaraDB for MongoDB instance. This topic describes the limits of ApsaraDB for MongoDB on some operations.
|Deploy an instance||Standalone instances can be created only in the China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), or China (Shenzhen) region.|
|Configure the database version||
The MongoDB version must be 3.4.
|Configure the storage engine||
The storage engine must be WiredTiger.
|Connect to an instance by using its public endpoint||By default, ApsaraDB for MongoDB does not provide public endpoints for instances. This is because security risks may arise if you connect to instances over the Internet. If you want to connect to a standalone instance over the Internet, you must apply for a public endpoint. For more information, see Apply for a public endpoint for an ApsaraDB for MongoDB instance.|
|Restart an instance||You must restart an instance by using the ApsaraDB for MongoDB console or by calling the RestartDBInstance operation.|
|Migrate data||To migrate data, you must use the built-in tools provided by MongoDB or Data Transmission Service (DTS). For more information, see Migrate self-managed MongoDB databases to standalone instances by using tools provided by MongoDB or Migrate self-managed standalone MongoDB databases to Alibaba Cloud by using DTS.|
|Back up data||Standalone instances are backed up in snapshot mode due to the special architecture.
Note A snapshot backup retains the status of disk data at a specific point in time.
|Restore data||You can create instances only from a backup. For more information, see Create an instance from a backup.|
|Modify the parameters of an instance||For security and stability reasons, some parameters cannot be modified. For more information, see Configure database parameters for an ApsaraDB for MongoDB instance.|