Yandex Cloud
Поиск
Связаться с намиПодключиться
  • Истории успеха
  • Документация
  • Блог
  • Все сервисы
  • Статус работы сервисов
    • Популярные
    • Инфраструктура и сеть
    • Платформа данных
    • Контейнеры
    • Инструменты разработчика
    • Бессерверные вычисления
    • Безопасность
    • Мониторинг и управление ресурсами
    • ИИ для бизнеса
    • Бизнес-инструменты
  • Все решения
    • По отраслям
    • По типу задач
    • Экономика платформы
    • Безопасность
    • Техническая поддержка
    • Каталог партнёров
    • Обучение и сертификация
    • Облако для стартапов
    • Облако для крупного бизнеса
    • Центр технологий для общества
    • Облако для интеграторов
    • Поддержка IT-бизнеса
    • Облако для фрилансеров
    • Обучение и сертификация
    • Блог
    • Документация
    • Контент-программа
    • Мероприятия и вебинары
    • Контакты, чаты и сообщества
    • Идеи
    • Тарифы Yandex Cloud
    • Промоакции и free tier
    • Правила тарификации
  • Истории успеха
  • Документация
  • Блог
Проект Яндекса
© 2025 ООО «Яндекс.Облако»
Terraform в Yandex Cloud
  • Начало работы
  • Библиотека решений
    • Обзор
    • История изменений (англ.)
          • vpc_address
          • vpc_default_security_group
          • vpc_gateway
          • vpc_network
          • vpc_private_endpoint
          • vpc_route_table
          • vpc_security_group
          • vpc_security_group_rule
          • vpc_subnet

В этой статье:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for object_storage
  • Nested Schema for dns_options
  • Nested Schema for endpoint_address
  • Nested Schema for timeouts
  • Import
  1. Справочник Terraform
  2. Ресурсы (англ.)
  3. Virtual Private Cloud (VPC)
  4. Resources
  5. vpc_private_endpoint

yandex_vpc_private_endpoint (Resource)

Статья создана
Yandex Cloud
Обновлена 11 сентября 2025 г.
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for object_storage
    • Nested Schema for dns_options
    • Nested Schema for endpoint_address
    • Nested Schema for timeouts
  • Import

Manages a VPC Private Endpoint within the Yandex Cloud. For more information, see the official documentation.

  • How-to Guides
    • Cloud Networking

Example usageExample usage

//
// Create a new VPC Private Endpoint.
//
resource "yandex_vpc_private_endpoint" "my_pe" {
  name        = "object-storage-private-endpoint"
  description = "description for private endpoint"

  labels = {
    my-label = "my-label-value"
  }

  network_id = yandex_vpc_network.lab-net.id

  object_storage {}

  dns_options {
    private_dns_records_enabled = true
  }

  endpoint_address {
    subnet_id = yandex_vpc_subnet.lab-subnet-a.id
  }
}

// Auxiliary resources
resource "yandex_vpc_network" "lab-net" {
  name = "lab-network"
}

resource "yandex_vpc_subnet" "lab-subnet-a" {
  v4_cidr_blocks = ["10.2.0.0/16"]
  zone           = "ru-central1-a"
  network_id     = yandex_vpc_network.lab-net.id
}

SchemaSchema

RequiredRequired

  • network_id (String) ID of the network which private endpoint belongs to.
  • object_storage (Block List, Min: 1, Max: 1) Private endpoint for Object Storage. (see below for nested schema)

OptionalOptional

  • description (String) The resource description.
  • dns_options (Block List, Max: 1) Private endpoint DNS options block. (see below for nested schema)
  • endpoint_address (Block List, Max: 1) Private endpoint address specification block.

Важно

Only one of address_id or subnet_id + address arguments can be specified. (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.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • name (String) The resource name.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • created_at (String) The creation timestamp of the resource.
  • id (String) The ID of this resource.
  • status (String) Status of the private endpoint.

Nested Schema for Nested Schema for object_storage

Nested Schema for Nested Schema for dns_options

Optional:

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

Nested Schema for Nested Schema for endpoint_address

Optional:

  • address (String) Specifies IP address within subnet_id.
  • address_id (String) ID of the address.
  • subnet_id (String) Subnet of the IP address.

Nested Schema for Nested Schema for timeouts

Optional:

  • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
  • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
  • update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

ImportImport

The resource can be imported by using their resource ID. For getting the resource ID you can use Yandex Cloud Web Console or YC CLI.

# terraform import yandex_vpc_private_endpoint.<resource Name> <resource Id>
terraform import yandex_vpc_private_endpoint.my_pe ...

Была ли статья полезна?

Предыдущая
vpc_network
Следующая
vpc_route_table
Проект Яндекса
© 2025 ООО «Яндекс.Облако»