Data Management (DMS) is an integrated solution for managing data, structures, R&D processes, users, access permissions, and access security. It supports relational databases (MySQL, SQL Server) and NoSQL databases (MongoDB, Redis). Use DMS to connect to and manage your ApsaraDB for MongoDB instances directly from the console.
Roles and permissions
DMS assigns one of four roles to each user. Your role determines which actions you can perform:
| Action | Required role |
|---|---|
| Use all system management features (except data protection); manage users and IP address whitelist | DMS administrator |
| Manage operations logs and use the data protection feature | Security administrator |
| Manage instances, tasks, security rules, and configurations; design schemas | Database administrator (DBA) |
| Cannot use system management features; must first obtain permission to manage the instance | Common user |
If you are a common user, request instance access before proceeding. See Apply for permissions.
Prerequisites
Before you begin, ensure that you have added the DMS server IP addresses to the whitelist of your ApsaraDB for MongoDB instance.
Skip this step if you have already added the DMS server IP addresses to the whitelist.
Add the following IP addresses based on your instance's network type:
| Network type | IP addresses to add |
|---|---|
| Virtual Private Cloud (VPC) | 100.104.0.0/16 |
| Classic network | 120.55.177.0/24, 121.43.18.0/24, 101.37.74.0/24, 10.153.176.0/24, 10.137.42.0/24, 11.193.54.0/24 |
For instructions, see Configure a whitelist for an ApsaraDB for MongoDB instance.
Log on to an instance
The steps differ slightly depending on your instance type. Identify your instance type before you begin:
Standalone instance: Redirected to DMS immediately after clicking Log On.
Replica set instance: Select the node to log on to, then redirected to DMS.
Sharded cluster instance: Select the mongos node to log on to, then reconnected to DMS.
Step 1: Go to the instance details page
Go to the Replica Set Instances or Sharded Cluster Instances page.
In the left-side navigation pane, click Replica Set Instances or Sharded Cluster Instances.
In the upper-left corner, select the resource group and region where your instance is deployed.
Find the instance and click its ID, or click Manage in the Actions column.
Step 2: Open the logon dialog box
On the Basic Information page, click Log On in the upper-right corner.
Step 3: Configure the connection parameters
In the Log on to Database Instance dialog box, fill in the following parameters:
| Parameter | Description |
|---|---|
| Database type | The database engine. Pre-filled with the current instance's engine. |
| Instance region | The region where the instance is deployed. Pre-filled with the current region. |
| Connection String Address | The instance endpoint. Pre-filled with the current instance's endpoint. |
| Database Name | The authentication database where the database account was created. If Database Account is root, enter admin. Do not use the root account in production — create dedicated users with appropriate permissions instead. |
| Security hosting | Enables security hosting, which puts the instance into a logon-free state. |
| Database Account | The account used to access the database. The default initial account is root. |
| Database Password | The password for the database account. If you have forgotten the root password, reset it before proceeding. |
Step 4: (Optional) Test the connection
Click Test Connection.
If the Success message appears, the connection is valid. Click OK to proceed.
If the test fails, read the error message, click OK, and adjust the configuration. Repeat until the connection succeeds.
Step 5: Log on
Click Login.
Tip: To have the browser save the password, select Remember password before clicking Login.
Apply for permissions
Common users must request access to an instance through DMS before they can manage it. See Manage permissions.