Resume Suspended Express Connect Circuits via RecoverPhysicalConnection API - Express Connect - Alibaba Cloud - Express Connect

Operation description

You can call the RecoverPhysicalConnection operation to recover access to an Express Connect circuit that has been terminated. Currently, only shared Express Connect circuits can be recovered.

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:RecoverPhysicalConnection

update

*PhysicalConnection

acs:vpc:{#regionId}:{#accountId}:physicalconnection/{#physicalconnectionId}

None

Request parameters

Parameter	Type	Required	Description	Example
InstanceId	string	Yes	The instance ID of the Express Connect circuit. Note Currently, only shared Express Connect circuits can be recovered.	pc-bp1mrgfbtmc9brre7****
Token	string	No	The client token that is used to ensure the idempotence of the request. The client generates the value of this parameter. The value must be unique among different requests and cannot exceed 64 ASCII characters in length.	CBCE910E-D396-4944-8****
DryRun	boolean	No	Specifies whether to perform a dry run. Valid values: true: performs a dry run without recovering access to the Express Connect circuit. The system checks the required parameters, request format, and instance status. If the check fails, the corresponding error is returned. If the check succeeds, the request ID is returned. false (default): sends the request. After the request passes the check, access to the Express Connect circuit is recovered.	false
RegionId	string	Yes	The region ID of the Express Connect circuit. You can call the DescribeRegions operation to query the region ID.	cn-hangzhou

Response elements

Element	Type	Description	Example
	object	The response.
RequestId	string	The request ID.	CD14EA74-E9C3-59A9-942A-DFEC7E12818D

Examples

Success response

JSON format

{
  "RequestId": "CD14EA74-E9C3-59A9-942A-DFEC7E12818D"
}

Error codes

HTTP status code	Error code	Error message	Description
400	IncorrectStatus.PhysicalConnection	The status of %s is incorrect.	The operation failed because the status of the Express Connect circuit is invalid.
400	ResourceNotFound	The specified resource %s is not found.	The specified resource %s is not found.
400	OperationDenied.TerminateVirtualPhysicalConnection	The operation is not allowed because of TerminateVirtualPhysicalConnection.	The VirtualPhysicalConnection does not have permission or is in arrears, the operation is not allowed
400	OperationDenied.PconnNotAllowRecover	Exclusive physical connection does not allow recovery.	The current resource cannot perform this operation. Please contact the duty officer for assistance.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.