All Products
Search

This Product

    Lindorm:UpdateLindormV2Instance

    Document Center

    Lindorm:UpdateLindormV2Instance

    Last Updated:Sep 18, 2026

    Updates a Lindorm V2 instance.

    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

    lindorm:UpdateLindormV2Instance

    update

    *All Resource

    *

    		 None None

    Request parameters

    Parameter

    Type

    Required

    Description

    Example
    RegionId

    string

    Yes

    The region ID of the instance. You can call DescribeRegions to query available regions. Use this parameter to specify the region in which to create the instance.

    cn-hangzhou
    CloudStorageType

    string

    No

    The cloud storage type. Valid values:

    • PerformanceStorage: performance cloud storage.

    • StandardStorage: standard cloud storage.

    Valid values:

    • StandardStorage :

      Standard cloud storage.

    • CapacityStorage :

      Capacity cloud storage.

    • PerformanceStorage :

      Performance cloud storage.

    PerformanceStorage
    CloudStorageSize

    integer

    No

    The cloud storage space. Unit: GB.

    480
    EnableCapacityStorage

    boolean

    No

    Specifies whether to enable capacity storage.

    false
    CapacityStorageSize

    integer

    No

    The capacity storage space.

    10000
    EngineList

    array<object>

    Yes

    The list of engine types.

    array<object>

    No

    The list of engine information.

    EngineType

    string

    Yes

    The engine type. Valid values:

    • TABLE: LindormTable.

    • TSDB: LindormTSDB.

    • LSEARCH: search engine.

    • LTS: LTS engine.

    • LVECTOR: vector engine.

    • LCOLUMN: column store engine.

    • LAI: AI engine.

    Valid values:

    • TABLE :

      LindormTable.

    • LSEARCH :

      Search engine.

    • LMESSAGE :

      Message engine.

    • LAI :

      AI engine.

    • LCOLUMN :

      Column store engine.

    • LVECTOR :

      Vector engine.

    • LTS :

      LTS engine.

    • TSDB :

      LindormTSDB.

    • LSTREAM :

      Stream engine.

    TABLE
    NodeGroupList

    array<object>

    No

    The list of engine node groups.

    object

    No

    The list of engine node groups.

    NodeSpec

    string

    Yes

    The DPI engine node specifications. Valid values:

    • lindorm.c.2xlarge: 8 cores and 16 GB memory.

    • lindorm.g.2xlarge: 8 cores and 32 GB memory.

    • lindorm.c.4xlarge: 16 cores and 32 GB memory.

    • lindorm.g.4xlarge: 16 cores and 64 GB memory.

    • lindorm.c.8xlarge: 32 cores and 64 GB memory.

    • lindorm.g.8xlarge: 32 cores and 128 GB memory.

    lindorm.g.2xlarge
    NodeCount

    integer

    Yes

    The number of nodes.

    6
    NodeDiskType

    string

    No

    The cloud disk type of the node. This parameter is optional. This parameter is used in special scenarios and is available only after you are added to the whitelist.

    Valid values:

    • cloud_efficiency :

      Standard cloud disk.

    • cloud_essd :

      ESSD cloud disk (standard SSD).

    cloud_essd
    NodeDiskSize

    integer

    No

    The disk size per node. This parameter is optional.

    0
    ResourceGroupName

    string

    No

    The name of the node group. This parameter is required. The value is returned by calling the GetLindormV2Instance operation.

    groupName
    GroupId

    string

    No

    The node group ID.

    ix90Yes
    InstanceId

    string

    Yes

    The instance ID.

    ld-bp1o3y0yme2i2****

    Response elements

    Element

    Type

    Description

    Example

    object

    RequestId

    string

    The request ID.

    1556DCB0-043A-4444-8BD9-CF4A68E7EE64
    InstanceId

    string

    The instance ID.

    ld-bp1478w1603****
    OrderId

    integer

    The order ID.

    240136741090345
    AccessDeniedDetail

    string

    The details of the permission verification failure.

    {"AuthAction":"xxx","AuthPrincipalDisplayName":"222","AuthPrincipalOwnerId":"111","AuthPrincipalType":"SubUser",,"NoPermissionType":"ImplicitDeny","PolicyType":"AccountLevelIdentityBasedPolicy","EncodedDiagnosticMessage":"xxxxxx"}

    Examples

    Success response

    JSON format

    {
  "RequestId": "1556DCB0-043A-4444-8BD9-CF4A68E7EE64",
  "InstanceId": "ld-bp1478w1603****",
  "OrderId": 240136741090345,
  "AccessDeniedDetail": "{\"AuthAction\":\"xxx\",\"AuthPrincipalDisplayName\":\"222\",\"AuthPrincipalOwnerId\":\"111\",\"AuthPrincipalType\":\"SubUser\",,\"NoPermissionType\":\"ImplicitDeny\",\"PolicyType\":\"AccountLevelIdentityBasedPolicy\",\"EncodedDiagnosticMessage\":\"xxxxxx\"}"
}

    Error codes

    HTTP status code

    Error code

    Error message

    Description
    400 Lindorm.Errorcode.ParameterInvaild The parameter is invalid.
    400 LindormErrorCode.%s %s. %s.
    400 LindormErrorCode.OperationDenied.OrderProcessing There is an order in process, please confirm that it has been processed and try again. There is an order in process, please confirm that it has been processed and try again.
    403 Lindorm.Errorcode.OperationDenied You are not authorized to operate on the specified resource.
    403 API.Forbidden The API operation is forbidden in this environment. This operation is not supported in the current environment.
    403 Lindorm.Errorcode.ServiceLinkedRoleNoPermission No permission to create service linked role. You are not authorized to create the service-linked role.

    See Error Codes for a complete list.

    Release notes

    See Release Notes for a complete list.