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
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
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

In this article:

  • Creating a direct trunk
  • Creating a trunk via a partner
  1. Step-by-step guides
  2. Creating a trunk

Creating a new trunk

Written by
Yandex Cloud
Updated at June 10, 2025
  • Creating a direct trunk
  • Creating a trunk via a partner

Warning

To request access to this function, contact support.

Creating a direct trunkCreating a direct trunk

Note

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

CLI
  1. See the description of the CLI command for creating a trunk:

    yc cic trunk-connection create --help
    
  2. Create a direct trunk in the specified folder:

    yc cic trunk-connection create --name trunk-m9 \
      --description "Trunk M9" \ 
      --pop ru-msk-m9-0 \
      --capacity 1-gbps \
      --trunk-options type=direct,transceiver=10GBASE-LR \ 
      --deletion-protection \
      --folder-id b1gqf**********jiz2w \
      --async
    

    Expected result:

    id: cf3td**********nufvr
    name: trunk-m9
    description: Trunk M9
    cloud_id: b1g7a**********kd23p
    folder_id: b1gqf**********jiz2w
    region_id: ru-central1
    created_at: "2025-03-25T10:54:46Z"
    single_port_direct_joint:
      transceiver_type: TRANSCEIVER_TYPE_10GBASE_LR
      port_name: 25GE1/0/12
    point_of_presence_id: ru-msk-m9-0
    capacity: CAPACITY_1_GBPS
    status: ACTIVE
    

    Where:

    • id: Trunk ID.
    • name: Trunk name.
    • description: Trunk description.
    • cloud_id: ID of the cloud in whose folder the trunk was created.
    • folder_id: ID of the cloud folder the trunk was created in.
    • region_id: Region of the cloud containing the trunk.
    • Trunk type:
      • single_port_direct_joint: Direct trunk:
        • transceiver_type: Transceiver type in use.
        • port_name: Port number(s) allocated for the trunk on the network device.
        • access_device_name: Name of the network device with ports allocated for the trunk.
      • lag_direct_joint: Aggregated (LAG) direct trunk:
        • transceiver_type: Transceiver type in use.
        • lag_id: Aggregated connection ID.
        • port_names: List of physical ports in the LAG.
      • partner_joint_info: Partner trunk:
        • partner_id: Partner ID.
        • service_key: Partner trunk service key.
    • point_of_presence_id: Point of presence ID. When creating a trunk, you must select the required value from the Label column of the table.
    • capacity: Trunk capacity. When creating a trunk, you must select the required value from the Label column of the table.
    • status: Resource state. Target state: ACTIVE.
    • created_at: Date and time of resource creation.
    • deletion-protection: Resource protection against accidental deletion. You will not be able to delete the resource unless this flag is removed first.
    • async: Running the operation in asynchronous mode. We recommend you to perform all resource state change operations in this mode.

Creating a trunk via a partnerCreating a trunk via a partner

CLI
  1. See the description of the CLI command for creating a trunk:

    yc cic trunk-connection create --help
    
  2. Get the required partner connection ID:

    yc cic partner list
    
  3. Create a partner trunk in the specified folder:

    yc cic trunk-connection create --name trunk-m9 \
      --description "Trunk M9" \
      --pop ru-msk-m9-0 \
      --capacity 500-mbps \
      --trunk-options type=partner,partner-id=partnerID \
      --folder-id b1gqf**********jiz2w \
      --async
    

    Note

    When creating it, specify partner ID and do not specify transceiver type.

    Expected result:

    id: cf3td**********nufvr
    name: trunk-m9
    description: Trunk M9
    cloud_id: b1g7a**********kd23p
    folder_id: b1gqf**********jiz2w
    region_id: ru-central1
    created_at: "2025-03-25T10:54:46Z"
    partner_joint_info:
      partner_id: partnerID
      service_key: euucl**********bdga6
    point_of_presence_id: ru-msk-m9-0
    capacity: CAPACITY_500_MBPS
    status: ACTIVE
    
  4. Create a new support ticket to inform your partner about the trunk you created.

    Follow this request format:

    Subject: [CIC] Notification to _partnerID_ about the Cloud Interconnect trunk that has been created.
    
    
    Request text: Please notify the partner about the parameters of the new trunk trunk_id: euus5dfgchu2********
    
    

    Note

    The support engineer will process the ticket and notify the partner about the new trunk.

    The following data will be sent to the partner: partner_joint_id, partner_vlan_id, capacity, and service_key.

Was the article helpful?

Previous
Getting information about trunk links
Next
Updating trunk parameters
Yandex project
© 2025 Yandex.Cloud LLC