[Yandex Cloud documentation](../../index.md) > [Yandex Virtual Private Cloud](../index.md) > [Step-by-step guides](index.md) > Service connections > Getting service connection info

# Getting information about a service connection



{% list tabs group=instructions %}

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install).

  The folder used by default is the one specified when [creating](../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id <folder_ID>` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.
  
  1. View the description of the CLI command to get information about a [service connection](../concepts/private-endpoint.md) (private endpoint):

      ```bash
      yc vpc private-endpoint get --help
      ```

  1. Get information about a service connection by specifying its name or ID:

     ```bash
     yc vpc private-endpoint get <service_connection_ID>
     ```

     Result:
     ```text
     id: enpd7***************
     folder_id: b1g23***************
     created_at: "2024-08-31T16:23:33.859574Z"
     name: s3-vpc-link
     description: Private Endpoint to the Object Storage
     network_id: enpgi***************
     status: AVAILABLE
     address:
       subnet_id: e2l8b***************
       address: 10.128.0.10
       address_id: e2ldn***************
     dns_options: {}
     object_storage: {}
     ```

- Terraform

  With [Terraform](https://www.terraform.io/), you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.
  
  Terraform is distributed under the [Business Source License](https://github.com/hashicorp/terraform/blob/main/LICENSE). The [Yandex Cloud provider for Terraform](https://github.com/yandex-cloud/terraform-provider-yandex) is distributed under the [MPL-2.0](https://www.mozilla.org/en-US/MPL/2.0/) license.
  
  For more information about the provider resources, see the guides on the [Terraform](https://www.terraform.io/docs/providers/yandex/index.html) website or [its mirror](../../terraform/index.md).

  If you do not have Terraform yet, [install it and configure the Yandex Cloud provider](../../tutorials/infrastructure-management/terraform-quickstart.md#install-terraform).
  
  
  To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), [authenticate](../../terraform/authentication.md) using the appropriate method.

  To get information about a [service connection](../concepts/private-endpoint.md) through Terraform:

  1. Add the `data` and `output` sections to the Terraform configuration file:

      ```hcl
      data "yandex_vpc_private_endpoint" "my-vpc-data" {
        private_endpoint_id = "<service_connection_ID>"
      }

      output "endpoint-info-network" {
        value = data.yandex_vpc_private_endpoint.my-vpc-info.network_id
      }
      ```

      Where:

      * `data "yandex_vpc_private_endpoint"`: Description of the service connection as a data source:
         * `resource_id`: Service connection ID.
      * `output "ref_description"`: Output variable storing the service connection's network ID (`network_id`):
         * `value`: Return value.

     You can replace `network_id` with any other parameter to get the information you need. For more information about the `yandex_vpc_private_endpoint` data source parameters, see the [relevant provider documentation](../../terraform/data-sources/vpc_private_endpoint.md).

  1. Create the resources:

      1. In the terminal, navigate to the configuration file directory.
      1. Make sure the configuration is correct using this command:
      
         ```bash
         terraform validate
         ```
      
         If the configuration is valid, you will get this message:
      
         ```bash
         Success! The configuration is valid.
         ```
      
      1. Run this command:
      
         ```bash
         terraform plan
         ```
      
         You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.
      1. Apply the configuration changes:
      
         ```bash
         terraform apply
         ```
      
      1. Type `yes` and press **Enter** to confirm the changes.

      Terraform will create the required resources and display their output variables. To check the results, run this command:

      ```bash
      terraform output
      ```

      Result:

      ```text
      endpoint-info-network = "enpt232s2lp6********"
      ```

- API {#api}

  To get information about a [service connection](../concepts/private-endpoint.md), use the [get](../privatelink/api-ref/PrivateEndpoint/get.md) REST API method for the [PrivateEndpoint](../privatelink/api-ref/PrivateEndpoint/index.md) resource or the [PrivateEndpointService/Get](../privatelink/api-ref/grpc/PrivateEndpoint/get.md) gRPC API call.

{% endlist %}