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
  • Optional
  • Read-Only
  • Nested Schema for dns_record
  • Nested Schema for external_ipv4_address
  • Nested Schema for timeouts
  • Import
  1. Справочник Terraform
  2. Ресурсы (англ.)
  3. Virtual Private Cloud (VPC)
  4. Resources
  5. vpc_address

yandex_vpc_address (Resource)

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

Manages a address within the Yandex Cloud. You can only create a reserved (static) address via this resource. An ephemeral address could be obtained via implicit creation at a compute instance creation only. For more information, see the official documentation.

  • How-to Guides
    • Cloud Networking
    • VPC Addressing

Example usageExample usage

//
// Create a new VPC regular IPv4 Address.
//
resource "yandex_vpc_address" "addr" {
  name = "exampleAddress"

  external_ipv4_address {
    zone_id = "ru-central1-a"
  }
}
//
// Create a new VPC IPv4 Address with DDoS Protection.
//
resource "yandex_vpc_address" "vpnaddr" {
  name = "vpnaddr"

  external_ipv4_address {
    zone_id                  = "ru-central1-a"
    ddos_protection_provider = "qrator"
  }
}

SchemaSchema

OptionalOptional

  • deletion_protection (Boolean) The true value means that resource is protected from accidental deletion.
  • description (String) The resource description.
  • dns_record (Block List) DNS record specification of address. (see below for nested schema)
  • external_ipv4_address (Block List, Max: 1) Specification of IPv4 address.

Важно

Either one address or zone_id arguments can be specified.

Важно

Either one ddos_protection_provider or outgoing_smtp_capability arguments can be specified.

Важно

Change any argument in external_ipv4_address will cause an address recreate. (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.
  • reserved (Boolean) false means that address is ephemeral.
  • used (Boolean) true if address is used.

Nested Schema for Nested Schema for dns_record

Required:

  • dns_zone_id (String) DNS zone id to create record at.
  • fqdn (String) FQDN for record to address.

Optional:

  • ptr (Boolean) If PTR record is needed.
  • ttl (Number) TTL of DNS record.

Nested Schema for Nested Schema for external_ipv4_address

Optional:

  • ddos_protection_provider (String) Enable DDOS protection. Possible values are: qrator
  • outgoing_smtp_capability (String) Wanted outgoing smtp capability.
  • zone_id (String) The availability zone where resource is located. If it is not provided, the default provider zone will be used.

Read-Only:

  • address (String) Allocated 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_address.<resource Name> <resource Id>
terraform import yandex_vpc_address.addr ...

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

Предыдущая
vpc_subnet
Следующая
vpc_default_security_group
Проект Яндекса
© 2025 ТОО «Облачные Сервисы Казахстан»