ModifyPrepayInstanceSpec

Updated at:

Modifies the compute resource specifications of a subscription Realtime Compute for Apache Flink instance. If the new specifications are smaller than the current specifications, a scale-in operation is performed. If the new specifications are larger than the current specifications, a scale-out operation is performed.

Note

This API has been deprecated. We recommend migrating to foasconsole(2021-10-28) - ModifyInstanceSpec for enhanced functionality and continued support. While the deprecated API remains temporarily accessible, no further updates or bug fixes will be provided.

Operation description

Before using this operation, make sure that you fully understand the billing method and pricing of Realtime Compute for Apache Flink.

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

stream:ModifyVvpPrepayInstanceSpec

update

*VvpInstance

acs:stream:{#regionId}:{#accountId}:vvpinstance/{#InstanceId}

None None

Request parameters

Parameter

Type

Required

Description

Example

Region

string

Yes

The region.

cn-beijing

InstanceId

string

Yes

The order instance ID.

f-cn-wwo36qj4g06

ResourceSpec

object

Yes

The resource specification information.

Cpu

integer

Yes

The number of CPUs.

1

MemoryGB

integer

Yes

The memory size.

Note

The memory size must be 4 times the number of CPUs.

4

Ha

boolean

No

Specifies whether to enable zone-disaster recovery resources for the workspace.

true

HaZoneId

string

No

The ID of the secondary zone for zone-disaster recovery.

HaVSwitchIds

array

No

The list of vSwitch IDs in the secondary zone for zone-disaster recovery.

string

No

The vSwitch ID in the secondary zone for zone-disaster recovery.

HaResourceSpec

object

No

The resource specifications for zone-disaster recovery.

Cpu

integer

No

The number of CPUs for zone-disaster recovery resources.

10

MemoryGB

integer

No

The memory size of zone-disaster recovery resources, in GB. The value must be 4 times the number of CPUs.

40

Response elements

Element

Type

Description

Example

object

Schema of Response

RequestId

string

The request ID.

67F33190-946B-1105-B6A1-E2DF0426DD51

OrderId

integer

The order ID.

210406354690749

Success

boolean

Indicates whether the request was successful.

true

Examples

Success response

JSON format

{
  "RequestId": "67F33190-946B-1105-B6A1-E2DF0426DD51",
  "OrderId": 210406354690749,
  "Success": true
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.