：CreateTransitRouterVpcAttachment

Usage notes

• You can use the following methods to create a VPC connection on an Enterprise Edition transit router:
  • If an Enterprise Edition transit router is already created in the region where you want to create a VPC connection, set VpcId, ZoneMappings.N.VSwitchId, ZoneMappings.N.ZoneId, and TransitRouterId.
  • If no Enterprise Edition transit router is created in the region where you want to create a VPC connection, set VpcId, ZoneMappings.N.VSwitchId, ZoneMappings.N.ZoneId, CenId, and RegionId. When you create a VPC connection, the system automatically creates an Enterprise Edition transit router in the specified region.
• CreateTransitRouterVpcAttachment is an asynchronous operation. After you send a request, the VPC connection ID is returned but the operation is still being performed in the system background. You can call ListTransitRouterVpcAttachments to query the status of a VPC connection.
  • If a VPC is in the Attaching state, the VPC connection is being created. You can query the VPC connection but cannot perform other operations.
  • If a VPC connection is in the Attached state, the VPC connection is created.
• By default, route learning and associated forwarding are disabled between transit router route tables and VPC connections.

Prerequisites

Before you call this operation, make sure that the following requirements are met:

• At least one vSwitch is deployed for the VPC in the zones supported by Enterprise Edition transit routers. Each vSwitch must have at least one idle IP address. For more information, see Regions and zones supported by Enterprise Edition transit routers.
• To connect to a network instance that belongs to another Alibaba Cloud account, you must first acquire the required permissions from the account. For more information, see Acquire permissions to connect to a network instance that belongs to another account.
• VPC connections incur fees. Take note of the billing rules of VPC connections before you create a VPC connection. For more information, see Billing.

Request parameters

Response parameters

Examples

Sample requests

http(s)://[Endpoint]/?Action=CreateTransitRouterVpcAttachment
&ClientToken=02fb3da4-130e-11e9-8e44-001****
&CenId=cen-j3jzhw1zpau2km****
&TransitRouterId=tr-bp1su1ytdxtataupl****
&RegionId=cn-hangzhou
&TransitRouterAttachmentName=testname
&TransitRouterAttachmentDescription=testname
&VpcId=vpc-bp1kbjcre9vtsebo1****
&VpcOwnerId=1250123456123456
&ChargeType=POSTPAY
&DryRun=false
&ZoneMappings=[{"VSwitchId":"vsw-bp1a214sbus8z3b54****","ZoneId":"cn-hangzhou-h"}]
&Tag=[{"Key":"tagtest","Value":"tagtest"}]
&<Common request parameters>

Sample success responses

XML format

HTTP/1.1 200 OK
Content-Type:application/xml

<CreateTransitRouterVpcAttachmentResponse>
    <TransitRouterAttachmentId>tr-attach-ia340z7xis7t5s****</TransitRouterAttachmentId>
    <RequestId>C087A369-82B9-43EF-91F4-4B63A9C6E6B6</RequestId>
</CreateTransitRouterVpcAttachmentResponse>

JSON format

HTTP/1.1 200 OK
Content-Type:application/json

{
  "TransitRouterAttachmentId" : "tr-attach-ia340z7xis7t5s****",
  "RequestId" : "C087A369-82B9-43EF-91F4-4B63A9C6E6B6"
}

Error codes

For a list of error codes, see Service error codes.