ModifyInstanceConfig -

Modifies the parameter settings of an ApsaraDB for Redis instance.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

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.

Operation	Access level	Resource type	Condition key	Associated operation
kvstore:ModifyInstanceConfig	update	DBInstance acs:kvstore:{#regionId}:{#accountId}:instance/{#instanceId}	kvstore:InstanceAofConfig kvstore:TLSVersion	none

Request parameters

Parameter	Type	Required	Description	Example
InstanceId	string	Yes	The ID of the instance.	r-bp1zxszhcgatnx****
Config	string	Yes	The instance parameter settings that you want to modify. Specify this parameter in the JSON format. The new value of a parameter overwrites the original value. Description** For more information, see Supported parameters.	{"maxmemory-policy":"volatile-lru","zset-max-ziplist-entries":128,"zset-max-ziplist-value":64,"hash-max-ziplist-entries":512,"set-max-intset-entries":512}

Response parameters

Parameter	Type	Description	Example
	object
RequestId	string	The ID of the request.	8D0C0AFC-E9CD-47A4-8395-5C31BF9B****

Examples

Sample success responses

JSONformat

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

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidParameters.Format	Specified parameters is not valid.	The specified parameters are invalid.
400	ParamNotSupportedForCurrentVersion	Parameter is not supported for current version.	The error message returned because modifications to parameter values are not supported for the current engine version.
403	InstanceType.NotSupport	Current instance type does not support this operation.	The current instance type does not support this operation
403	NetworkType.NotSupport	Current network type does not support this operation.	-

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

Change history

Change time	Summary of changes	Operation

No change history