/v2/partner_network_connect/attachmentsCreate a partner attachment
Creates a partner attachment that connects VPCs through a partner network provider. Supply name, connection_bandwidth_in_mbps, region, naas_provider, and vpc_ids; the name must use alphanumeric characters, dashes, or periods, and the bandwidth and region must be supported values. A 202 response returns attachment details, including attached VPC network IDs and BGP configuration information.
- IdempotentThe SDK sends
Idempotency-Key, so a retried request is only applied once.
Partner attachment configuration. Include name, connection_bandwidth_in_mbps, region, naas_provider, and vpc_ids; parent_uuid, bgp, and redundancy_zone are optional.
A 401 is returned when authentication credentials are invalid; a 404 when a referenced resource is not found; a 422 when the request cannot be processed; a 429 when the API rate limit is exceeded; and a 500 when a server error occurs. If you submit a body, include name, connection_bandwidth_in_mbps, region, naas_provider, and vpc_ids; vpc_ids must contain at least one item, and any bgp object must include local_router_ip, peer_router_ip, peer_router_asn, and auth_key. name, connection_bandwidth_in_mbps, region, and redundancy_zone must match their declared pattern or allowed values.