---
title: "exoscale_nlb (Data Source)"
description: "Fetch Exoscale Network Load Balancers (NLB) https://community.exoscale.com/product/networking/nlb/ data.\nCorresponding resource: exoscale_nlb ../resources/nlb.md."
url: https://community.exoscale.com/reference/terraform/provider/data-sources/nlb/
section: reference
last_updated: 2026-10-02
---
> For AI agents: the documentation index is at https://community.exoscale.com/llms.txt. Every page is available as markdown at `<page URL>index.md` or with `Accept: text/markdown`.

# exoscale_nlb (Data Source)

Fetch Exoscale [Network Load Balancers (NLB)](https://community.exoscale.com/product/networking/nlb/index.md) data.

Corresponding resource: [exoscale_nlb](https://community.exoscale.com/reference/terraform/provider/resources/nlb/index.md).

## Example Usage

```terraform
data "exoscale_nlb" "my_nlb" {
  zone = "ch-gva-2"
  name = "my-nlb"
}

output "my_nlb_id" {
  value = data.exoscale_nlb.my_nlb.id
}
```

Please refer to the [examples](https://github.com/exoscale/terraform-provider-exoscale/tree/master/examples/)
directory for complete configuration examples.


## Schema

### Required

- `zone` (String) The Exoscale [Zone](https://www.exoscale.com/datacenters/) name.

### Optional

- `id` (String) The Network Load Balancers (NLB) ID to match (conflicts with `name`).
- `name` (String) The NLB name to match (conflicts with `id`).
- `timeouts` (Block, Optional) (see [below for nested schema](#nestedblock--timeouts))

### Read-Only

- `address_family` (String) The NLB address family (`inet4` or `inet6`).
- `created_at` (String) The NLB creation date.
- `description` (String) The Network Load Balancers (NLB) description.
- `ip_address` (String) The NLB public IP address (IPv4 or IPv6, depending on `address_family`).
- `labels` (Map of String) A map of key/value labels.
- `state` (String) The current NLB state.

<a id="nestedblock--timeouts"></a>
### Nested Schema for `timeouts`

Optional:

- `read` (String) A string that can be [parsed as a duration](https://pkg.go.dev/time#ParseDuration) consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.