Yandex Cloud
Search
Contact UsTry it for free
  • 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
    • Price calculator
    • Pricing plans
  • 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_default_security_group
          • 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 dns_record
  • Nested Schema for external_ipv4_address
  • Nested Schema for timeouts
  • Import
  1. Terraform reference
  2. Resources
  3. Virtual Private Cloud (VPC)
  4. Resources
  5. vpc_address

yandex_vpc_address (Resource)

Written by
Yandex Cloud
Updated at September 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.

Warning

Either one address or zone_id arguments can be specified.

Warning

Either one ddos_protection_provider or outgoing_smtp_capability arguments can be specified.

Warning

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 ...

Was the article helpful?

Previous
vpc_subnet
Next
vpc_default_security_group
© 2025 Direct Cursus Technology L.L.C.