Queries the status, billing method, zones, vSwitches, and elastic network interfaces (ENIs) of virtual private cloud (VPC) connections.
Operation description
You can use the following methods to query VPC connections on an Enterprise Edition transit router:
- Specify the ID of the Enterprise Edition transit router.
- Specify the ID of the relevant Cloud Enterprise Network (CEN) instance and the region ID of the Enterprise Edition transit router.
- Specify the ID of the region where the Enterprise Edition transit router is deployed.
Debugging
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 |
---|---|---|---|---|
cen:ListTransitRouterVpcAttachments | list | *CenInstance acs:cen:*:{#accountId}:ceninstance/{#ceninstanceId} *TransitRouterVpcAttachment acs:cen:*:{#accountId}:centransitrouterattachment/* *TransitRouterVpcAttachment acs:cen:*:{#accountId}:centransitrouterattachment/{#centransitrouterattachmentId} |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
CenId | string | No | The IDs of the CEN instances. | cen-j3jzhw1zpau2km**** |
RegionId | string | No | The region ID of the Enterprise Edition transit router. You can call the DescribeRegions operation to query the most recent region list. | cn-hangzhou |
TransitRouterAttachmentId | string | No | The ID of the VPC connection. | tr-attach-nls9fzkfat8934**** |
TransitRouterId | string | No | The ID of the Enterprise Edition transit router. | tr-bp1su1ytdxtataupl**** |
MaxResults | integer | No | The number of entries to return on each page. Default value: 20. | 20 |
NextToken | string | No | The token that determines the start point of the query. Valid values:
| FFmyTO70tTpLG6I3FmYAXGKPd**** |
Tag | array<object> | No | The information about the tags. You can specify at most 20 tags in each call. | |
object | No | |||
Key | string | No | The tag key. The tag key cannot be an empty string. The tag key can be up to 64 characters in length and cannot start with You can specify at most 20 tag keys. | tagtest |
Value | string | No | The tag value. The tag value can be 0 to 128 characters in length, and cannot start with Each tag key must have a unique tag value. You can specify at most 20 tag values in each call. | tagtest |
VpcId | string | No | The ID of the VPC. | vpc-bp1kbjcre9vtsebo1**** |
OrderType | string | No | The entity that pays the fees of the network instance. Valid values:
| PayByCenOwner |
Status | string | No | Specifies whether the network instance is attached to the CEN instance. Valid values:
| Attached |
Response parameters
Examples
Sample success responses
JSON
format
{
"NextToken": "FFmyTO70tTpLG6I3FmYAXGKPd****",
"RequestId": "C97FF53F-3EF8-4883-B459-60E171924B23",
"TotalCount": 1,
"MaxResults": 20,
"TransitRouterAttachments": [
{
"CreationTime": "2021-06-15T02:14Z",
"Status": "Attached",
"VpcId": "vpc-bp1h8vbrbcgohcju5****",
"TransitRouterAttachmentId": "tr-attach-nls9fzkfat8934****",
"TransitRouterId": "tr-bp1su1ytdxtataupl****",
"ResourceType": "VPC",
"TransitRouterAttachmentDescription": "testdesc",
"VpcOwnerId": 1250123456123456,
"VpcRegionId": "cn-hangzhou",
"TransitRouterAttachmentName": "testname",
"ZoneMappings": [
{
"ZoneId": "cn-hangzhou-h",
"VSwitchId": "vsw-bp1a214sbus8z3b54****",
"NetworkInterfaceId": "eni-bp149hmyaqegerml****"
}
],
"AutoPublishRouteEnabled": true,
"ChargeType": "POSTPAY",
"Tags": [
{
"Key": "test",
"Value": "test"
}
],
"OrderType": "PayByCenOwner",
"CenId": "cen-j3jzhw1zpau2km****\n",
"TransitRouterVPCAttachmentOptions": {
"key": "{ \"ipv6Support\": \"disable\" }"
}
}
]
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | IllegalParam.NextToken | The specified NextToken is invalid. | The error message returned because the NextToken parameter is set to an invalid value. |
400 | IllegalParam.TrInstance | The specified TransitRouter is invalid. | The error message returned because the TransitRouter parameter is set to an invalid value. |
400 | IllegalParam.Region | The specified Region is invalid. | The error message returned because the specified region is invalid. |
400 | IllegalParam.CenId | The specified CenId is invalid. | The error message returned because the ID of the CEN instance is invalid. |
400 | IllegalParam.TransitRouterId | The specified TransitRouterId is invalid. | The error message returned because the specified transit router ID is invalid. |
400 | IllegalParam.CenIdOrRegionId | The specified CenId or RegionId is invalid. | The error message returned because the specified CEN instance ID or region ID is invalid. |
400 | IllegalParam.MaxResults | The specified MaxResults is illegal. | MaxResults illegal. |
400 | InvalidParameter | Invalid parameter. | The error message returned because the parameter is set to an invalid value. |
400 | Unauthorized | The AccessKeyId is unauthorized. | The error message returned because you do not have the permissions to perform this operation. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-09-10 | The Error code has changed. The response structure of the API has changed | View Change Details |
2024-04-19 | The Error code has changed | View Change Details |
2023-08-04 | The Error code has changed | View Change Details |
2023-03-01 | API Description Update. The Error code has changed. The response structure of the API has changed | View Change Details |
2023-01-06 | The Error code has changed. The request parameters of the API has changed. The response structure of the API has changed | View Change Details |
2022-12-02 | The Error code has changed. The request parameters of the API has changed | View Change Details |
2022-10-19 | The Error code has changed. The response structure of the API has changed | View Change Details |