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

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for log_settings
  • Nested Schema for compute_instance
  • Nested Schema for compute_instance.boot_disk
  • Nested Schema for compute_instance.boot_disk.initialize_params
  • Nested Schema for compute_instance.network_interface
  • Nested Schema for compute_instance.resources
  1. Terraform reference
  2. Resources
  3. Load Testing
  4. Data Sources
  5. loadtesting_agent

yandex_loadtesting_agent (Data Source)

Written by
Yandex Cloud
Updated at August 7, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for log_settings
    • Nested Schema for compute_instance
    • Nested Schema for compute_instance.boot_disk
    • Nested Schema for compute_instance.boot_disk.initialize_params
    • Nested Schema for compute_instance.network_interface
    • Nested Schema for compute_instance.resources

Get information about a Yandex Load Testing Agent.

Example usageExample usage

//
// Get information about existing LoadTesting Agent.
//
data "yandex_loadtesting_agent" "my_agent" {
  agent_id = "some_agent_id"
}

output "instance_external_ip" {
  value = data.yandex_loadtesting_agent.my_agent.compute_instance.0.network_interface.0.nat_ip_address
}

SchemaSchema

RequiredRequired

  • agent_id (String) The ID of a specific load testing agent.

OptionalOptional

  • log_settings (Block List, Max: 1) (see below for nested schema)

Read-OnlyRead-Only

  • compute_instance (List of Object) (see below for nested schema)
  • compute_instance_id (String) Compute Instance ID.
  • description (String) The resource description.
  • 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.
  • name (String) The resource name.

Nested Schema for Nested Schema for log_settings

Optional:

  • log_group_id (String) The ID of cloud logging group to which the load testing agent sends logs.

Nested Schema for Nested Schema for compute_instance

Read-Only:

  • boot_disk (Block List, Min: 1, Max: 1) Boot disk specifications for the instance. (see below for nested schema)

  • computed_labels (Map of String) The set of labels key:value pairs assigned to this instance. This includes user custom labels and predefined items created by Yandex Cloud Load Testing.

  • computed_metadata (Map of String) The set of metadata key:value pairs assigned to this instance. This includes user custom metadata, and predefined items created by Yandex Cloud Load Testing.

  • labels (Map of String) A set of key/value label pairs to assign to the instance.

  • metadata (Map of String) A set of metadata key/value pairs to make available from within the instance.

  • network_interface (Block List, Min: 1) Network specifications for the instance. This can be used multiple times for adding multiple interfaces. (see below for nested schema)

  • platform_id (String) The Compute platform for virtual machine.

  • resources (Block List, Min: 1, Max: 1) Compute resource specifications for the instance. (see below for nested schema)

  • service_account_id (String) The ID of the service account authorized for this load testing agent. Service account should have loadtesting.generatorClient or loadtesting.externalAgent role in the folder.

  • zone_id (String) The availability zone where resource is located. If it is not provided, the default provider zone will be used.

Nested Schema for Nested Schema for compute_instance.boot_disk

Read-Only:

  • auto_delete (Boolean) Whether the disk is auto-deleted when the instance is deleted. The default value is true.

  • device_name (String) This value can be used to reference the device under /dev/disk/by-id/.

  • disk_id (String) The ID of created disk.

  • initialize_params (Block List, Min: 1, Max: 1) Parameters for creating a disk alongside the instance. (see below for nested schema)

Nested Schema for Nested Schema for compute_instance.boot_disk.initialize_params

Read-Only:

  • block_size (Number) Block size of the disk, specified in bytes.

  • description (String) A description of the boot disk.

  • name (String) A name of the boot disk.

  • size (Number) The size of the disk in GB. Defaults to 15 GB.

  • type (String) The disk type.

Nested Schema for Nested Schema for compute_instance.network_interface

Read-Only:

  • index (Number)

  • ip_address (String) Manual set static IP address.

  • ipv4 (Boolean) Flag for allocating IPv4 address for the network interface.

  • ipv6 (Boolean) Flag for allocating IPv6 address for the network interface.

  • ipv6_address (String) Manual set static IPv6 address.

  • mac_address (String)

  • nat (Boolean) Flag for using NAT.

  • nat_ip_address (String) A public address that can be used to access the internet over NAT.

  • nat_ip_version (String)

  • security_group_ids (Set of String) Security group ids for network interface.

  • subnet_id (String) The ID of the subnet to attach this interface to. The subnet must reside in the same zone where this instance was created.

Nested Schema for Nested Schema for compute_instance.resources

Read-Only:

  • core_fraction (Number) If provided, specifies baseline core performance as a percent.

  • cores (Number) The number of CPU cores for the instance. Defaults to 2 cores.

  • memory (Number) The memory size in GB. Defaults to 2 GB.

Was the article helpful?

Previous
kms_symmetric_key_iam_member
Next
loadtesting_agent
© 2025 Direct Cursus Technology L.L.C.