AzureAzure Cache for Redisazurerm_redis_firewall_rulePro

How to Import an Azure Redis Firewall Rule into Terraform

To import an existing Azure Redis Firewall Rule into Terraform, scan it with Terraback and run terraback azure import --method bulk. Terraback writes the matching azurerm_redis_firewall_rule 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 cache (.../Microsoft.Cache/Redis/<cache>/firewallRules/<name>).

Import Azure Redis Firewall Rule with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Azure Cache for Redis resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live Azure Redis Firewall Rule 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_redis_firewall_rule.main
  id = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/prod-rg/providers/Microsoft.Cache/Redis/prod-redis/firewallRules/office"
}

Example azurerm_redis_firewall_rule configuration

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

resource "azurerm_redis_firewall_rule" "main" {
  name                = "office"
  redis_cache_name    = "prod-redis"
  resource_group_name = "prod-rg"
  start_ip            = "203.0.113.0"
  end_ip              = "203.0.113.255"
}

Gotchas when importing a Azure Redis Firewall Rule

  • The rule is a child of a basic/standard/premium cache: its ARM ID nests under Microsoft.Cache/Redis/<cache>/firewallRules/<name>; the type segment 'Redis' is capitalized.
  • name must be alphanumeric (no hyphens or underscores); Azure rejects other characters in firewall rule names.
  • start_ip and end_ip define an inclusive range; for a single address set both to the same IP.
  • Firewall rules apply to the basic/standard/premium tiers; the Enterprise tier uses VNet/private-link controls instead, not this resource.

Doing it manually with terraform import

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