Call UpdateTransitRouterVpnAttachmentAttribute to modify VPN attachment attributes - Cloud Enterprise Network

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

cen:UpdateTransitRouterVpnAttachmentAttribute

update

*TransitRouterVpnAttachment

acs:cen:*:{#accountId}:centransitrouterattachment/{#centransitrouterattachmentId}

None

Request parameters

Parameter	Type	Required	Description	Example
ClientToken	string	No	A 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 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.	123e4567-e89b-12d3-a456-42665544****
DryRun	boolean	No	Specifies whether to perform a dry run. Valid values: true: Performs a dry run to check the request without modifying the attributes of the VPN connection. The system checks the required parameters, request format, and service limits. If the request fails the check, an error message is returned. If the request passes the check, the `DryRunOperation` error code is returned. false (Default): Sends a normal request. If the request passes the check, the system modifies the attributes of the VPN connection.	false
TransitRouterAttachmentId	string	Yes	The ID of the VPN connection.	tr-attach-a6p8voaodog5c0****
TransitRouterAttachmentName	string	No	The new name of the VPN connection. The name can be empty or 1 to 128 characters in length, and cannot start with http:// or https://.	nametest
TransitRouterAttachmentDescription	string	No	The new description of the VPN connection. The description can be empty or 1 to 256 characters in length, and cannot start with http:// or https://.	desctest
AutoPublishRouteEnabled	boolean	No	Specifies whether to allow the Enterprise Edition transit router to automatically publish routes to the IPsec-VPN connection. Valid values: true: The Enterprise Edition transit router automatically publishes routes to the IPsec-VPN connection. false: The Enterprise Edition transit router does not automatically publish routes to the IPsec-VPN connection.	true

Response elements

Element	Type	Description	Example
	object	The response that is returned.
RequestId	string	The request ID.	1AB038F2-96E5-560B-9F6E-734311D466FA

Examples

Success response

JSON format

{
  "RequestId": "1AB038F2-96E5-560B-9F6E-734311D466FA"
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidTransitRouterAttachmentId.NotFound	TransitRouterAttachmentId is not found.	The error message returned because the ID of the network instance does not exist.
400	IncorrectStatus.TransitRouterAttachmentId	The resource is not in a valid state for the attachment operation.	The error message returned because the operation is not supported when the specified attachment is in an unstable state
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.
400	InvalidParameter.OrderType	The specified parameter OrderType is invalid.	The specified parameter OrderType is invalid.
400	InvalidOperation.OrderTypeMustMatchGrantCrossAccount	The OrderType must be the same as the OrderType in the grant cross-account record.	The OrderType must be the same as the OrderType in the grant cross-account record.
400	OperationFailed.GrantCrossAccountNotExist	Cross-account authorization does not exist.	Cross-account authorization does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.