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 dns_record
  • Nested Schema for external_ipv4_address
  1. Terraform reference
  2. Resources
  3. Virtual Private Cloud (VPC)
  4. Data Sources
  5. vpc_address

yandex_vpc_address (Data Source)

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

Get information about a Yandex VPC address. For more information, see the official documentation.

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

Warning

One of address_id or name should be specified.

Example usageExample usage

//
// Get information about existing VPC IPv4 Address.
//
data "yandex_vpc_address" "addr" {
  address_id = "my-address-id"
}

SchemaSchema

OptionalOptional

  • address_id (String) ID of the address.
  • folder_id (String) The folder identifier that resource belongs to. If it is not provided, the default provider folder-id is used.
  • name (String) The resource name.

Read-OnlyRead-Only

  • created_at (String) The creation timestamp of the resource.
  • deletion_protection (Boolean) The true value means that resource is protected from accidental deletion.
  • description (String) The resource description.
  • dns_record (List of Object) (see below for nested schema)
  • external_ipv4_address (List of Object) (see below for nested schema)
  • id (String) The ID of this resource.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • reserved (Boolean) false means that address is ephemeral.
  • used (Boolean) true if address is used.

Nested Schema for Nested Schema for dns_record

Read-Only:

  • dns_zone_id (String) DNS zone id to create record at.

  • fqdn (String) FQDN for record to address.

  • ptr (Boolean) If PTR record is needed.

  • ttl (Number) TTL of DNS record.

Nested Schema for Nested Schema for external_ipv4_address

Read-Only:

  • address (String) Allocated IP address.

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

Was the article helpful?

Previous
sws_waf_profile
Next
vpc_gateway
© 2025 Direct Cursus Technology L.L.C.