Modify Router Interface Bandwidth via API Without Downtime - Express Connect - Alibaba Cloud - Express Connect

Modifies the specification of a router interface by calling the ModifyRouterInterfaceSpec operation.

Operation description

After you call this operation, the router interface enters the Activating state. After the router interface is activated, it enters the Active state.

Note

You cannot modify the specification of a router interface that has an overdue payment.

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

vpc:ModifyRouterInterfaceSpec

update

*RouterInterface

acs:vpc:{#regionId}:{#accountId}:routerinterface/{#RouterInterfaceId}

None

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The region where the router interface is deployed. You can call the DescribeRegions operation to query the region ID.	cn-hangzhou
RouterInterfaceId	string	Yes	The ID of the router interface.	ri-2zeo3xzyf38r4urzd****
Spec	string	Yes	The specification of the router interface. The following table describes the available specifications and the corresponding bandwidths: Mini.2: 2 Mbps Mini.5: 5 Mbps Small.1: 10 Mbps Small.2: 20 Mbps Small.5: 50 Mbps Middle.1: 100 Mbps Middle.2: 200 Mbps Middle.5: 500 Mbps Large.1: 1000 Mbps Large.2: 2000 Mbps Large.5: 5000 Mbps Xlarge.1: 10000 Mbps Note If Role is set to AcceptingSide (accepter), set Spec to Negative.	Small.1
ClientToken	string	No	The client token that is used to ensure the idempotence of the request. You can use the client to generate the token, but you must make sure that the token is unique among different requests. The ClientToken value can contain only ASCII characters. Note If you do not specify this parameter, the system automatically uses the RequestId of the API request as the ClientToken. The RequestId may differ for each API request.	02fb3da4-130e-11e9-8e44-0016e04115b

Response elements

Element	Type	Description	Example
	object	The specification of the router interface.
Spec	string	The specification of the router interface. Valid values: Mini.2: 2 Mbps Mini.5: 5 Mbps Small.1: 10 Mbps Small.2: 20 Mbps Small.5: 50 Mbps Middle.1: 100 Mbps Middle.2: 200 Mbps Middle.5: 500 Mbps Large.1: 1000 Mbps Large.2: 2000 Mbps Large.5: 5000 Mbps Xlarge.1: 10000 Mbps.	Small.1
RequestId	string	The request ID.	4EC47282-1B74-4534-BD0E-403F3EE64CAF

Examples

Success response

JSON format

{
  "Spec": "Small.1",
  "RequestId": "4EC47282-1B74-4534-BD0E-403F3EE64CAF"
}

Error codes

HTTP status code	Error code	Error message	Description
400	Forbidden.FinancialLocked	RouterInterface can not be operated by this action when it?s FinancialLocked.
400	InvalidParam.NotFound	Parameter must not be null,uid, bid,regionNo, remoteRegionNo or routerId
400	InvalidOppositeRegionId.NotFound	The OppositeRegionId provided does not exist in our records.
400	InvalidInstanceOwner.Error	The router instance owner error.	The instance owner information is invalid.
400	InvalidRouterInterfaceSpec.Malformed	Specified RouterInterface spec is not valid.	The RouterInterface Spec parameter is set to an invalid value.
400	IllegalParam.chargeType	RouterInterface chargeType different.
400	ResourceQueryError	The specified resource is queried error.	An error occurred while querying the specified resource.
400	InvalidSpec.ValueNotSupported	The specified Spec is not supported.
400	InvalidSpec.ValueNotSupported	The specified Spec is not supported.
400	InvalidInstance.StatusError	The router instance status error.	The status of the instance is invalid.
400	InvalidOpposite.NotFound	The opposite does not exist.	The peer does not exist.
404	InvalidRouterInterfaceId.NotFound	The specified RouterInterfaceId does not exist in our record.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.