All Products
Search
Document Center

AnalyticDB:BindAccount

Last Updated:Aug 30, 2024

Associates a standard account of an AnalyticDB for MySQL cluster with a Resource Access Management (RAM) user.

Operation description

For information about the endpoints of AnalyticDB for MySQL, see Endpoints .

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

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 Resources is 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.
OperationAccess levelResource typeCondition keyAssociated operation
adb:BindAccountupdate
  • AccountLakeVersion
    acs:adb:{#regionId}:{#accountId}:dbcluster/{#DBClusterId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
DBClusterIdstringYes

The ID of the AnalyticDB for MySQL Data Lakehouse Edition (V3.0) cluster.

amv-wz99d9nh532****
RamUserstringYes

The ID of the RAM user.

1444832459****
AccountNamestringYes

The standard account of the cluster.

test_accout

Response parameters

ParameterTypeDescriptionExample
object

Schema of Response

RequestIdstring

The request ID.

DFF27323-3868-5F8A-917D-5D1D06B6BC0D

Examples

Sample success responses

JSONformat

{
  "RequestId": "DFF27323-3868-5F8A-917D-5D1D06B6BC0D"
}

Error codes

HTTP status codeError codeError messageDescription
400InvalidAccountName.MalformedThe specified parameter AccountName is not valid.The AccountName parameter is invalid. Check the parameter.
400InvalidDBClusterId.NotFoundThe DBClusterId provided does not exist in our records.The specified DBClusterId parameter does not exist. Make sure that the DBClusterId value is valid.
400InvalidDBClusterId.MalformedThe specified parameter DBClusterId is not valid.The DBClusterId parameter is invalid. Check the parameter.
400ACS.Account.NotExistThe account is not found.The specified RAM user does not exist.
400ACS.Account.UserHasBindThe user has been associated with another database account %s.The RAM user is associated with another database account.
400ACS.User.DatabaseAccountHasBindThe database account has been bound to %s.The database account is associated with a RAM user.
400ACS.InvalidParameter.%sParameter %s is invalid.The specified parameter is invalid.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2023-06-08The Error code has changedView Change Details
2023-04-20The Error code has changedView Change Details
2023-03-31The Error code has changedView Change Details