Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regional Azure Firewall Policies #750

Closed
2 tasks done
DavidLHannah opened this issue Mar 28, 2024 · 1 comment · Fixed by #805
Closed
2 tasks done

Regional Azure Firewall Policies #750

DavidLHannah opened this issue Mar 28, 2024 · 1 comment · Fixed by #805
Assignees
Labels
Area: Networking 🌐 Issues / PR's related to Networking Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities Type: Enhancement ✨ New feature or request

Comments

@DavidLHannah
Copy link
Contributor

DavidLHannah commented Mar 28, 2024

Describe the feature end to end, including deployment scenario details under which the feature would occur.

When using the vwanConnectivity module to deploy multiple regional Virtual Hubs with Azure Firewall, only a single Azure Firewall Policy is deployed. This single policy is applied to all of the vHubs that are deployed. This means the firewall configurations will be the same in all regions.

In order to account for potential regional-specific configurations, support for multiple Azure Firewall Policies may be required.

Why is this feature important. Describe why this would be important for your organization and others. Would this impact similar orgs in the same way?

If we are properly designing for regional failover of resources with Private Endpoints, then we will also implement regional Azure Private DNS Resolvers. Refer here for further details: https://github.com/adstuart/azure-privatelink-multiregion

Considering this, the need will arise for providing unique DNS Proxy configurations on the Azure Firewall in each region where a Azure Private DNS Resolver is deployed.

Potentially related to #375 & #387

Feature Implementation

An Azure Firewall Policy resource should be created and applied to each Azure Firewall that is deployed in a region.

The parAzFirewallDnsServers parameter could be moved to part of the parVirtualWanHubs parameter, such that each hub may be associated with specific regional DNS resolvers.

Potentially deploy additional firewall policy that could act as the Parent Policy to all other policies deployed in the vWAN.

Check previous GitHub issues

  • I have searched the issues for this item and found no duplicate

Code of Conduct

  • I agree to follow this project's Code of Conduct
@oZakari oZakari added Area: Networking 🌐 Issues / PR's related to Networking long-term labels Mar 28, 2024
@oZakari
Copy link
Contributor

oZakari commented Mar 28, 2024

Hi @DavidLHannah, this a good call out! As you noted, this would be related to the multi-region issues you referenced. Although, multi-region is on our all-up ALZ backlog this is something that is still in the early phases of investigation.

Will add this to the ALZ-Backlog as a long-term goal.

@oZakari oZakari moved this from Backlog to In Progress in Azure Landing Zones - Bicep - Public Roadmap May 15, 2024
@oZakari oZakari added Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities Type: Enhancement ✨ New feature or request and removed long-term labels Jul 9, 2024
@oZakari oZakari moved this from In Progress to Done in Azure Landing Zones - Bicep - Public Roadmap Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Networking 🌐 Issues / PR's related to Networking Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities Type: Enhancement ✨ New feature or request
Development

Successfully merging a pull request may close this issue.

3 participants