DeleteCenChildInstanceRouteEntryToAttachment - Cloud Enterprise Network

Operation description

You can delete route entries from Virtual Private Cloud (VPC) instances and virtual border router (VBR) instances only if the next hop of the route entry is a transit router connection (a network instance connection).
DeleteCenChildInstanceRouteEntryToAttachment is an asynchronous operation. After you send a request, the system returns a RequestId, but the route entry is still being deleted in the background. You can call the DescribeRouteEntryList operation for VPC to query the status of the route entry.
- If a route entry is in the Deleting state, it is being deleted. During this time, you can only query the route entry and cannot perform other operations on it.
- If you cannot find the specified route entry, it has been deleted.

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 support 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

cen:DeleteCenChildInstanceRouteEntryToAttachment

delete

*CenInstance

acs:cen:*:{#accountId}:ceninstance/{#ceninstanceId}

None

Request parameters

Parameter	Type	Required	Description	Example
ClientToken	string	No	The client token that is used to ensure the idempotence of the request. Generate a token from your client to make sure that the token is unique among different requests. The token can contain only ASCII characters. Note If you do not specify this parameter, the system automatically uses the RequestId of the request as the ClientToken. The RequestId may be different for each request.	02fb3da4-130e-11e9-8e44-001****
DryRun	boolean	No	Specifies whether to perform a dry run. A dry run checks for potential issues, including permissions and instance status. Valid values: false (default): Sends a normal request. The route entry of the network instance is deleted after the request passes the check. true: Sends a check request. The system checks the required parameters and the request format. If the check fails, an error message is returned. If the check succeeds, the corresponding request ID is returned. The route entry of the network instance is not deleted. Note This parameter is not in effect.	false
CenId	string	Yes	The ID of the Cloud Enterprise Network (CEN) instance.	cen-wgcl0ik5o8jakq****
TransitRouterAttachmentId	string	Yes	The ID of the network instance connection.	tr-attach-r1qhupkc19iadz****
RouteTableId	string	Yes	The ID of the route table that belongs to the network instance.	vtb-bp1osd9opvegfpowc****
DestinationCidrBlock	string	Yes	The destination CIDR block of the route entry.	10.0.1.0/24

Response parameters

Parameter	Type	Description	Example
	object	The returned data.
RequestId	string	The request ID.	250E717B-9823-5FD8-A1C6-5714234FB825

Examples

Success response

JSON format

{
  "RequestId": "250E717B-9823-5FD8-A1C6-5714234FB825"
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidRouteEntry.NotFound	Route entry not exists.	The error message returned because the route entry does not exist.
400	IncorrectStatus.VpcRouteEntry	The resource is not in a valid state for the attachment operation.	The error message returned because the status of the VPC route entry does not support this operation. Try again later.
400	InvalidTransitRouterAttachmentId.NotFound	TransitRouterAttachmentId is not found.	The error message returned because the ID of the network instance does not exist.
400	IncorrectStatus.Vpc	The resource is not in a valid state for the attachment operation.	The error message returned because the status of the VPC does not support this operation. Try again later.
400	InvalidCidrBlock.Malformed	The specified CIDR block is not valid.	The error message returned because the specified CIDR block is invalid.
400	InvalidParameter	Invalid parameter.	The error message returned because the parameter is set to an invalid value.
400	Unauthorized	The AccessKeyId is unauthorized.	The error message returned because you do not have the permissions to perform this operation.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.