cruizba 43c66b0708 openvidu-deployment: AWS HA: TURN over UDP for private Media Nodes, and signal the stack only when healthy ... TURN over UDP for Media Nodes in private subnets. With TurnDomainName, TurnCertificateARN and LoadBalancerSubnets set, and the Media Nodes in other subnets than the Load Balancers, a second internet-facing Network Load Balancer forwards UDP 443 to the TURN server of the Media Nodes, with cross-zone load balancing. It is only used when the SubnetProcessor detects private Media Nodes. An NLB cannot have a UDP and a TLS listener on the same port, so TURN over TLS stays on the TURN Load Balancer as the fallback. LiveKit gives clients the UDP TURN address as turn:<node IP>:443, so each Media Node announces the IP of the NLB in its availability zone (--public-ip, and --force-media-node-public-ip on the Master Nodes) instead of the NAT gateway IP. The NLB keeps the static IPs that AWS assigns to it, so no Elastic IPs of the account are used: each Media Node resolves the zonal DNS name of the NLB. New TurnUDPLoadBalancerDNS output. Master Nodes signal their WaitCondition only once OpenVidu is installed, started and healthy, and signal a failure on any error. Before, they signalled right after generating the shared secret, so a failed installation still ended in CREATE_COMPLETE. The WaitCondition timeout goes from PT20M to PT40M. Assisted-by: claude-code - Anthropic - Claude Opus 5.5		2026-10-16 19:18:46 +02:00
..
cf-openvidu-ha.yaml	openvidu-deployment: AWS HA: TURN over UDP for private Media Nodes, and signal the stack only when healthy	2026-10-16 19:18:46 +02:00