AzureAzure Event Hubsazurerm_eventhubPro

How to Import an Azure Event Hub into Terraform

To import an existing Azure Event Hub into Terraform, scan it with Terraback and run terraback azure import --method bulk. Terraback writes the matching azurerm_eventhub resource block and the Terraform 1.5+ import block for you, so you do not have to run terraform import by hand. The import ID is the full resource ID nested under the namespace (.../namespaces/<ns>/eventhubs/<name>).

Import Azure Event Hub with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure Event Hubs resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure Event Hub to managed Terraform.

1

Scan your Azure account

terraback scan all azure --subscription-id YOUR_ID
2

Generate import blocks and import into state

terraback azure import --method bulk

The Terraform import block

Terraback emits a Terraform 1.5+ import block like the one below. Because the block lives in your configuration, the import is reviewable in a pull request and repeatable across environments.

import {
  to = azurerm_eventhub.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.EventHub/namespaces/prod-ehns/eventhubs/events"
}

Example azurerm_eventhub configuration

Here is a realistic Azure Event Hub block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "azurerm_eventhub" "main" {
  name                = "events"
  namespace_name      = "prod-ehns"
  resource_group_name = "prod-rg"
  partition_count     = 2
  message_retention   = 1
}

Gotchas when importing a Azure Event Hub

  • The ID nests under its namespace; the path segment is lowercase 'eventhubs'.
  • partition_count is immutable on Standard/Basic tiers; changing it forces a new event hub.
  • Consumer groups and authorization rules are separate azurerm_eventhub_consumer_group and azurerm_eventhub_authorization_rule resources.
  • An Event Hub cannot be created without an existing namespace; import the namespace first.

Doing it manually with terraform import

The native approach is to write the azurerm_eventhub block by hand, then run terraform import azurerm_eventhub.example <import-id> for every resource, one at a time. That works for a handful of resources, but it does not scale: you author all the HCL yourself and repeat the command for each item. Terraback generates the HCL and the import blocks for your whole account in one pass.

Import your whole Azure account in minutes

Terraback scans 80+ Azure resource types and emits clean Terraform plus import blocks, running locally with read-only credentials. $499 once, no SaaS.