terraform-azurerm-caf-enterprise-scale
terraform-azurerm-caf-enterprise-scale copied to clipboard
feature request: Azure Firewall Configuration does not support Specific Public IP addresses or multiple Public IP addresses
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Versions
terraform:
all
azure provider:
all
module:
all
Description
Describe the bug
The terraform configuration bloc for Azure Firewall does not support specification of multiple public IP addresses or of a single static public IP address:
- variables.tf:
azure_firewall = object({
enabled = bool
config = object({
address_prefix = string
enable_dns_proxy = bool
dns_servers = list(string)
sku_tier = string
base_policy_id = string
private_ip_ranges = list(string)
threat_intelligence_mode = string
threat_intelligence_allowlist = list(string)
availability_zones = object({
zone_1 = bool
zone_2 = bool
zone_3 = bool
})
})
})
Steps to Reproduce
- Edit the variables.tf in the root module
- Attempt to specify a static Public IP address or multiple static public IP addresses
Screenshots
azure_firewall = object({
enabled = bool
config = object({
address_prefix = string
enable_dns_proxy = bool
dns_servers = list(string)
sku_tier = string
base_policy_id = string
private_ip_ranges = list(string)
threat_intelligence_mode = string
threat_intelligence_allowlist = list(string)
availability_zones = object({
zone_1 = bool
zone_2 = bool
zone_3 = bool
})
})
})
Additional context
Lack of support for easily specifying multiple Public IP addresses (static or dynamic) in the configuration means the user is unable to make use of key features of the Azure Firewall.:
- DNAT is handicapped to only the default PIP.
- Compliance policies which mandate the use of separate public IP addresses for different services even through the same firewall are difficult or expensive to meet - even though AFW supports these capabilities.