CreatePhysicalConnection - Elastic Compute Service - Alibaba Cloud Documentation Center

CreatePhysicalConnection

Note

This API has been deprecated. We recommend migrating to Vpc(2016-04-28) - CreatePhysicalConnection for enhanced functionality and continued support. While the deprecated API remains temporarily accessible, no further updates or bug fixes will be provided.

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

create

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The ID of the region where the physical connection is to be created. Call the `DescribeRegions` operation to obtain the latest list of regions.
AccessPointId	string	Yes	The ID of the access point.
Type	string	No	The type of the physical connection. The only supported value is `VPC`, which is also the default.
LineOperator	string	Yes	The connectivity provider. Valid values: `CT`: China Telecom `CU`: China Unicom `CM`: China Mobile `CO`: other Chinese connectivity providers `Equinix` `Interxion` `Other`: other overseas connectivity providers
bandwidth	integer	No	The bandwidth of the physical connection in Mbit/s. Valid values: 2 to 10240. If you omit this parameter, the system applies the default bandwidth for the specified port type.
PeerLocation	string	Yes	The location of the on-premises data center.
PortType	string	No	The port type. Valid values: `100Base-T`: 100 Mbit/s copper port `1000Base-T`: 1 Gbit/s copper port `1000Base-LX`: 1 Gbit/s single-mode optical port (10 km) `10GBase-T`: 10 Gbit/s copper port `10GBase-LR`: 10 Gbit/s single-mode optical port (10 km)
RedundantPhysicalConnectionId	string	No	The ID of the redundant physical connection. The redundant physical connection must be in the Allocated, Confirmed, or Enabled state.
Description	string	No	A description for the physical connection. The description must be 2 to 256 characters long and cannot start with `http://` or `https://`.
Name	string	No	A name for the physical connection. The name must be 2 to 128 characters long and start with a letter. It can contain letters, digits, underscores (_), and hyphens (-). The name cannot start with `http://` or `https://`.
CircuitCode	string	No	The circuit code provided by the connectivity provider.
ClientToken	string	Yes	A client-generated token to ensure request idempotency. You must ensure that the token is unique for each request. The token must consist of only ASCII characters and be no more than 64 characters in length.
ClientToken	string	No	A client-generated token to ensure request idempotency. You must ensure that the token is unique for each request. The token must consist of only ASCII characters and be no more than 64 characters in length.
UserCidr	string	No	The IPv4 CIDR block for the on-premises device.

Response elements

Element	Type	Description	Example
	object	The response data.
PhysicalConnectionId	string	The ID of the physical connection.
RequestId	string	The ID of the request.

Examples

Success response

JSON format

{
  "PhysicalConnectionId": "",
  "RequestId": ""
}

Error codes

HTTP status code	Error code	Error message	Description
400	Invalid.Status	The device or interface status invalid, or has been used..
400	InvalidAccessPointId.NotEnabled	Invalid access point status.
400	InvalidType.Malformd	The Type provided was invalid.	The type is invalid.
400	InvalidPeerLocation.Malformd	The PeerLocation provided was invalid.	The specified PeerLocation parameter is invalid.
400	InvalidLineOperator.Malformd	The LineOperator provided was invalid.	The specified LineOperator parameter is invalid.
400	InvalidPortType.Malformd	The PortType provided was invalid.	The specified PortType parameter is invalid.
400	InvalidDescription.Malformed	The specifid ??Description?? is not valid.
400	InvalidRedundantPhysicalConnectionId.NotFound	The RedundantPhysicalConnectionId does not found.
400	InvalidName.Malformed	The specified ??Name?? is not valid.
400	QuotaExceeded.pConnPerAP	Physical connection count per ap quota exceed.	The maximum number of physical connections per AP has been reached.
400	InvalidBandwidth	invalid physical connection banwidth.	The specified bandwidth value of the physical connection is invalid.
400	InvalidRedundantPhysicalConnection	redundant physical connection doesn't belong to current user.
400	InvalidRedundantPhysicalConnectionStatus	invalid redundant physical connection status.	The state of the standby physical connection is invalid.
400	InvalidCircuitCode.Malformed	circuitCode is illegal.
400	QuotaExceeded.freePconnPerAP	free physical connections count excceeded.	The free quota on physical connections has been used up.
400	InvalidPhysicalConnectionOperator.Malformed	Specified PhysicalConnection Operator is not valid.
400	InvalidPhysicalConnectionPortType.Malformed	Specified PhysicalConnection PortType is not valid.
400	InvalidPhysicalConnectionBandwidth.Malformed	Specified PhysicalConnection Bandwidth is not valid.
400	IllegalParam.ClientToken	Token verify failed because client token length too long.
404	InvalidRegionId.NotFound	The RegionId provided does not exist in our records.	Region information error
404	InvalidAccessPointId.NotFound	The AccessPointId provided does not exist in our records.	The specified AccessPointId parameter does not exist.
404	InvalidPortType.NotFound	There are no resources with the portType.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.