Deletes a router interface.
Operation description
When you call this operation, take note of the following limits:
- You can delete only a router interface that is in the Idle or Inactive state.
- Before you delete a router interface, you must delete all custom route entries destined for the router interface.
Debugging
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 Resourcesis 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.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| vpc:DeleteRouterInterface | Write |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| RegionId | string | Yes | 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-shanghai |
| RouterInterfaceId | string | Yes | The ID of the router interface. | ri-2zeo3xzyf38r4urz**** |
| 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 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.
| 123e4567-e89b-12d3-a456-426655440000 |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "54B48E3D-DF70-471B-AA93-08E683A1B45"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | InvalidInstance.StatusError | The router instance status error. | The status of the instance is invalid. |
| 400 | OperationFailed.OperationLocked | Operation failed because OperationLocked. | The operation failed because the instance is locked due to O&M. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation | ||||||
|---|---|---|---|---|---|---|---|---|
| 2023-12-21 | API Description Update. The Error code has changed | see changesets | ||||||
| ||||||||
| 2023-07-24 | The API operation is not deprecated.. The Error code has changed | see changesets | ||||||
|