AWS / Azure / GCP

The Loadbalancer.org appliance automatically detects changes in your auto-scaling groups, with zero configuration and zero downtime...

In the Azure Management Portal, select the Virtual Machines option, click on the newly deployed Load Balancer VM, click on Network interfaces and then select the network interface attached to the load balancer, then click IP configurations and ensure that IP forwarding is Enabled...

The WAF addresses the OWASP Top 10 vulnerabilities and is very quick and simple to deploy...

LVS-DR and LVS-TUN are both forms of Direct Server Return where the load balancer only has to deal with one half of the connection...

We're proud to announce that we have achieved Advanced Technology Partner status with Amazon Web Services (AWS), the leading platform for public cloud infrastructure-as-a-service...

SSL offload is handled by STunnel, while HAProxy handles back-end server re-encryption...

For several years, if an instance was launched in AWS and during the initial configuration an IAM role was not defined, the only option available was to stop/terminate the instance and launch another, however, this has now changed!..

HAProxy is an excellent choice if you need layer 7 functionality, but its a full reverse-proxy, so the application thinks that all of the traffic is coming from HAProxys IP - rather than the clients...

The Loadbalancer.org for AWS appliance will monitor auto scaling groups, update configs based on auto scaling events and add/remove servers...

Using the flexibility of both AWS and our Enterprise AWS appliance, it's possible to configure a secure and robust load balanced Remote Desktop Services deployment to suit a range of requirements...

Anyone who has been watching Loadbalancer.org over the last few years will have noticed the things that we don't like :-). We've made it pretty clear that we don't like load balancing firewalls and we've also been pretty reluctant to turn our load balancers into a GSLB...

One of our favorite methods of load balancing is using Layer 4 DR because it is transparent and fast. Unfortunately, because of Amazon's infrastructure, this is not possible in EC2 so we need to use another method which means we are left with layer 4 NAT and transparent HAproxy using TProxy...

I get quite frustrated with benchmarks because they are very hard to perform properly, and even when you do them properly its very hard to get any useful data from them...

I’m excited and slightly scared by our latest product! Excited because I've become slightly addicted to launching multiple instances in different parts of the world and load balancing the traffic seamlessly. Scared because this could change our whole business model...