Modifies the permissions of a database account.
Operation description
For information about the endpoints of AnalyticDB for MySQL, see Endpoints .
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| adb:ModifyAccountPrivileges | update |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| RegionId | string | Yes | The region ID. | cn-hangzhou |
| DBClusterId | string | Yes | The ID of the AnalyticDB for MySQL Data Lakehouse Edition (V3.0) cluster. | amv-bp1k5p066e1a**** |
| AccountName | string | Yes | The name of the database account. | account1 |
| AccountPrivileges | array<object> | Yes | The permissions that you want to grant to the database account. | |
| object | Yes | |||
| PrivilegeObject | object | No | The objects on which you want to grant permissions, including databases, tables, and columns. | |
| Database | string | No | The databases on which you want to grant permissions. This parameter must be specified when the PrivilegeType parameter is set to Database, Table, or Column. | tsdb1 |
| Table | string | No | The tables on which you want to grant permissions. This parameter must be specified when the PrivilegeType parameter is set to Table or Column. | table1 |
| Column | string | No | The columns on which you want to grant permissions. This parameter must be specified when the PrivilegeType parameter is set to Column. | column1 |
| Privileges | array | No | The permissions that you want to grant to the database account. | |
| string | No | The permission that you want to grant to the database account. You can call the | select | |
| PrivilegeType | string | No | The permission level that you want to assign to the database account. You can call the | Global |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "9DD88DE7-824F-1082-AA57-575AFC6517A8"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | ACS.Privilege.ModifyFailed | Failed to modify the account privilege. Make sure that bound account have sufficient database privileges. | Failed to modify the database account permissions. Check whether the database account that is associated with the RAM user has sufficient database permissions. |
| 400 | InvalidDBClusterId.Malformed | The specified parameter DBClusterId is not valid. | The DBClusterId parameter is invalid. Check the parameter. |
| 400 | ACS.Parameter.Malformed | The following required parameters are not specified: %s | You must specify the required parameters. |
| 400 | ACS.InvalidParameter.%s | Parameter %s is invalid. | The specified parameter is invalid. |
| 400 | 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. |
| 400 | ACS.User.NotBindDatabaseAccount | The user has not been associated with a database account. | The user is not associated with the database account. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2024-04-09 | The Error code has changed | View Change Details |
| 2023-04-20 | The Error code has changed | View Change Details |
| 2023-03-24 | The internal configuration of the API is changed, but the call is not affected | View Change Details |