All Products
Search

This Product

    Cloud Architect Design Tools:ModifyApplicationSpec

    Document Center

    Cloud Architect Design Tools:ModifyApplicationSpec

    Last Updated:Mar 30, 2026

    Modifies the configuration of an application.

    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

    bpstudio:ModifyApplicationSpec

    none

    *Application

    acs:bpstudio::{#accountId}:application/{#ApplicationId}

    		 None None

    Request parameters

    Parameter

    Type

    Required

    Description

    Example
    ApplicationId

    string

    Yes

    The application ID.

    02S7UU41WKJL7ERR
    InstanceSpec

    array<object>

    No

    The specifications for the configuration change.

    array<object>

    No

    The parameters for the configuration change.

    InstanceId

    string

    No

    The ID of the resource to change.

    rm-2ze8f4ah378a*****
    Configuration

    object

    No

    The parameters for the configuration change.

    any

    No

    The input parameters for the configuration change.

    Note

    • For subscription instances, use `UPGRADE` for upgrades and `DOWNGRADE` for downgrades. For pay-as-you-go instances, use `UPGRADE` for all configuration changes.

    ecs

    • orderType: UPGRADE

    • instance_type: xxx (Instance type)

    rds (You can change the instance type and storage capacity at the same time.)

    • orderType: UPGRADE

    • instance_type: xxx (Instance type)

    • instance_storage: xxx (Storage capacity)

    kvstore

    • orderType: UPGRADE

    • number: 1 (Number of shards)

    • instance_class: xxx (Instance type)

    kvstore_prepaid_public_cn

    • orderType: UPGRADE

    • shard_quantity: 4 (Number of shards)

    • shard_class: xxx (Shard specifications)

    • storage: 10 (Disk capacity)

    tair

    • orderType: UPGRADE

    • shard_quantity: 4 (Number of shards)

    • shard_class: xxxx (Shard specifications)

    kafka

    • orderType: UPGRADE

    • eip_max (Internet traffic):

    • IO_max (Internet traffic):

    • partition_num: Number of partitions

    • disk_size (Disk capacity):

    polardb

    • orderType: UPGRADE

    • master_spec (Node specifications):

    elasticsearch

    • orderType: UPGRADE

    • node_spec (Data node specifications):

    • kibana_node_spec (Kibana node specifications):

    • master_spec (Dedicated master node specifications)

    • warm_node_spec (Cold data node specifications):

    • client_node_spec (Coordinating node specifications):

    • elastic_node_spec (Elastic data node):

    hitsdb_lindormnext_v2

    • orderType: UPGRADE

    • upgrade_type: SPEC (specifications), OPEN (enable), or COUNT (number of nodes)

    • engine_type (Engine type): TABLE (LindormTable), TSDB (LindormTSDB), LSEARCH (search engine), LTS (LTS engine), LVECTOR (vector engine), or LCOLUMN (column store engine)

    • node_type (Node type): universal (general-purpose), calculated (compute-optimized), mem_enhanced (memory-optimized), local_hdd_pro (local HDD), or local_ssd_pro (local SSD)

    • node_spec (Node specifications):

    • core_num (Number of nodes):

    • is_cloud_disk (Mount a cloud disk): `true` or `false`

    • disk_type (Cloud disk type): `cloud_efficiency` or `cloud_essd`

    • disk_size (Cloud disk storage capacity):

    slb

    Note

    Valid values for `InstanceChargeType` (instance billing method): `PayBySpec` (pay-by-specification) and `PayByCLCU` (pay-by-usage).
    Valid values for `internet_charge_type` (Internet traffic fee): `0` (pay-by-bandwidth) and `1` (pay-by-traffic).
    If you set `InstanceChargeType` to `PayBySpec`, the `specification` parameter is required.
    If you set `internet_charge_type` to `0`, the `bandwidth` parameter is required.



    • orderType: UPGRADE

    • specification (Instance type):

    • InstanceChargeType (Instance billing method):

    • internet_charge_type (Internet traffic fee):

    • bandwidth (Bandwidth):

    hbase

    • orderType: UPGRADE

    • core_instance_type (Core instance type):

    dds

    • orderType: UPGRADE

    • db_instance_class (Instance type):

    onspre

    Upgrade or downgrade the specifications of an Enterprise Platinum Edition instance

    • orderType: UPGRADE

    • tps_max (Peak TPS):

    • topic_capacity (Maximum number of topics):

    • message_capacity (Message storage):

    Upgrade a Standard Edition instance to an Enterprise Platinum Edition instance

    orderType: BUY tps_max (Peak TPS): topic_capacity (Maximum number of topics): message_capacity (Message storage): period_unit (Subscription unit): `Month` or `Year`
  • period (Subscription duration):

    • hitsdb_lindorm

    • orderType: UPGRADE

    • lindorm_core_spec (Wide table node specifications):

    drds

    • orderType: UPGRADE

    • drds_instance_spec (Instance type):

    clickhouse Change the configuration of an Enterprise Edition instance:

    • max_ccu (Maximum CCUs):

    • mini_ccu (Minimum CCUs):

    Community Edition instance: Horizontal scaling:

    • node_count (Number of nodes):

    Vertical scaling:

    • zkSize (Zookeeper specifications):

    • instance_class (Instance type):

    • storage_type (Storage class):

    • storage_size (Storage space):

    drds_polarx Standard Edition:

    • node_spec (Node specifications):

    Enterprise Edition:

    • cn_node_spec (Compute node specifications):

    • dn_node_spec (Data node specifications):

    • dn_storage_space (Data node disk):

    opensearch

    • buytype (Cluster preference):

    • storage (Storage capacity):

    • compute (Compute resource):

    eip

    • bandwidths (Peak bandwidth):

    • internet_charge_type (Traffic):

    • bandwidth (Bandwidth):

    adb

    • reserved_node_size (Single-node specifications of reserved resources):

    • reserved_node_count (Number of reserved nodes):

    • Activate_AI_node (Enable AI nodes):

    • ADB_AI_Node_Size (AI node specifications):

    • AI_Node_Count_Postpaid (Number of AI nodes):

    • Deployment_Method (Deployment mode):

    • zone_id (Primary zone):

    • vswitch_id (vSwitch of the primary zone):

    • StandbyAZ (Secondary zone):

    • Standby_vswitch_id (vSwitch of the secondary zone):

    hologres

    • size (Compute resources):

    • GatewayNum (Number of Gateway nodes):

    • warehouse_cu (Reserved compute resources for the compute group):

    • enable_serverless_computing (Enable Serverless Computing):

    flink

    • max_cu (Maximum quota):

    • min_cu (Compute resource quota in a single zone):

    • min_cu_ha (Cross-zone):

    dts

    • instance_class (Data synchronization configuration change):

    • migration_instance_class (Data migration configuration change):

    hitsdb_lts

    • upgrade_type: upgrade-lts-core-num

    • core_number (Number of nodes):

    • upgrade_type: upgrade-lts-engine

    • core_spec (Node specifications):

    ons_rmq

    • msg_process_spec (Message processing compute specifications):

    • series_type (Primary series type):

    orderType:UPGRADE

    Response elements

    Element

    Type

    Description

    Example

    object

    Schema of Response

    Success

    string

    Indicates whether the request was successful.

    true
    Code

    string

    The status code.

    200
    Message

    string

    The error message.

    Success
    Data

    string

    The return value.

    -1
    RequestId

    string

    The request ID.

    A3488F1D-xxxx-xxxx-xxxx-5374BA0F3562
    AccessDeniedDetail

    string

    The details about the access denial.

    { "PolicyType": "", "AuthPrincipalOwnerId": "", "EncodedDiagnosticMessage": "", "AuthPrincipalType": "", "AuthPrincipalDisplayName": "", "NoPermissionType": "", "AuthAction": "" }

    Examples

    Success response

    JSON format

    {
  "Success": "true",
  "Code": "200",
  "Message": "Success",
  "Data": "-1",
  "RequestId": "A3488F1D-xxxx-xxxx-xxxx-5374BA0F3562",
  "AccessDeniedDetail": "{\n    \"PolicyType\": \"\",\n    \"AuthPrincipalOwnerId\": \"\",\n    \"EncodedDiagnosticMessage\": \"\",\n    \"AuthPrincipalType\": \"\",\n    \"AuthPrincipalDisplayName\": \"\",\n    \"NoPermissionType\": \"\",\n    \"AuthAction\": \"\"\n  }"
}

    Error codes

    HTTP status code

    Error code

    Error message

    Description
    400 bp.java.8004 No permissions.
    400 bp.java.nopowerContact You do not have permission to use this function. Please contact the main account or permission administrator to authorize the relevant permissions.
    400 bp.java.nopower No permissions.

    See Error Codes for a complete list.

    Release notes

    See Release Notes for a complete list.