All Products
Search
Document Center

Tair (Redis® OSS-Compatible):ModifyAccountDescription

Last Updated:Aug 28, 2026

Modifies the description of an account for a Tair (Redis OSS-compatible) instance.

Operation description

Supported only for instances that run Redis 4.0 or later.

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

kvstore:ModifyAccountDescription

update

*DBInstance

acs:kvstore:{#regionId}:{#accountId}:instance/{#instanceId}

None None

Request parameters

Parameter

Type

Required

Description

Example

InstanceId

string

Yes

The ID of the instance.

r-bp1zxszhcgatnx****

AccountName

string

Yes

The username of the account. Call the DescribeAccounts operation to query account usernames.

demoaccount

AccountDescription

string

Yes

The description of the account.

  • The description must start with a letter and cannot start with http:// or https://.

  • The description can contain letters, digits, underscores (_), and hyphens (-).

  • The description must be 2 to 256 characters in length.

testescription

SourceBiz

string

No

Automatically generated by the service. You do not need to specify this parameter.

SDK

Response elements

Element

Type

Description

Example

object

RequestId

string

The ID of the request.

8D0C0AFC-E9CD-47A4-8395-5C31BF9B****

Examples

Success response

JSON format

{
  "RequestId": "8D0C0AFC-E9CD-47A4-8395-5C31BF9B****"
}

Error response

JSON format

{
  "RequestId":"8D0C0AFC-E9CD-47A4-8395-5C31BF9B3E76"
}

Error codes

HTTP status code

Error code

Error message

Description

400 InvalidEngineVersion.Format Current EngineVersion does not support operations. The operation is not supported while the instance runs this engine version.
400 InvalidAccountDescription.Format Specified AccountDescription is not valid.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.