All Products
Search
Document Center

ApsaraDB RDS:UpgradeDBProxyInstanceKernelVersion

Last Updated:Mar 13, 2024

Upgrades the dedicated proxy version of an instance.

Operation description

Supported database engines

  • MySQL
  • PostgreSQL

References

Note Before you call this operation, read the following documentation and make sure that you fully understand the prerequisites and impacts of this operation.

Debugging

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
rds:UpgradeDBProxyInstanceKernelVersionWRITE
  • DBInstance
    acs:rds:{#regionId}:{#accountId}:dbinstance/{#dbinstanceId}
  • rds:ResourceTag
none

Request parameters

ParameterTypeRequiredDescriptionExample
DBInstanceIdstringYes

The instance ID. You can call the DescribeDBInstances operation to query the instance ID.

rm-uf6wjk5****
UpgradeTimestringNo

The time when you want to upgrade the database proxy version of the instance. Valid values:

  • MaintainTime (default): performs the upgrade during the maintenance window that you specified. For more information, see Modify the maintenance window.
  • Immediate: performs the upgrade immediately.
  • SpecificTime: performs the upgrade at a specified point in time.
Note
  • If the instance runs MySQL, you can set this parameter to MaintainTime, Immediate, or SpecificTime.
  • If the instance runs PostgreSQL, you can set this parameter to MaintainTime or Immediate.
  • MaintainTime
    SwitchTimestringNo

    The specific point in time when you want to perform the upgrade. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time must be in UTC.

    Note If you set UpgradeTime to SpecificTime, you must specify SwitchTime.
    2019-07-10T13:15:12Z
    DBProxyEngineTypestringNo

    A reserved parameter. You do not need to specify this parameter.

    normal

    Response parameters

    ParameterTypeDescriptionExample
    object

    The response parameters.

    DBInstanceNamestring

    The ID of the database proxy of the instance.

    bu9***
    RequestIdstring

    The ID of the request.

    44537EC8-DFA2-4745-B579-E733FF2C5B9A
    TaskIdstring

    The task ID.

    33436****

    Examples

    Sample success responses

    JSONformat

    {
      "DBInstanceName": "bu9***",
      "RequestId": "44537EC8-DFA2-4745-B579-E733FF2C5B9A",
      "TaskId": "33436****"
    }

    Error codes

    HTTP status codeError codeError messageDescription
    400InvalidDBInstanceNameSpecified parameter DBInstanceName is not valid.The value of the DBInstanceName parameter is invalid. Check that the value of this parameter is not null or an empty string.
    403IncorrectDBInstanceStateThe proxy instance has not been activated.-
    403IncorrectDBInstanceStateCurrent DB instance state does not support this operation.-
    404AllocateResourceFailedFailed to allocate resources. Please check the zone and the host you selected.Failed to obtain the requested resources. Check whether the zone and the host can provide sufficient resources for the instance type that you specify.
    404InvalidParamThe parameter is invalid.The operation failed. The values of some parameters are invalid.
    404InsufficientResourceCapacityThe target availability zone does not have sufficient resources.The target Availability Zone does not have enough resources.

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

    Change history

    Change timeSummary of changesOperation
    2024-01-09The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      Error Codes 404 change
      delete Error Codes: 400
      delete Error Codes: 403
    2023-12-19API 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: 403
      Added Error Codes: 404
    2023-04-17The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      Error Codes 403 change
      delete Error Codes: 400
    2022-06-23API 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: 403
    2022-06-08The Error code has changed. The request parameters of the API has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      delete Error Codes: 400
      delete Error Codes: 403
    Input ParametersThe request parameters of the API has changed.
      Added Input Parameters: DBProxyEngineType