Creating a private connection

Written by

Yandex Cloud

Updated at July 3, 2025

Warning

To request access to this function, contact support.

Note

You need the cic.editor role to run this operation.

CLI

View the description of the CLI command to create a private connection:
```
yc cic private-connection create --help
```
Create a private connection:
```
yc cic private-connection create --name prc-pop1 \
  --description "Private connection #1 via POP-1" \ 
  --trunk-id cf3td**********nufvr \
  --vlan-id 125 \
  --ipv4-peering peering-subnet=192.168.10.0/30,peer-ip=192.168.10.1,cloud-ip=192.168.10.2,peer-bgp-asn=65202 \
  --async
```
Note

By default, the private connection will be created in the same folder as the trunk. To simplify maintenance, it is best not create trunks and private connections in different folders.

Expected result:
```
id: cca59**********dvjir
name: prc-pop1
folder_id: b1gqf**********jiz2w
region_id: ru-central1
trunk_connection_id: cf3td**********nufvr
vlan_id: "125"
ipv4_peering:
  peering_subnet: 192.168.10.0/30
  peer_ip: 192.168.10.1
  cloud_ip: 192.168.10.2
  peer_bgp_asn: "20001"
  peer_bgp_md5_key: '*** hidden ***'
status: ACTIVE
created_at: "2025-03-20T08:25:33Z"
```
Where:
- id: Private connection ID.
- name: Private connection name.
- description: Private connection description.
- folder_id: ID of the cloud folder the private connection was created in.
- region_id: Cloud region the private connection was created in.
- trunk_connection_id: ID of the trunk the private connection was created in.
- vlan_id: VLAN ID for the private connection in 802.1Q trunk. This value is selected by the customer. It must be different from the VLAN IDs of the previously set up private connections in this trunk.
- ipv4_peering: Group of IP/BGP connectivity parameters for the private connection:
  - peering_subnet: Point-to-point subnet for BGP peering. This value is selected by the customer.
  - peer_ip: Customer endpoint IP address on the point-to-point peering subnet. This value is selected by the customer.
  - cloud_ip: Yandex Cloud endpoint IP address on the point-to-point peering subnet. This value is selected by the customer.
  - peer_bgp_asn: Customer endpoint BGP ASN in ASPlain format. This value is selected by the customer.
  - peer_bgp_md5_key: Optional parameter. Encrypted BGP session key value.
- status: Resource state. Target state: ACTIVE.
- created_at: Date and time of resource creation.
- async: Running the operation in asynchronous mode. This is the recommended mode for all operations that involve changes to resources.

Creating a private connection

Was the article helpful?