A plug for our (Cloudflare's) product — we support managed load balancing for UDP as well.
- https://blog.cloudflare.com/spectrum-for-udp-ddos-protection...
- https://blog.cloudflare.com/introducing-spectrum-with-load-b...
New AWS UDP Load Balancing for Network Load Balancer
31–35 of 35 posts
Re: New AWS UDP Load Balancing for Network Load Balancer
#32A plug for our (Cloudflare's) product — we support managed load balancing for UDP as well. - https://blog.cloudflare.com/spectrum-for-udp-ddos-protection... - https://blog.cloudflare.com/introducing-spectrum-with-load-b...
Looks cool but if the product is only available for "Enterprise" customers and the pricing is "Request Quote" that means it's expensive. At least the AWS pricing is published.
Re: New AWS UDP Load Balancing for Network Load Balancer
#33With that out of the way ... hope they can add IPv6 support next!
Re: New AWS UDP Load Balancing for Network Load Balancer
#34Can be nice for games, QUIC and DNSCrypt.
Re: New AWS UDP Load Balancing for Network Load Balancer
#35Earlier quoted context omitted.
Lots of people use IPVS but the more efficient modes don't work on AWS. Generally why most that need a LOT of traffic use a cloud provider for regular servers and their own servers in CoLo for heavy stuff. With how Amazon likes to use OSS in their services I'm pretty sure their UDP load balancer are in fact just using IPVS
Interesting, thanks. Hadn't considered this option before, and will do some more exploring, though I note on the IPVS page they say: "For scheduling UDP datagrams, IPVS load balancer records UDP datagram scheduling with configurable timeout, and the default UDP timeout is 300 seconds. Before UDP connection timeouts, all UDP datagrams from the same socket (protocol, ip address and port) will be directed to the same se…
I may be wrong, but I think you can tell IPVS to schedule using tuple hash only using Direct Return mode, which means no stored state for connection tracking.
Edit: doesn't appear to be true, but it uses it's own "lightweight" connection tracking table so you can unload conntrack modules from kernel.
Realistically IPVS can probably route 40 gigabit of traffic per instance. Combine that with DNS round robin and maybe even multi-homing at the front and you could handle basically anything