All Products
Search
Document Center

AnalyticDB:CreateAccount

Last Updated:Oct 26, 2026

Creates an account.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

  • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

  • API: The API that you can call to perform the action.

  • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

  • Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

    • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.

    • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

  • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.

  • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

adb:CreateAccount

create

DBCluster

acs:adb:{#regionId}:{#accountId}:dbcluster/{#dbclusterId}

None None

Request parameters

Parameter

Type

Required

Description

Example

DBClusterId

string

Yes

The ID of the Data Warehouse Edition cluster.

Note

You can call the DescribeDBClusters operation to query the cluster ID.

am-bp1r053byu48p****

AccountName

string

Yes

The name of the database account. The name must meet the following requirements:

  • It must start with a lowercase letter and end with a lowercase letter or a digit.

  • It can contain only lowercase letters, digits, and underscores (_).

  • It must be 2 to 16 characters in length.

  • It cannot be a reserved account name, such as root, admin, or opsadmin.

test_accout

AccountPassword

string

Yes

The password of the database account. The password must meet the following requirements:

  • It must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters.

  • Special characters include: !@#$%^&*()_+-=

  • It must be 8 to 32 characters in length.

Test_accout1

AccountDescription

string

No

The description of the account.

  • It cannot start with http:// or https://.

  • It can be up to 256 characters in length.

Database test account

AccountType

string

No

The type of the account. Valid values:

  • Normal: standard account. You can create up to 256 standard accounts in a cluster.

  • Super (default): privileged account. You can create only one privileged account in a cluster.

Note
  • If the cluster does not have any accounts, you can create either a privileged account or a standard account when you call this operation. If the cluster already has a privileged account, you must set this parameter to Normal to create a standard account.

  • After an account is created, the privileged account has permissions on all databases in the cluster. By default, a standard account does not have any permissions. You must use the privileged account to manually grant permissions on specific databases to the standard account. For more information, see Grant permissions to a user.

Normal

Tag

array<object>

No

The list of tags.

object

No

The tag information.

Key

string

No

The tag key. You can use tags to filter the cluster list. You can specify up to 20 tag key-value pairs. The number N in each tag key-value pair must be unique and must be a consecutive integer starting from 1. The value of Tag.N.Key corresponds to the value of Tag.N.Value.

Note

The tag key can be up to 64 characters in length and cannot start with aliyun, acs:, http://, or https://.

testkey1

Value

string

No

The tag value. You can use tags to filter the cluster list. You can specify up to 20 tag key-value pairs. The number N in each tag key-value pair must be unique and must be a consecutive integer starting from 1. The value of Tag.N.Key corresponds to the value of Tag.N.Value.

Note

The tag value can be up to 64 characters in length and cannot start with aliyun, acs:, http://, or https://.

testvalue1

Response elements

Element

Type

Description

Example

object

The list.

TaskId

integer

The ID of the task.

1564657730

RequestId

string

The ID of the request.

2FED790E-FB61-4721-8C1C-07C627FA5A19

DBClusterId

string

The ID of the Data Warehouse Edition cluster.

am-bp1r053byu48p****

Examples

Success response

JSON format

{
  "TaskId": 1564657730,
  "RequestId": "2FED790E-FB61-4721-8C1C-07C627FA5A19",
  "DBClusterId": "am-bp1r053byu48p****"
}

Error codes

HTTP status code

Error code

Error message

Description

404 InvalidDBCluster.NotFound The DBClusterId provided does not exist in our records. The specified DBClusterId parameter does not exist. Make sure that the DBClusterId value is valid.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.