Updated on 2026-11-03 GMT+08:00

Creating an Account

Scenarios

When you create a TaurusDB instance, account root is created by default. You can create other accounts as needed.

You can create an account using either of the following methods:

Using TaurusDB: TaurusDB is easy to use. There are no special commands to remember.
Using DAS: DAS is a powerful service that offers more flexibility, but you need to be familiar with the creation commands.

Account Types

**Table 1** Account description
Account Type	Description
Administrator account root	Only the administrator account root is provided on the instance creation page. For details about the supported permissions, see TaurusDB Constraints. NOTE: Running revoke, drop user, or rename user on root may cause service interruption. Exercise caution when running any of these statements.
System accounts	To provide O&M services, the system automatically creates system accounts when you create TaurusDB instances. These system accounts are unavailable to you. rdsAdmin: a management account with superuser permissions, which is used to query and modify instance information, rectify faults, migrate data, and restore data. rdsRepl: a replication account, which is used to synchronize data from the primary node to read replicas. rdsBackup: a backup account, which is used to back up data in the background. rdsMetric: a metric monitoring account, which is used by watchdog to collect database status data. rdsProxy: a database proxy account, which is used for authentication when the database is connected through the proxy address. This account is automatically created when you enable read/write splitting.
Other accounts	Accounts created through the console or SQL statements. After an account is created, you can assign permissions to it as required. For details, see Changing Permissions for Accounts.

Constraints

This operation is not allowed when another operation is being performed on your DB instance.
If you grant permissions on both all and specific databases to an account, the account's actual permissions are a combination of them.
If you delete a database somewhere other than on the TaurusDB console, permissions granted specifically for the database are not automatically deleted. They must be deleted manually. This is an open-source MySQL behavior. For details, see DROP DATABASE Statement.
For accounts created by executing SQL statements through DAS or a client connected directly to the database kernel, if the account names do not comply with the naming rules (for example, they contain other special characters), check whether the accounts are displayed properly on the Accounts page. Compatibility is not guaranteed for accounts containing special characters that are created by bypassing the naming rules through a direct client connection in data O&M scenarios such as backup and restoration.
After multi-tenancy is enabled, you cannot grant or revoke permissions for multi-tenant users through the console. If needed, connect to the instance using a client tool and execute SQL statements. For details, see Using Multi-Tenancy for Resource Isolation.

Procedure

Log in to the TaurusDB console.
Click in the upper left corner and select a region.
On the Instances page, click the target instance name.
In the navigation pane, choose Accounts.
On the displayed page, click Create Account.

In the displayed Create Account dialog box, set the required parameters.

Figure 1 Creating an account
Click to enlarge

**Table 2** Parameter description
Parameter	Description
Username	The username contains 1 to 32 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
Host IP Address	To enable all IP addresses to access your DB instance, set it to %. If you enter 10.10.10.%, all IP addresses in the subnet 10.10.10.* are allowed to access the TaurusDB instance. To specify multiple IP addresses, separate them with commas (,), for example, 192.168.0.*,172.16.213.* (no spaces before or after the comma).
Password	The password must meet the following requirements: It must consist of 8 to 32 characters. It must contain at least four of the following: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^-_=+?,()&\|.). It must comply with the values of validate_password* parameters. To check the password-related parameter values, click an instance name, choose Parameters in the navigation pane, and search for validate_password in the upper right corner of the page. It cannot be the username or the username spelled backwards.
Confirm Password	The value must be the same as that of Password.
Authorization Type	You can grant permissions on all databases or on specified databases. If you grant permissions on both all databases and specified databases to an account, the account has the combined permissions granted by both.
Authorized Databases	Select one or more unauthorized databases from the drop-down list. In the Database Permissions list, select the target databases and grant them read/write or read-only permission. After granting permissions, you can click Revoke Permissions and then grant permissions again as needed. If there are no unauthorized databases available, click Create Database, enter the required account information, and click OK. You can also modify the account permissions later.
Description	The description can consist of up to 512 characters. It cannot contain carriage returns or any of the following special characters: !<"='>&

Click OK.
After the account is created, manage it on the Accounts page.

Log in to the TaurusDB console.
Click in the upper left corner and select a region.
On the Instances page, locate an instance and click Log In in the Operation column.
On the displayed DAS login page, enter the username and password and click Log In.
Create a database account.

You can use either of the following methods.
1. Choose SQL Operations > SQL Window. In the displayed SQL window, select the target database and run the following command:
```
create user username;
```
2. Choose Account Management > User Management and click Create User.
  For details, see Creating a User.
After the account is created, manage it on the Accounts page.

APIs

Parent Topic: Account Management (Non-Administrator)