All Products
Search
Document Center

Virtual Private Cloud:ModifyRouterInterfaceSpec

Last Updated:Mar 04, 2024

Modifies the specification of a router interface.

Operation description

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

Note You cannot modify the specification of a router interface that has overdue payments.

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
vpc:ModifyRouterInterfaceSpecWrite
  • RouterInterface
    acs:vpc:{#regionId}:{#accountId}:routerinterface/{#RouterInterfaceId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
RegionIdstringYes

The ID of the region where the router interface is deployed.

You can call the DescribeRegions operation to query the most recent region list.

cn-hangzhou
RouterInterfaceIdstringYes

The ID of the router interface.

ri-2zeo3xzyf38r4urzd****
SpecstringYes

The specification of the router interface. Valid specifications and bandwidth values:

  • Mini.2: 2 Mbit/s
  • Mini.5: 5 Mbit/s
  • Small.1: 10 Mbit/s
  • Small.2: 20 Mbit/s
  • Small.5: 50 Mbit/s
  • Middle.1: 100 Mbit/s
  • Middle.2: 200 Mbit/s
  • Middle.5: 500 Mbit/s
  • Large.1: 1,000 Mbit/s
  • Large.2: 2,000 Mbit/s
  • Large.5: 5,000 Mbit/s
  • Xlarge.1: 10,000 Mbit/s
Note When Role is set to AcceptingSide, set Spec to Negative.
Small.1
ClientTokenstringNo

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 client token can contain only ASCII characters.

Note If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.
02fb3da4-130e-11e9-8e44-0016e04115b

Response parameters

ParameterTypeDescriptionExample
object

The specification of the router interface.

Specstring

The specification of the router interface. Valid values:

  • Mini.2: 2 Mbit/s
  • Mini.5: 5 Mbit/s
  • Small.1: 10 Mbit/s
  • Small.2: 20 Mbit/s
  • Small.5: 50 Mbit/s
  • Middle.1: 100 Mbit/s
  • Middle.2: 200 Mbit/s
  • Middle.5: 500 Mbit/s
  • Large.1: 1,000 Mbit/s
  • Large.2: 2,000 Mbit/s
  • Large.5: 5,000 Mbit/s
  • Xlarge.1: 10,000 Mbit/s
Small.1
RequestIdstring

The request ID.

4EC47282-1B74-4534-BD0E-403F3EE64CAF

Examples

Sample success responses

JSONformat

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

Error codes

HTTP status codeError codeError messageDescription
400Forbidden.FinancialLockedRouterInterface can not be operated by this action when it?s FinancialLocked.-
400InvalidParam.NotFoundParameter must not be null,uid, bid,regionNo, remoteRegionNo or routerId-
400InvalidOppositeRegionId.NotFoundThe OppositeRegionId provided does not exist in our records.The peer region does not exist.
400InvalidInstanceOwner.ErrorThe router instance owner error.The instance owner information is invalid.
400InvalidRouterInterfaceSpec.MalformedSpecified RouterInterface spec is not valid.The RouterInterface Spec parameter is set to an invalid value.
400IllegalParam.chargeTypeRouterInterface chargeType different.-
400ResourceQueryErrorThe specified resource is queried error.An error occurred while querying the specified resource.
400 InvalidSpec.ValueNotSupportedThe specified Spec is not supported.-
400InvalidSpec.ValueNotSupportedThe specified Spec is not supported.-
400InvalidInstance.StatusErrorThe router instance status error.The status of the instance is invalid.
400InvalidOpposite.NotFoundThe opposite does not exist.The peer does not exist.
404InvalidRouterInterfaceId.NotFoundThe specified RouterInterfaceId does not exist in our record.The specified router interface does not exist.

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

Change history

Change timeSummary of changesOperation
2023-12-21API Description Update. The API operation is not deprecated.. The Error code has changedsee changesets
Change itemChange content
API DescriptionAPI Description Update.
API Deprecation DescriptionThe API operation is not deprecated..
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 404
2021-11-17The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 404
2021-11-17The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
    delete Error Codes: 404