It wasn’t that long ago when IT team leaders were looking at hybrid- and multi-cloud solutions as the answer to their disaster recovery prayers. DR, after all, was the number one driving force behind these organizations’ cloud migration. As much as enterprises saw the value in shifting their mission-critical applications into the cloud, putting all their eggs in that one basket left them helpless in the event a DDoS attack or a provider slowdown flooded out their link to that cloud.
Hybrid and multi-cloud was supposed to be the way out of the conundrum: diversifying your cloud portfolio meant you had different backups of the same assets and services, allowing you to draw from one cloud if another was currently suffering downtime. But, there was a problem.
Hub and spoke: exposing the weak link in the chain
The current multi-cloud model has a key vulnerability all its own: shifting workloads from one cloud to another means that you need to shift the workload down from the cloud to the enterprise, then back up to the next cloud. In other words, the multi-cloud DR model only works as a backup if you’re still maintaining constant access between your various clouds and your own organization.
This “hub and spoke” model exposes these connections, often delivered over the public internet, as another key vulnerability in the enterprise-to-cloud DR model. All it takes is a DDoS attack flooding out your connection to ensure that workloads you may need to shift from AWS to Google Cloud, or from Azure to a private cloud, aren’t moving anywhere.
That’s no disaster recovery strategy. Just the opposite: that’s exactly the kind of disaster that your DR strategy should be helping you to avoid in the first place.
Cutting out the middleman with CloudNexus
There are two ways around this problem: building end-to-end connections between clouds to avoid needing to shift workloads through the enterprise, and using direct connections to bypass the unreliable and unsecure nature of the public internet.
CloudNexus does both.
With CloudNexus, Console Connect users can establish true cloud-to-cloud connectivity between their platforms of choice – from private clouds to public ones like AWS – so that they can shift workloads as their DR response requires, all without having to move it through the enterprise in the process. And, because this connectivity is delivered via private and reliable direct connections that live outside of the public internet, these cloud pipelines can’t be flooded out by DDoS attacks.
Say goodbye to the days of disaster recovery via hub and spoke. CloudNexus delivers a cloud-to-cloud DR model that can stand up to DDoS disasters in the way that traditional multi-cloud setups can’t.
You May Also Like: