[Yandex Cloud documentation](../../index.md) > [Yandex Cloud Interconnect](../index.md) > [Step-by-step guides](index.md) > Creating a trunk

# Creating a new trunk

## Creating a direct trunk {#direct}

{% note info %}

You need the [cic.editor](../security/index.md#cic-editor) role to run this operation.

{% endnote %}

{% list tabs group=instructions %}

- Management console {#console}

  1. In the [management console](https://console.yandex.cloud), click ![layout-side-content-left](../../_assets/console-icons/layout-side-content-left.svg) or ![chevron-down](../../_assets/console-icons/chevron-down.svg) in the top panel and select the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder).
  1. [Navigate](../../console/operations/select-service.md#select-service) to **Cloud Interconnect**.
  1. In the left-hand panel, select ![pipeline](../../_assets/console-icons/pipeline.svg) **Trunk connections** and click **Create trunk connection**. In the window that opens:

      1. In the **Connection capacity** field, specify the [traffic packet](../concepts/capacity.md) size for the new trunk.
      1. In the **Point of presence** field, select the required [point of presence](../concepts/pops.md).
      1. In the **Connection type** field, select `Direct`.
      1. In the **Transceiver type** field, select the tranciever type to use on the Cloud Interconnect side. Your hardware must have a compatible tranciever.
      1. Optionally, under **General information**, specify:

          * **Name**. The naming requirements are as follows:

              * Length: between 3 and 63 characters.
              * It can only contain lowercase Latin letters, numbers, and hyphens.
              * It must start with a letter and cannot end with a hyphen.

              If you do not specify a name, the trunk name will be identical to the trunk [ID](../../api-design-guide/concepts/resources-identification.md).
          * Ad hoc trunk **Description**.
          * Trunk [**Labels**](../../resource-manager/concepts/labels.md).
      1. To protect the new trunk from accidental deletion, enable **Deletion protection**.
      1. Click **Create**.

- CLI {#cli}

  1. See the description of the CLI command for creating a [trunk](../concepts/trunk.md):

      ```bash
      yc cic trunk-connection create --help
      ```

  1. Create a direct trunk in the specified folder:



      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](../concepts/transceivers.md) 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](../concepts/transceivers.md) 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](../concepts/pops.md) ID. When creating a trunk, you must select the required value from the _Label_ column of the [table](../concepts/pops.md).
      * `capacity`: Trunk [capacity](../concepts/capacity.md). When creating a trunk, you must select the required value from the _Label_ column of the [table](../concepts/capacity.md).
      * `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 a command in asynchronous mode. We recommend you to perform all resource state change operations in this mode.

{% endlist %}