Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Interconnect
    • All guides
    • Getting information about Cloud Interconnect partners
    • Getting information about Cloud Interconnect points of presence
    • Getting information about trunk links
    • Creating a trunk
    • Updating trunk parameters
    • Getting information about operations in a trunk
    • Deleting a trunk
    • Getting information about private connections
    • Creating a private connection
    • Updating private connection parameters
    • Getting a list of operations for a private connection
    • Updating the list of static routes for a private connection
    • Removing static routes for a private connection
    • Deleting a private connection
    • Getting information about public connections
    • Getting information about a routing instance
    • Overview
    • Operation overview
    • Terminology
    • Points of presence
    • Transceivers
    • Trunk
    • Private connection
    • Public connection
    • CIC partners
    • Monitoring
    • Data size and connection capacity
    • Quotas and limits
  • Pricing policy
  • Access management
  • Release notes
  1. Step-by-step guides
  2. Getting information about private connections

Getting information about a private connection

Written by
Yandex Cloud
Updated at July 3, 2025

Note

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

CLI
  1. View the description of the CLI command to get information about a private connection:

    yc cic private-connection get --help
    
  2. Get a list of private connections in the specified folder:

    yc cic private-connection list --folder-id b1gqf2hjizv2jw******
    

    Result:

    +----------------------+--------------------+----------------------+
    |          ID          |        NAME        | TRUNK CONNECTION ID  |
    +----------------------+--------------------+----------------------+
    | euuiog88zphgsq****** | customer-name-prc1 | euuqqctbrflq3i****** |
    | euucr7p47329kq****** | customer-name-prc2 | euuvdjl5shd0fv****** |
    +----------------------+--------------------+----------------------+      
    
  3. Get information about the private connection by specifying its ID obtained in the previous step:

    # yc cic private-connection get <private_connection_ID>
    yc cic private-connection get euuiog88zphgsq******
    

    Result:

    id: euuiog88zphgsq******
    name: customer-name-prc1
    folder_id: b1gqf2hjizv2jw******
    region_id: ru-central1
    trunk_connection_id: euuqqctbrflq3i******
    vlan_id: "1531"
    ipv4_peering:
      peering_subnet: 10.211.10.0/30
      peer_ip: 10.211.10.1
      cloud_ip: 10.211.10.2
      peer_bgp_asn: "64515"
      cloud_bgp_asn: "200350"
    

    Where:

    • id: Private connection ID.
    • name: Private connection name.
    • folder_id: ID of the cloud folder where you created the private connection.
    • region_id: Region of the cloud where you created the private connection.
    • trunk_connection_id: ID of the trunk link containing the private connection.
    • vlan_id: Private connection VLAN ID.
    • IP and BGP connectivity settings for the private connection point-to-point subnet:
      • peering_subnet: Point-to-point subnet for BGP peering.
      • peer_ip: Customer endpoint IP address on the point-to-point peering subnet.
      • cloud_ip: Yandex Cloud endpoint IP address on the point-to-point peering subnet.
      • peer_bgp_asn: BGP ASN on the customer's equipment.
      • cloud_bgp_asn: BGP ASN on the Yandex Cloud equipment.

Was the article helpful?

Previous
Deleting a trunk
Next
Creating a private connection
© 2025 Direct Cursus Technology L.L.C.