Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI Studio
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 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 a list of trunk operations
    • 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
    • Overview of operations
    • 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 public connections

Getting information about public connections

Written by
Yandex Cloud
Updated at June 10, 2025

Note

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

CLI
  1. To get information about public connections, see the description of the CLI command:

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

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

    Result:

    +----------------------+--------------------+----------------------+---------------+
    |          ID          |        NAME        | TRUNK CONNECTION ID  | SERVICE TYPES |
    +----------------------+--------------------+----------------------+---------------+
    | euuiog88zphgsq****** | customer-name-pub1 | euuqqctbrflq3i****** | APIGW, ML     |
    | euucr7p47329kq****** | customer-name-pub2 | euuvdjl5shd0fv****** | APIGW, ML     |
    +----------------------+--------------------+----------------------+---------------+
    
  3. Get information about the public connection by specifying its ID obtained in the previous step:

    # yc cic public-connection get <public_connection_ID>
    yc cic public-connection get euuiog88zphgsq****** 
    

    Result:

    id: euuiog88zphgsq******
    name: customer-name-pub1
    folder_id: b1gqf2hjizv2jw******
    region_id: ru-central1
    trunk_connection_id: euuqqctbrflq3i******
    vlan_id: "1428"
    ipv4_peering:
      peering_subnet: 178.170.2xx.x2/31
      peer_ip: 178.170.2xx.x2
      cloud_ip: 178.170.2xx.x3
      peer_bgp_asn: "65001"
      cloud_bgp_asn: "200350"
    ipv4_allowed_service_types:
      - CLOUD_SERVICE_APIGW
      - CLOUD_SERVICE_ML
    ipv4_peer_announced_prefixes:
      - 178.170.2xx.x2/31
    

    Where:

    • id: Public connection ID.
    • name: Public connection name.
    • folder_id: ID of the cloud folder containing the new public connection.
    • region_id: Region of the cloud containing the new public connection.
    • trunk_connection_id: ID of the trunk link containing the new public connection.
    • vlan_id: public connection VLAN ID.
    • IP and BGP connectivity settings for the public 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.
    • ipv4_allowed_service_types: IDs of the services with their IP prefixes announced in the public connection.
    • ipv4_peer_announced_prefixes: List of client IP prefixes (if any) allowed to send traffic to the public connection.

Was the article helpful?

Previous
Deleting a private connection
Next
Getting information about a routing instance
© 2025 Direct Cursus Technology L.L.C.