Resumes an Express Connect circuit.

Operation description

Description

You can call this API operation to resume a suspended Express Connect circuit. You can resume only shared Express Connect circuits by calling this API operation.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

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.

Operation	Access level	Resource type	Condition key	Associated operation
vpc:RecoverPhysicalConnection	update	PhysicalConnection acs:vpc:{#regionId}:{#accountId}:physicalconnection/{#physicalconnectionId}	none	none

Request parameters

Parameter	Type	Required	Description	Example
InstanceId	string	Yes	The ID of the Express Connect circuit. Note You can resume only shared Express Connect circuits by calling this API operation.	pc-bp1mrgfbtmc9brre7****
Token	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 token can contain only ASCII characters and cannot exceed 64 characters in length.	CBCE910E-D396-4944-8****
DryRun	boolean	No	Specifies whether to perform only a dry run, without performing the actual request. Valid values: true: performs only a dry run. The system checks the request for potential issues, including missing parameter values, incorrect request syntax, and instance status. If the request fails the dry run, an error message is returned. If the request passes the dry run, the request ID is returned. false (default): performs a dry run and performs the actual request. If the request passes the dry run, a 2xx HTTP status code is returned and the operation is performed.	false
RegionId	string	Yes	The region ID of the Express Connect circuit. You can call the DescribeRegions operation to query the most recent region list.	cn-hangzhou

Response parameters

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

Examples

Sample success responses

JSONformat

{
  "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.

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

Change history

Change time	Summary of changes	Operation
2024-06-13	The Error code has changed	View Change Details
2024-01-04	The Error code has changed	View Change Details
2021-09-27	Add Operation	View Change Details