ModifyPhysicalConnectionAttribute

Note

This API has been deprecated. We recommend migrating to Vpc(2016-04-28) - ModifyPhysicalConnectionAttribute 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:ModifyPhysicalConnectionAttribute

update

*PhysicalConnection

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

None

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The ID of the region where the physical connection is located. To get the latest list of regions, call the `DescribeRegions` operation.
PhysicalConnectionId	string	Yes	The ID of the physical connection.
LineOperator	string	No	The line operator that provides the physical connection.
bandwidth	integer	No	The bandwidth of the physical connection. Unit: Mbit/s.
PeerLocation	string	No	The peer location of the physical connection.
PortType	string	No	The port type of the physical connection.
RedundantPhysicalConnectionId	string	No	The ID of the redundant physical connection.
Description	string	No	The new description of the physical connection.
Name	string	No	The new name of the physical connection.
ClientToken	string	No	A client-generated token to ensure the idempotency of the request. The token must be unique across requests. The client token can contain only ASCII characters and cannot exceed 64 characters in length.
ClientToken	string	No	A client-generated token to ensure the idempotency of the request. The token must be unique across requests. The client token can contain only ASCII characters and cannot exceed 64 characters in length.
UserCidr	string	No	The client-side IP address or CIDR block in your data center. This parameter is used only for outbound traffic shaping.
CircuitCode	string	No	The circuit code of the physical connection, provided by the line operator.

Response elements

Element	Type	Description	Example
	object	The response data.
RequestId	string	The request ID.

Examples

Success response

JSON format

{
  "RequestId": ""
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidLineOperator.Malformd	The LineOperator provided was invalid.	The specified LineOperator parameter is invalid.
400	InvalidPeerLocation.Malformd	The PeerLocation provided was invalid.	The specified PeerLocation 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	InvalidName.Malformed	The specified ??Name?? is not valid.
400	InvalidStatus	invalid physical connection status.	The physical connection state is invalid.
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	InvalidPhysicalConnectionBandwidth.Malformed	Specified PhysicalConnection Bandwidth is not valid.
404	InvalidRegionId.NotFound	The RegionId provided does not exist in our records.	Region information error
404	InvalidPhysicalConnectionId.NotFound	The PhysicalConnectionId provided does not exist in our records.	The specified Express Connect circuit does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.