azurerm_managed_lustre_file_system cost estimation
A high-performance Lustre file system for HPC/ML, billed per GiB of provisioned capacity by throughput tier. 4 TB at the 250 MB/s/TiB tier is ~$696/month.
An azurerm_managed_lustre_file_system (AMLFS) provides the parallel throughput HPC, ML training, and rendering workloads need from a shared POSIX file system. Cost is provisioned capacity per GiB-month, with the per-GiB rate set by the throughput tier — capacity and performance are bought together.
The SKU encodes the throughput tier: AMLFS-Durable-Premium-250 is ~$0.17/GiB-month, so 4 TB (4,096 GiB) is ~$696/month. Higher tiers (Premium-500, ~$0.34) double the rate for double the per-TiB throughput; lower tiers (Premium-125 ~$0.10, Premium-40 ~$0.06) trade throughput for cost.
Because you provision capacity (and implicitly throughput) up front and pay for it continuously, the levers are sizing the capacity to the working set and picking the lowest throughput tier that meets the workload's bandwidth need. Over-provisioning either inflates the bill directly.
c3x prices the file system from storage_capacity_in_tb and the SKU's throughput tier, so the provisioned cost is visible before you create a multi-terabyte file system.
Terraform example
A minimal but realistic configuration that C3X can estimate.
resource "azurerm_managed_lustre_file_system" "hpc" {
name = "hpc-lustre"
resource_group_name = azurerm_resource_group.main.name
location = azurerm_resource_group.main.location
sku_name = "AMLFS-Durable-Premium-250"
storage_capacity_in_tb = 4
subnet_id = azurerm_subnet.compute.id
zones = ["1"]
maintenance_window {
day_of_week = "Sunday"
time_of_day_in_utc = "02:00"
}
}Pricing dimensions
What you actually pay for when you provision azurerm_managed_lustre_file_system.
| Dimension | Unit | What's being charged |
|---|---|---|
| Provisioned capacity | per GiB-month | Billed for provisioned capacity at the throughput tier's per-GiB rate. Higher throughput tiers raise the rate; capacity and performance scale together. ~$0.17/GiB-month (Premium-250) → 4 TB ≈ $696.32/month |
Sample C3X output
A 4 TB AMLFS-Durable-Premium-250 file system:
azurerm_managed_lustre_file_system.hpc
└─ Provisioned capacity (Premium-250, 4 TB) 4096 GiB-month $696.32
Monthly $696.32Optimization tips
Common ways to reduce azurerm_managed_lustre_file_system cost without changing the workload.
Pick the lowest throughput tier that meets demand
Roughly halves cost per tier stepped downThe SKU's throughput tier sets the per-GiB rate — Premium-500 is double Premium-250, Premium-125 is ~60% of it. Measure the workload's required bandwidth and choose the cheapest tier that delivers it.
Size capacity to the working set
Proportional to capacity avoidedYou pay for provisioned GiB regardless of fill. Provision the active working set plus headroom rather than the full dataset — link cold data to blob storage and stage only what's hot.
Tear down between campaigns
Full cost during idle periodsHPC/ML file systems are often needed for a training campaign or render, not permanently. AMLFS bills continuously while it exists; deleting it (after exporting to blob) between campaigns stops the charge.
Use blob integration for cold data
Workload-dependentAMLFS integrates with Azure Blob for import/export, so cold input/output data lives in cheap blob storage and only the active working set occupies the expensive Lustre capacity.
FAQ
How is Azure Managed Lustre billed?
Per GiB-month of provisioned capacity, at a rate set by the throughput tier in the SKU. AMLFS-Durable-Premium-250 is ~$0.17/GiB-month, so 4 TB is ~$696/month. Higher throughput tiers cost more per GiB; capacity and performance are provisioned together.
How do I reduce Managed Lustre cost?
Pick the lowest throughput tier that meets the workload's bandwidth, size capacity to the active working set (with blob integration for cold data), and tear the file system down between campaigns since it bills continuously while it exists.
How does c3x estimate the cost?
From storage_capacity_in_tb and the SKU's throughput tier, pricing the provisioned GiB. An over-sized or over-tiered file system shows its monthly cost before deployment.
Related resources
Estimate this resource in your own Terraform
Free, open source, no API key. C3X parses your Terraform and shows line-item cost for every resource, including azurerm_managed_lustre_file_system.