The Edge Firewall on a Public IP, Enabled, Ending in a Deny
Every OVH public IP has an edge firewall that is disabled until enabled, so rules written to it filter nothing; twenty ordered rules where the first match wins and a list without a deny permits what it does not mention; and SSH from anywhere is the first rule offered. Enabled, your permits in sequence with a deny last, SSH from anywhere refused unless accepted.
This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.
Provider drift
This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.
What depends on this
No reference architecture names this module, so changing it affects only configurations that reference it directly.
Nearest alternatives
Nothing else in the catalogue covers security & identity on OVHcloud. If this module is not the right shape, the closest options are on other clouds.
The same job on other clouds
Cloud Firewall on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.
Installing it
module "ovh_ip_firewall" {
source = "www.iac-bazaar.com/iac-bazaar/ovh-ip-firewall/ovh"
version = "1.0.0"
}A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.