All Products
Document Center

ApsaraDB for Redis:DeleteAccount

Last Updated:May 28, 2024

Deletes an account from an ApsaraDB for Redis instance.

Operation description

  • This operation is supported only for ApsaraDB for Redis instances that run Redis 4.0.
  • The ApsaraDB for Redis instance must be in the Running state.


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
  • DBInstance

Request parameters


The instance ID.


The username of the account. You can call the DescribeAccounts operation to query the username of the account.


Response parameters


The request ID.



Sample success responses


  "RequestId": "8129F11A-D70B-43A6-9455-CE9EAA71****"

Error codes

HTTP status codeError codeError messageDescription
400InvalidAccountName.FormatSpecified AccountName is not valid.-
400InvalidEngineVersion.FormatCurrent EngineVersion does not support operations.The operation is not supported while the instance runs this engine version.
404InvalidAccountName.NotFoundSpecified AccountName does not exist.-

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

Change history

Change timeSummary of changesOperation
2024-02-26API Description Update. The Error code has changedsee changesets
Change itemChange content
API DescriptionAPI Description Update.
Error CodesThe Error code has changed.
    delete Error Codes: 400
    delete Error Codes: 404
    Added Error Codes: 403
2023-03-02The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400
    delete Error Codes: 404