How to Import an Azure Cache for Redis Enterprise Cluster into Terraform

Import Azure Cache for Redis Enterprise Cluster with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure Cache for Redis (Enterprise) resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure Cache for Redis Enterprise Cluster to managed Terraform.

terraback scan all azure --subscription-id YOUR_ID

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_redis_enterprise_cluster.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Cache/redisEnterprise/prod-redis-ent"
}

Example azurerm_redis_enterprise_cluster configuration

Here is a realistic Azure Cache for Redis Enterprise Cluster block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "azurerm_redis_enterprise_cluster" "main" {
  name                = "prod-redis-ent"
  resource_group_name = "prod-rg"
  location            = "eastus"
  sku_name            = "Enterprise_E10-2"
}

Gotchas when importing a Azure Cache for Redis Enterprise Cluster

• The Enterprise tier uses the ARM type Microsoft.Cache/redisEnterprise, which is different from the basic/standard/premium tiers (Microsoft.Cache/Redis); do not confuse them at import time.
• sku_name bundles the SKU family and capacity in one string, for example Enterprise_E10-2; it is not the same shape as the basic-tier sku_name/capacity split.
• The database lives in a separate azurerm_redis_enterprise_database child resource (usually named 'default') and is not imported with the cluster.
• zones, if set, is fixed at creation; the Enterprise tier is a premium offering, so verify cost before provisioning new clusters.

Doing it manually with terraform import

The native approach is to write the azurerm_redis_enterprise_cluster block by hand, then run terraform import azurerm_redis_enterprise_cluster.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 other Azure resources