On July 6, 2021, the Department of Defense announced the cancellation of JEDI — the Joint Enterprise Defense Infrastructure program — ending one of the most contentious procurement processes in the history of government technology acquisition. What replaces it will shape DoD cloud strategy for years to come.
What Was JEDI and Why Was It Cancelled?
JEDI was designed to accelerate cloud adoption and digitize DoD operations, facilitate military communication, and improve national security infrastructure through a single enterprise cloud platform. The program sought proposals in 2017, with Amazon Web Services (AWS), Microsoft, and Oracle competing for the contract.
Microsoft won the $10 billion contract in 2018. AWS challenged the process in court, alleging bias in favor of Microsoft. Courts halted the contract, and following years of litigation, the Pentagon ultimately decided the program had become unworkable — terminating it to pursue a fundamentally different approach.
The Joint Warfighter Cloud Capability (JWCC)
The replacement program, Joint Warfighter Cloud Capability (JWCC), takes a multi-cloud approach — procuring cloud services from multiple vendors simultaneously rather than concentrating all DoD workloads with a single provider.
The reasoning was sound. Cloud computing capabilities had evolved dramatically since 2017. DoD’s operational doctrine had expanded beyond traditional domains into cyber and space. Different military units needed to communicate, process, and share data in ways that a single-vendor architecture couldn’t optimally support. Flexibility, resilience, and avoiding vendor lock-in had become strategic priorities.
Why Multi-Cloud Is the Right Call for DoD
Best-of-breed capability selection. Organizations can select the optimal product from multiple providers for each workload rather than being constrained by a single vendor’s offerings. AWS may be better suited for certain compute-intensive intelligence workloads; Azure may be preferred for applications tightly integrated with Microsoft productivity tools and identity management.
Improved security posture. Distributing applications and data across multiple data centers and providers makes comprehensive breach more difficult. A vulnerability in one vendor’s environment doesn’t necessarily expose all DoD workloads.
Flexibility and negotiating leverage. Multi-cloud reduces vendor lock-in and gives DoD ongoing leverage in contract negotiations. A credible ability to shift workloads creates competitive pricing pressure.
Network performance optimization. Organizations can select data centers and content delivery networks strategically, reducing latency for forward-deployed users and improving data availability across global operating environments.
What This Means for Defense Contractors
The JWCC model creates more distributed opportunity across the defense IT ecosystem. Multiple cloud providers mean multiple integration, migration, and managed service opportunities — and prime contractors supporting DoD cloud adoption need expertise across AWS, Azure, and potentially Oracle and Google Cloud environments.
For smaller contractors and system integrators, multi-cloud creates a more competitive landscape than a single-vendor lock would have produced.
CEdge provides cloud migration, multi-cloud architecture, and FedRAMP authorization support for DoD and intelligence community clients across AWS GovCloud and Azure Government environments.