DISA sees progress in migrating to milCloud replacement


Written by Marc Pomerleau

The Defense Information Systems Agency has migrated 60 of 120 accounts from its old milCloud cloud infrastructure to the new model it replaces it with.

In December, DISA announced it would be ending milCloud 2.0, moving to what it now calls Stratus, which offers a multi-tenant private cloud to meet the unique needs of mission partners.

Since then, 60 mission partner accounts have migrated to the new platform, said Courtnea Johnson, head of DISA’s Cloud Infrastructure branch, during a virtual event hosted by NextGov. She added that DISA migrated over 1,700 terabytes of data and over 820 virtual machines.

“We did this in six months, which is a huge success. Normally when you look at the migration history, sometimes it takes longer – it takes eight to 12 months to migrate all the data and all the VMs to a new platform,” Johnson said. “We are very proud of the success here and couldn’t have done it without our mission partners. We partner with them, they trust us, and we work directly with them to make that happen.

Other milCloud accounts and users have moved to the commercial cloud, closed accounts altogether, or switched to Amazon Web Services, she said.

For some, the move to the commercial cloud made sense because they used milCloud as a springboard to learn more about cloud environments, Johnson said, especially since the milCloud 2.0 contract vehicle allowed mission partners to purchase credits. AWS cloud.

Ultimately, DISA wants to be an honest broker and help mission partners with the cloud, she said, wherever that cloud journey takes partners.

“We are truly an honest broker. When we meet with mission partners to partner with them to better understand their needs, sometimes Stratus may not be the answer for them,” Johnson said. “Sometimes they may be ready to go into the commercial world and not into a private cloud because we’re looking at complex requirements for mission partners and we’re looking to help mission partners get them where they need to be, c ie in the cloud — and it’s a commercial cloud or a private cloud.

Regarding next steps for Stratus, Johnson said DISA is looking to expand the classified network, known as SIPRNet. While Stratus offers SIPRNet, DISA would like to contact mission partners to see if they are interested in migrating applications from their current SIPRNet environment to Stratus.

They are also working on automation to make Stratus a “true self-service cloud”.

“We want to be able to automate everything we do to enable mission partners to accelerate the move to the cloud,” she said.

DISA also wants a utility-based model so mission partners can pay as they go to get the most out of the benefits of the cloud.

Previous Inside Russian filtration camps, Ukrainians undergo torture and abuse
Next Coinbase announces a 63% drop in revenue amid an industry slowdown.