azurerm_eventhub_cluster cost estimation

An azurerm_eventhub_cluster provisions a single-tenant, dedicated Event Hubs deployment measured in Capacity Units (CUs). Each CU bills ~$9.38/hour, so a single CU is ~$6,847/month — and clusters often run multiple CUs. This is one of the most expensive standing resources in Azure.

Dedicated clusters exist for very high, sustained throughput (roughly 1 GB/s+ ingress per CU), single-tenant isolation, and predictable performance at scale. For the vast majority of workloads, a Standard or Premium Event Hubs namespace — billed per throughput/processing unit at a tiny fraction of the cost — is the right choice. The dedicated cluster only pays off when you're genuinely saturating the throughput a namespace can provide.

The cost is simply CU count × the hourly rate, billed continuously whether or not events flow. So the decision is binary: do you have the sustained scale to justify dedicated capacity, or should this be a namespace?

c3x prices the cluster from sku_capacity (CU count), so this very high standing cost is visible before deployment — important, given the scale.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "azurerm_eventhub_cluster" "dedicated" {
  name                = "events-dedicated"
  resource_group_name = azurerm_resource_group.main.name
  location            = azurerm_resource_group.main.location
  sku_name            = "Dedicated_1"
}

Pricing dimensions

What you actually pay for when you provision azurerm_eventhub_cluster.

Dimension	Unit	What's being charged
Dedicated capacity units	per CU-hour	sku_capacity (CUs) × the hourly rate, billed continuously regardless of event volume. $9.38/CU-hour → 1 CU ≈ $6,847.40/month

Sample C3X output

A single-CU dedicated cluster, 24/7:

azurerm_eventhub_cluster.dedicated
└─ Dedicated capacity units (1 CU)   730 CU-hours   $6,847.40
                                     Monthly        $6,847.40

Optimization tips

Common ways to reduce azurerm_eventhub_cluster cost without changing the workload.

Use a Standard/Premium namespace unless you truly need dedicated

Thousands/month vs a needless dedicated cluster

A dedicated cluster (~$6,847/CU/month) only pays off at very high sustained throughput (~1 GB/s+ per CU) or for single-tenant isolation. Standard/Premium Event Hubs namespaces bill per throughput unit at a tiny fraction — the right choice for almost all workloads.

Right-size CU count to sustained throughput

~$6,847/month per removed CU

Each CU is ~$6,847/month. Provision CUs to your sustained ingress/egress, not peak-of-peaks — and use the cluster's auto-inflate where applicable rather than over-provisioning.

Reserve capacity for steady clusters

Commitment discount on steady CUs

If a dedicated cluster is genuinely justified and runs continuously, reserved capacity pricing discounts it over pay-as-you-go for a 1-3 year commitment.

FAQ

Why is an Event Hubs dedicated cluster so expensive?

It's single-tenant dedicated capacity billed per Capacity Unit at ~$9.38/hour (~$6,847/month per CU), continuously. It's priced for very high sustained throughput and isolation — for normal workloads a Standard/Premium namespace costs a fraction.

When should I use a dedicated cluster instead of a namespace?

Only at very high, sustained throughput (~1 GB/s+ ingress per CU), when you need single-tenant isolation, or for predictable performance at large scale. Below that, a Standard or Premium Event Hubs namespace is far cheaper and sufficient.

How does c3x estimate the cost?

From sku_capacity (the CU count) × the CU-hour rate. Given the scale, seeing the standing cost before deployment matters — each CU is nearly $7,000/month.

Related resources

Azure

azurerm_eventhub_namespace

Standard/Premium namespace — far cheaper for normal throughput

`azurerm_eventhub_cluster` cost estimation