coturn TURN Server That Will Not Relay Into Your Private Network

coturn from EPEL as a TURN server for WebRTC: credentials from a shared secret the role makes, TURN over TLS, and the relay kept out of private and special-purpose ranges, where by default a valid credential reached 10.x and 192.168.x peers. The live test relays to a public peer and is refused for private ones and the metadata address. Original role, live-tested on Rocky Linux 10.

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.

ansibleMulti-cloud & platform-agnosticNetworking & VPCv1.0.0live-tested

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

Same cloud, same category. These are what you would weigh against it without changing provider.

A Squid Forward Proxy That Refuses Loopback And Metadata Consul Single Server, Five Listeners On Loopback FRR BGP With Filters Both Ways And MD5 Sessions Headscale Control Server On Loopback, Proven By A Pre-Auth Key Kea DHCPv4 That Answers Only The Subnets You Name Libreswan IKEv2 With A Pre-Shared Key, IKE On One Address WireGuard With A Kept Key And A Checked Config radvd Router Advertisements, Refused Where The Host Does Not Route

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_coturn" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-coturn/any"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.