> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/tools-terraform/docs/list-resources/datacenter.md).

# List Resource: ionoscloud\_datacenter

Lists IONOS CLOUD Virtual Data Centers.

⚠️ **Note:** List Resources require HashiCorp Terraform version 1.14 or later and are queried using `terraform query`.

Lists Virtual [Data Centers](https://docs.ionos.com/cloud/set-up-ionos-cloud/get-started/configure-data-center) on IONOS CLOUD.

## Example Usage

⚠️ **Note:** `list` blocks must be placed in a dedicated query file, whose name ends in `.tfquery.hcl` (for example `queries.tfquery.hcl`), separate from your main Terraform configuration.

### List all datacenters

```hcl
list "ionoscloud_datacenter" "all" {
  provider         = ionoscloud
  include_resource = true
}
```

### Filter datacenters by location

```hcl
list "ionoscloud_datacenter" "de_txl" {
  provider         = ionoscloud
  include_resource = true
  config {
    filters = [{
      field_name  = "location"
      field_value = "de/txl"
    }]
  }
}
```

### Filter datacenters by name and location

```hcl
list "ionoscloud_datacenter" "prod" {
  provider         = ionoscloud
  include_resource = true
  config {
    filters = [
      { field_name = "name",     field_value = "production" },
      { field_name = "location", field_value = "de/txl" },
    ]
  }
}
```

### Generate resource configuration from existing datacenters

Use `terraform query` with `-generate-config-out` to produce ready-to-use `ionoscloud_datacenter` resource blocks for the datacenters the query returns:

```shell
terraform query -generate-config-out=imported.tf
```

Terraform will write an `ionoscloud_datacenter` resource block for each discovered datacenter into `imported.tf`, which can then be used directly in your configuration.

> **Note:** The datacenters are read with a single Cloud API request, so the results are bounded by the API's default page limit. A contract holding more datacenters than that limit is truncated silently — no error is raised and the missing datacenters simply do not appear. Check that the number of generated resource blocks matches the number of datacenters you expect before treating `imported.tf` as complete.

Terraform names each generated resource after the `list` block label plus an index — a `list "ionoscloud_datacenter" "smoke"` block produces `ionoscloud_datacenter.smoke_0`, `smoke_1`, and so on.

### ⚠️ Do not reuse a `list` block label across separate imports

Because the generated names are derived from the `list` block label, running a second query with the **same** label produces the **same** resource addresses. If a previous address is still in state, the generated configuration is silently applied to the datacenter already recorded at that address — not to the one you just queried.

This happens because an `import` block is idempotent: Terraform skips it when the target address is already in state, so the identity in the generated `import` block is never consulted. Deleting the generated `.tf` file does **not** remove the state entry.

The consequences are not limited to a harmless diff. `location` is a force-new attribute, so if the two datacenters are in different locations, the plan **destroys the datacenter already in state** and creates a replacement — the datacenter you meant to import is never touched:

```hcl
# generated for a datacenter in de/fra, but smoke_0 in state points at one in de/txl
resource "ionoscloud_datacenter" "smoke_0" {
  location = "de/fra"          # forces replacement of the de/txl datacenter
  name     = "docker-machine-data-center"
}
```

To avoid this:

* Use a distinct `list` block label for each query you intend to import from, or
* Remove the stale address before regenerating: `terraform state rm ionoscloud_datacenter.smoke_0`

Always read the plan before applying. A clean import reports:

```
Plan: 1 to import, 0 to add, 0 to change, 0 to destroy.
```

Anything reporting changes, and especially `must be replaced` with `location = "..." -> "..." # forces replacement`, means the address is bound to a different datacenter — stop and clear the state entry first.

## Argument Reference

The `config` block supports the following arguments:

* `filters` - (Optional) List of filters to apply. All filters must match (AND logic). Each filter supports:
  * `field_name` - (Required) The field to filter on. Supported values: `name`, `location`.
  * `field_value` - (Required) The exact value to match against.

> **Note:** The Cloud API returns datacenters from every location in a single response, so filtering by `location` does not reduce the number of API calls; it only narrows the results. Filtering happens after that response is read, so it cannot recover a datacenter left out by the page limit described above.

## Identity Attributes

Each result exposes the following identity attributes, usable for import:

| Attribute  | Description                                                                                                               |
| ---------- | ------------------------------------------------------------------------------------------------------------------------- |
| `id`       | The UUID of the datacenter.                                                                                               |
| `location` | The location the datacenter lives in (e.g. `de/txl`). Only needed when the Cloud API endpoint is overridden per location. |

## Attributes Reference

Each result exposes the following attributes when `include_resource = true`, matching the `ionoscloud_datacenter` resource schema:

* `id` - The UUID of the datacenter.
* `name` - The name of the datacenter.
* `description` - A description for the datacenter.
* `location` - The physical location of the datacenter (e.g. `de/txl`).
* `version` - The version of the datacenter, incremented with every change.
* `features` - List of features supported by the location the datacenter is in.
* `sec_auth_protection` - Whether a two-factor protection is enabled for the datacenter.
* `cpu_architecture` - Array of features and CPU families available in the location:
  * `cpu_family` - A valid CPU family name (e.g. `INTEL_SKYLAKE`).
  * `max_cores` - The maximum number of cores available.
  * `max_ram` - The maximum RAM size in MB.
  * `vendor` - A valid CPU vendor name.
  * `enabled_features` - Features enabled for this CPU architecture, e.g. `SEV-SNP` for Confidential Computing.
* `ipv6_cidr_block` - The auto-assigned /56 IPv6 CIDR block, if IPv6 is enabled for the datacenter.
* `timeouts` - Always null; timeouts are configuration-only and are not returned by a query.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ionos.com/cloud/tools-terraform/docs/list-resources/datacenter.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.