The Joint Warfighting Cloud Capability is the Department of Defense enterprise contract vehicle that provides commercial cloud computing services across three security classification levels: unclassified, secret, and top secret. Known across the military as JWCC, it replaced an earlier, cancelled single-award initiative called the Joint Enterprise Defense Infrastructure.
The Pentagon announced four commercial technology companies as JWCC awardees on December 8, 2022: Amazon Web Services Inc., Google Support Services LLC, Microsoft Corporation, and Oracle. The contract gives every defense mission owner a pre-competed mechanism to order commercial cloud infrastructure rather than negotiating standalone computing contracts program by program.
The Four Commercial Cloud Providers
The Department of Defense selected four technology companies on December 8, 2022, to provide commercial cloud computing services under the Joint Warfighting Cloud Capability. Those four companies are Amazon Web Services, Google Support Services LLC, Microsoft Corporation, and Oracle.
The selection followed 17 months of joint work among the office of the Department of Defense Chief Information Officer, the Defense Information Systems Agency (DISA), and Washington Headquarters Services.
Senior defense officials presented the decision during a Pentagon press briefing on December 8, 2022. Department of Defense Chief Information Officer John Sherman framed the contract as a shift in military computing infrastructure. Sherman noted the vehicle brings cloud computing to defense components at all three security classification levels used by the department: unclassified, secret, and top secret.
DISA Director Lt. Gen. Robert J. Skinner spoke alongside Sherman at the Pentagon briefing. Skinner outlined plans to establish an operational environment that includes technical accelerators for personnel who use the new contract vehicle.
The award established a multi-vendor structure across the entire department. Rather than designating a single prime vendor for all defense workloads, the department structured the vehicle so that four commercial providers remain available simultaneously to defense buyers.
Contract Structure and Security Classifications
The JWCC contract is an indefinite-delivery/indefinite-quantity (IDIQ) contract vehicle that spans the unclassified, secret, and top secret security classification levels. This multiple-award structure allows the military services and defense agencies to acquire commercial computing capacity on demand without running separate source selections for basic infrastructure.
In federal procurement, an IDIQ contract vehicle establishes terms, pricing structures, and technical standards with selected vendors over a defined ordering period. Actual work and computing capacity are purchased later through individual task orders.
A single contract structure spanning three classification tiers simplifies how defense programs manage sensitive data. Fielded weapon systems, intelligence programs, and back-office administrative tools operate under strict classification boundaries. Military cloud programs historically ran across separate, fragmented contract actions tailored to a single classification domain.
The JWCC structure addresses three specific operational environments.
- Unclassified computing: Handles administrative records, general logistics data, public information, and unclassified defense research.
- Secret environments: Supports operational planning, tactical communications, and classified mission coordination across service branches.
- Top secret domains: Isolates sensitive intelligence programs, compartmented activities, and national security data requiring the highest government handling protections.
By establishing pre-competed commercial agreements covering all three boundaries, the department gives mission owners a direct route to commercial infrastructure. Defense programs can move workloads between classification levels using the same underlying commercial vendors and acquisition mechanics.
How DISA and Mission Owners Process Task Orders
The Defense Information Systems Agency administers the JWCC contract vehicle through its Hosting and Compute Center (HaCC). Any mission owner across the entire Department of Defense is authorized to use the vehicle to acquire commercial cloud services.
Task orders under JWCC direct awards for commercial cloud services to the participating providers. To begin a procurement, an individual defense organization works directly with its internal contracting officer, or it routes the requirement through the Defense Information Technology Contracting Organization (DITCO).
Components process procurement packages through the HaCC Customer Portal. That workflow runs through the DISA Acquisition Package Preparation System (DAPPS). DAPPS standardizes how requirements packages, security criteria, and funding lines are assembled before an order goes out to the vendors.
JWCC relies on Federal Acquisition Regulation (FAR) Part 51 commercial-item procurement authority. This authority allows the department to acquire commercial cloud infrastructure at standardized rates that are lower than standard commercial prices.
The table below outlines how responsibilities are divided between central administrators and the individual defense mission owners who use the contract.
| Organization | Role under JWCC | Primary responsibility | Procurement tools used |
|---|---|---|---|
| Defense Information Systems Agency (DISA) | Central contract administrator | Manages the vehicle, vendor pools, and cloud architecture | HaCC Customer Portal and DAPPS |
| Hosting and Compute Center (HaCC) | Technical operating center | Coordinates user onboarding and provides cloud accelerators | DISA customer systems |
| Defense Information Technology Contracting Organization (DITCO) | Contracting support organization | Solicits, awards, and administers individual customer task orders | Standard defense acquisition systems |
| Individual DoD Mission Owners | End-use customer organizations | Define mission requirements, commit funding, and issue solicitations | Internal contracting offices or DITCO |
This division keeps central policy and contract oversight with DISA while keeping operational control with individual program offices. An operational unit retains the authority to decide which computing services it needs and when to buy them.
Replacing the Cancelled JEDI Program
The Joint Warfighting Cloud Capability replaced an earlier Department of Defense enterprise cloud initiative known as the Joint Enterprise Defense Infrastructure (JEDI). The JEDI program was structured as a single-award contract designed to supply enterprise cloud computing to the entire military establishment through one commercial vendor.
The department subsequently cancelled the JEDI program. Following that cancellation, defense leadership revised its enterprise cloud acquisition strategy, moving away from a single-provider model.
The transition from JEDI to JWCC changed the structural design of Pentagon cloud acquisition. A single-award contract places the full operational burden of a department-wide rollout on one company. It also forces defense programs with diverse computational needs into one proprietary environment.
JWCC substituted that single-vendor framework with a multi-award vehicle. By bringing four commercial providers under contract simultaneously, the department established an acquisition pathway where multiple companies compete for individual task orders. That model ensures individual defense organizations can pick among different commercial cloud capabilities rather than adapting all military workloads to a single commercial offering.
Strategic Impact on Joint All-Domain Command and Control
The department designed JWCC to serve as the computing backbone for modern warfighting concepts, particularly Joint All-Domain Command and Control (JADC2). At the December 2022 award briefing, DoD Chief Information Officer John Sherman addressed the strategic purpose of the vehicle directly:
“This is a huge day for the department and what we can bring to our warfighters, particularly for areas like Joint All-Domain Command and Control.”
Sherman named JADC2 as one of the strategic efforts the contract was meant to support, alongside the department’s broader push toward faster, more distributed military decision-making.
The commercial providers selected for JWCC have emphasized different operational advantages when describing their contributions to defense infrastructure.
Amazon Web Services public sector leadership confirmed the company’s award on December 8, 2022. Dave Levy, Vice President of Worldwide Public Sector at AWS, outlined the company’s focus under the contract:
“Through JWCC, AWS is honored to provide industry-leading cloud services that enable the DoD to build and deploy critical mission systems, enhance security, increase agility, and lower cost.”
Microsoft documented its role on its compliance portal, noting that the vehicle gives defense programs a faster path to deploy Azure cloud services:
“The Joint Warfighting Cloud Capability (JWCC) contract gives the Department of Defense (DoD) a faster, lower cost way to buy commercial cloud services at every classification and impact level. Microsoft Azure cloud technology is now directly available to all of DoD in one contract vehicle.”
The availability of commercial cloud tools under JWCC complements other modern defense acquisition methods. Programs developing software prototypes through other transaction authority or fielding rapid capabilities through middle-tier acquisition pathways require secure cloud environments to host their data.
Similarly, development teams using the Pentagon’s dedicated software acquisition pathway need scalable hosting to push automated security updates directly to operational units.
Congressional Scrutiny and Independent Oversight
The scale and operational sensitivity of the JWCC contract vehicle have attracted ongoing oversight from Capitol Hill. Members of Congress track how the department secures multi-cloud environments spanning unclassified, secret, and top secret networks.
On August 2, 2024, Representative Elissa Slotkin introduced H.R. 9295 in the 118th Congress. The proposed legislation directed the Department of Defense Chief Information Officer to provide a formal briefing to Congress examining security options for the Joint Warfighter Cloud Capability program. The bill highlighted continuous legislative interest in the cybersecurity controls, data safeguards, and access policies governing commercial cloud systems used by the military.
Independent government auditors have tracked federal cloud procurement challenges broadly, though specific reviews of JWCC remain limited. The Government Accountability Office released a major review of federal cloud acquisition on June 23, 2026. The report, GAO-26-107530, is titled “Cloud Computing: Federal Government Needs to Address Procurement Challenges.”
The report evaluated cloud adoption hurdles and procurement practices across the federal government. However, GAO-26-107530 did not examine or mention the Joint Warfighting Cloud Capability in its text. As of mid-2026, GAO has not released a dedicated public audit examining JWCC task-order spending, technical performance, or inter-service adoption rates.
Because no dedicated GAO performance audit exists for JWCC, defense managers and policy analysts track the program primarily through official DoD CIO updates, DISA user guidance, and legislative directives.
Commercial Cloud as Standing Defense Infrastructure
The Joint Warfighting Cloud Capability changed how the Department of Defense buys commercial computing power by creating a permanent, pre-competed procurement mechanism. Before enterprise vehicles like JWCC existed, military programs built custom data centers or spent years competing separate cloud contracts for individual programs.
JWCC eliminated the requirement for individual program offices to conduct redundant source selections for basic cloud access. A defense organization that needs computing capacity at the secret or top secret level can use existing FAR Part 51 authorities, assemble a task-order package through DAPPS, and place requirements directly with pre-qualified commercial vendors.
This framework shifts defense cloud acquisition from isolated, program-specific infrastructure builds toward standing commercial services. As military operations rely more on distributed data networks, defense program managers can consult the DoD CIO portal to review task order rules, confirm security compliance requirements, and evaluate how the four JWCC awardees support operational cloud needs.