BindAccount - AnalyticDB - Alibaba Cloud Documentation Center

Operation description

For the endpoints of this service, see Endpoints.

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:BindAccount

update

*AccountLakeVersion

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

None

Request parameters

Parameter	Type	Required	Description	Example
DBClusterId	string	Yes	The ID of the Data Lakehouse Edition cluster.	amv-wz99d9nh532****
RamUser	string	Yes	The account ID of the RAM user.	1444832459****
AccountName	string	Yes	The standard database account.	test_accout

Response elements

Element	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID.	DFF27323-3868-5F8A-917D-5D1D06B6BC0D

Examples

Success response

JSON format

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

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidAccountName.Malformed	The specified parameter AccountName is not valid.	The AccountName parameter is invalid. Check the parameter.
400	InvalidDBClusterId.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	InvalidDBClusterId.Malformed	The specified parameter DBClusterId is not valid.	The DBClusterId parameter is invalid. Check the parameter.
400	ACS.Account.NotExist	The account is not found.	The specified RAM user does not exist.
400	ACS.Account.UserHasBind	The user has been associated with another database account %s.	The RAM user is associated with another database account.
400	ACS.User.DatabaseAccountHasBind	The database account has been bound to %s.	The database account is associated with a RAM user.
400	ACS.InvalidParameter.%s	Parameter %s is invalid.	The specified parameter is invalid.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.