With the Department of Defense’s awarding of the JEDI contract fast approaching, now is the time for DOD agencies to plan for their transition to the JEDI cloud. Given that it takes an average of 18 months to execute a cloud migration, there’s the added pressure of already being behind schedule (should everything go according to plan, the go-live date is November 1). Migrating to the cloud is an intimidating prospect, with a fair bit of uncertainty:
"Where is the data going to live?"
"How are we going to move it?"
"How will we manage that infrastructure?"
"Will the Force be with us?"
Whether you’re in the public or private sector, BlueCat has a time-tested process to ensure that migration of your DNS infrastructure to the cloud is as smooth as possible. At a basic level, that means extending the functionality and reach of on-prem DNS into the cloud – it’s just that easy...and that complicated.
Sort out your (computing) resources
Before changing up how your agency’s DNS operates, you’ll need to determine the current state of play. Are you running an organized system on all new equipment with routinely updated software, or was your DNS infrastructure put in place while The Phantom Menace was in theatres? Overall, there is a high likelihood that your initial project scope will grow significantly as the true extent of the cloud deployment comes into focus. Ultimately, flexibility is key.
Put together an action plan
Once you have a general idea of what you’re working with, you can determine where your post-migration DNS will reside. This in turn will enable planning for budgets, scheduling, and team responsibilities.
As mentioned earlier, it’s important to be flexible as the cost profile is bound to fluctuate. Your team may end up with more responsibilities once the cloud migration enables new functionality, so it’s wise to plan for additional scale. When anything begins moving to the cloud, it’s imperative that you have visibility and control over what is taking place, or you could be opening up vulnerabilities which lead to a security breach.
Make sure that plan starts with a unified DNS
If you’re thinking “Woah, we were just talking about making plans!” then this next portion is essential. To help with pinpointing exactly where to start, figuring out how to get your DNS functionality centralized might be the best place. If you don’t have centralized management and visibility of your DNS, then anything can happen. The possibility of trouble grows exponentially when physical limits are off the table. Essentially, what you want to avoid before you extend out into the cloud is the “autonomous black hole of compute” – a place that nobody can see into, and nobody can get to. You certainly don’t want all of your time and resources to end up there.
Do. Or do not. There is no try.
Once the JEDI cloud is operational, the clock will start ticking. DOD agencies will be mandated to conduct business over the cloud – whether they’re ready or not. There’s no reason to struggle or go it alone, and there’s even less reason to wait. BlueCat’s Enterprise DNS is a COTS solution that will ensure that you have visibility, control and detection to ensure that your network infrastructure is cloud-ready.