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.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • vpc_address
          • vpc_gateway
          • vpc_network
          • vpc_private_endpoint
          • vpc_route_table
          • vpc_security_group
          • vpc_security_group_rule
          • vpc_subnet

In this article:

  • Example usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for object_storage
  • Nested Schema for dns_options
  • Nested Schema for endpoint_address
  1. Terraform reference
  2. Resources
  3. Virtual Private Cloud (VPC)
  4. Data Sources
  5. vpc_private_endpoint

yandex_vpc_private_endpoint (Data Source)

Written by
Yandex Cloud
Updated at September 11, 2025
  • Example usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for object_storage
    • Nested Schema for dns_options
    • Nested Schema for endpoint_address

Get information about a Yandex VPC Private Endpoint. For more information, see Yandex Cloud VPC.

This data source is used to define VPC Private Endpoint that can be used by other resources.

Warning

One of private_endpoint_id or name should be specified.

Example usageExample usage

//
// Get information about existing VPC Private Endpoint.
//
data "yandex_vpc_private_endpoint" "pe" {
  private_endpoint_id = "my-private-endpoint-id"
}

SchemaSchema

OptionalOptional

  • name (String) The resource name.
  • object_storage (Block List) Private endpoint for Object Storage. (see below for nested schema)
  • private_endpoint_id (String) ID of the private endpoint.

Read-OnlyRead-Only

  • created_at (String) The creation timestamp of the resource.
  • description (String) The resource description.
  • dns_options (List of Object) (see below for nested schema)
  • endpoint_address (List of Object) (see below for nested schema)
  • folder_id (String) The folder identifier that resource belongs to. If it is not provided, the default provider folder-id is used.
  • id (String) The ID of this resource.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • network_id (String) ID of the network which private endpoint belongs to.
  • status (String) Status of the private endpoint.

Nested Schema for Nested Schema for object_storage

Nested Schema for Nested Schema for dns_options

Read-Only:

  • private_dns_records_enabled (Boolean) If enabled - additional service DNS will be created.

Nested Schema for Nested Schema for endpoint_address

Read-Only:

  • address (String) Specifies IP address within subnet_id.

  • address_id (String) ID of the address.

  • subnet_id (String) Subnet of the IP address.

Was the article helpful?

Previous
vpc_network
Next
vpc_route_table
© 2025 Direct Cursus Technology L.L.C.