GrantAccountPrivilege - Modify account permissions | Tair (Redis) API - Tair (Redis® OSS-Compatible)

Operation description

Note

Only Tair (Redis OSS-compatible) instances running Redis 4.0 or later are supported.
The instance must be in the Running state.

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

update

*DBInstance

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

None

Request parameters

Parameter	Type	Required	Description	Example
InstanceId	string	Yes	The ID of the instance.	r-bp1zxszhcgatnx****
AccountName	string	Yes	The account name. Call DescribeAccounts to query account names.	demoaccount
AccountPrivilege	string	Yes	The account permissions. Default value: RoleReadWrite. Valid values: RoleReadOnly: read-only permissions. RoleReadWrite: read and write permissions.	RoleReadWrite
SourceBiz	string	No	For internal use only.	SDK

Response elements

Element	Type	Description	Example
	object
RequestId	string	The request ID.	3845BDF5-15A6-4444-B770-78501819****

Examples

Success response

JSON format

{
  "RequestId": "3845BDF5-15A6-4444-B770-78501819****"
}

Error response

JSON format

{
	"RequestId": "3845BDF5-15A6-4444-B770-785018191E25"
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidAccountName.Format	Specified AccountName is not valid.
400	InvalidAccountPrivilege.Format	Specified AccountPrivilege is not valid.
400	IncorrectAccount	Current DB instance account does not support this operation.
400	IncorrectMinorVersion	Current engine minor version does not support operations.	The operation is not supported by the minor version of the instance. Update the instance to the latest minor version and try again.
404	InvalidAccountName.NotFound	Specified AccountName does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.