ConnectRouterInterface - Elastic Compute Service - Alibaba Cloud Documentation Center

Note

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

update

*RouterInterface

acs:vpc:{#regionId}:{#accountId}:routerinterface/{#RouterInterfaceId}

None

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The ID of the region where the router interface is located.
RouterInterfaceId	string	Yes	The ID of the initiator router interface.

Response elements

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

Examples

Success response

JSON format

{
  "RequestId": ""
}

Error codes

HTTP status code	Error code	Error message	Description
400	IncorrectRole.NotInitiatingSide	The specified RouterInterface is not InitiatingSide.	The specified router interface is not an initiator. Select an initiator router interface.
400	IncorrectStatus	RouterInterface can be operated by this action only when it??s status is Idle.
400	IncorrectOppositeInterfaceInfo.NotSet	OppositeInterfaceId/OppositeRouterId/OppositeRouterType/OppositeInterfaceOwnerId must be all set.
400	IncorrectOppositeInterfaceInfo	Cannot connect on the same router	You cannot connect a router to itself.
400	Forbidden.OnlyOneConnection	The Specified routers have a connection already
400	Forbidden.BillsOutstanding	You cannot use this action because you have bills outstanding.
400	InvalidAccount.NotFound	The specified account is not exists.
400	ErrCode.Invalid	got error
400	AttrMismatching.AcceptingSideRole	%s
400	AttrMismatching.AcceptingSideInstanceId	%s
400	AttrMismatching.AcceptingSideRegionNo	%s
400	AttrMismatching.AcceptingSideRouterId	%s
400	AttrMismatching.AcceptingSideRouterType	%s
400	AttrMismatching.AcceptingSideAliUid	%s
400	AttrMismatching.AcceptingSideOppositeInterfaceOwnerId	%s
400	AttrMismatching.AcceptingSideOppositeRegionNo	%s
400	AttrMismatching.AcceptingSideOppositeInterfaceId	%s
400	AttrMismatching.AcceptingSideOppositeRouterId	%s
400	AttrMismatching.AcceptingSideOppositeRouterType	%s
400	IllegalParam.InstanceOwner	The router instance owener error.
404	InvalidRegionId.NotFound	The RegionId provided does not exist in our records.	Region information error
404	InvalidRouterInterfaceId.NotFound	The specified RouterInterfaceId does not exist in our record.	The specified router interface does not exist. Check whether the router interface ID is valid.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.