Load Balancing and Failover Between AWS Regions

Load Balancing and Failover Between AWS Regions

Yes! It really is possible to distribute traffic between regions on AWS EC2. But only with Total Uptime’s Cloud Load Balancer.

We frequently receive inquiries from organizations who use Amazon EC2 for compute, but want a more robust load balancer that can distribute or fail over traffic between different regions, not just availability zones.  Amazon has their own Elastic Load Balancer, but it only works to distribute traffic within a region. And while it supports load balancing between availability zones within the same region, it does not allow you to distribute traffic to another region, unless you want to use DNS, which is less than ideal. Furthermore, it is also limited in the type of traffic that it can load balance, and is primarily designed for web applications.

Total Uptime is the best load balancer for AWS (and everyone else)

Not only does Total Uptime offer the ability to distribute traffic between AWS regions, we also give you the ability to load balance and fail over from any data center or cloud provider to any other provider! Because we’re vendor independent, you could have primary compute at Amazon (even in multiple regions), secondary compute at another provider and even tertiary compute and beyond giving you true multi-geography, multi-vendor redundancy like no other provider on the planet. No longer do you have to keep all of your eggs in one basket.

There is no question that Amazon web services is a very innovative organization offering an array of competitive solutions. In fact, most everyone agrees that Amazon kick started the entire cloud computing trend. But even if AWS eventually offers multi-region load balancing, the question still remains: Is AWS really the best choice for this critical role? Suppose you do deploy infrastructure at another provider and use an Elastic Load Balancer to distribute traffic there, but AWS goes down. Will the Elastic load balancer still deliver traffic to your non-AWS locations during the outage?

True data center, cloud provider independence

Total Uptime believes that vendor neutrality is a critical component of any IT strategy. We do not offer compute of any kind, ensuring we have no vested interest in any provider. Plus, the cloud IP addresses we provide you for making your applications accessible on the Internet are also data center independent, allowing you to route traffic anywhere you want, to any vendor you want without ever having to change an IP address again, regardless of where you move your compute.

At Total Uptime we do one thing – availability – and we do it well! Our solutions help our customers deploy applications across multiple vendors, ensuring redundancy, resiliency and availability. We take the same to heart in how we design and deploy our networks. We use multiple vendors for transit providers, unrelated globally distributed data centers and infrastructure, all ensuring no single point of failure. Click here to learn more about our global cloud platform. Or why not try our Cloud Load Balancer today for free!

Ready to take control over your network and increase uptime?
Access to our platform starts at just $23/month. Continue learning about Cloud Load Balancing or jump right in and try it free now.


Other posts you might like...

Downtime costs $7900 per minute, on average

The cost of datacenter downtime has increased more than 40% for many companies over the last 3 years, according to a recent study by Ponemon Institute, sponsored by Emerson Network Power. The report analyzes 67 datacenters...

read more

What are the key differences between DNS Failover and Cloud Failover so I can better understand which one is right for my application?

Both solutions require that you tell us what the IP address(es) are for your ‘real servers’. That way we know how to alter DNS or route traffic...

read more

Apple Suffers $32 Million Dollar DNS Outage

Yes, even the biggest and best organizations can suffer tremendous losses due to something as simple as a DNS issue. Unless you are immersed in DNS and it is one of your core competencies, it is easy to make a mistake, and that may be what transpired at Apple.

read more