Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
In March 2018, Amazon Web Services (AWS), Oracle and Microsoft were competing for influence over a proposed Pentagon cloud contract called JEDI. AWS was widely viewed as the early favorite, but the central fight was also about whether the Defense Department should rely on one cloud provider or award work to several. Microsoft eventually won the JEDI award; the Pentagon canceled the program in 2021 before it was implemented as planned, then awarded its replacement to AWS, Google, Microsoft and Oracle.
What the Pentagon wanted to buy
JEDI—short for Joint Enterprise Defense Infrastructure—was a planned enterprise-wide cloud contract for the Department of Defense. Its potential ceiling was up to $10 billion over as many as 10 years, not a commitment that the Pentagon would spend that amount. The goal was to provide computing, storage and data-processing capacity, including support for artificial intelligence and machine learning, across a sprawling department with many legacy systems. The Pentagon envisioned support for unclassified, secret and top-secret workloads, including operations at the tactical edge, where connectivity can be limited or intermittent. The Defense Department inspector general’s report describes the planned contract and its scale.
This was not simply a contest to rent ordinary data-center capacity. A provider would need to meet stringent security requirements, support workloads at different classification levels, connect with existing Defense Department networks, and operate in settings ranging from large facilities to remote military locations. Migration of old systems, data portability, performance, resilience and pricing also mattered. Commercial cloud can provide scalable infrastructure, but the Defense Department remains responsible for deciding which workloads can use it and for ensuring mission continuity.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhy AWS looked like the early favorite
At the time, AWS had a substantial lead in commercial cloud infrastructure and established federal-cloud experience, including classified government work. Contemporary reporting described AWS as the likely front-runner; that was an industry assessment, not an official Pentagon finding. A 2018 account characterized the CIA cloud arrangement as dating to 2013 and worth about $600 million. That is a historical report, not a statement of the current value or status of CIA cloud services. Contemporary coverage of the competition also noted that a Defense Department-affiliated unit had awarded migration-support work to REAN Cloud, an AWS affiliate. The contract was initially reported at up to $950 million before being reduced to $65 million, intensifying competitors’ concerns about whether AWS had an advantage.
#1 Best Overall
That earlier work was not the JEDI award. The distinction matters: AWS’s perceived lead and existing government business did not mean it had won the Pentagon’s enterprise contract.
Why Oracle and Microsoft challenged the structure
Oracle: procurement objections and a threatened business
Oracle objected to JEDI’s single-award structure, arguing that the solicitation restricted competition and exceeded the Pentagon’s needs. It also had a commercial stake: many government systems relied on Oracle databases, and a broad move toward hyperscale public cloud could weaken the company’s established database and government-technology business. Oracle separately protested a REAN Cloud award, arguing that it could open a route to AWS work. The Government Accountability Office’s statement on Oracle’s protest documents the challenge; the existence of a protest does not establish that AWS received improper favoritism.
Rank #2
Microsoft: a bidder with a case for multiple clouds
Microsoft was a serious potential provider as well as an incumbent enterprise-technology supplier. Its strategic case emphasized hybrid environments and phased migration: some applications or data might move to cloud services while others remained in-house. A single-provider award could concentrate the Pentagon’s business and limit opportunities for other suppliers to sell cloud, software, security, migration and integration services. Those were elements of Microsoft’s competitive positioning at the time, not an independent technical verdict that its approach was best. Microsoft ultimately received the JEDI award in 2019, though the program was later canceled.
The one-cloud versus many-cloud argument
Supporters of a single provider could point to simpler procurement and governance, more consistent architecture and security controls, economies of scale, and the possibility of standardizing fragmented systems around a common platform. A unified environment might also make it easier to aggregate data and run analytics across the department.
Rank #3
Critics argued that concentrating the work could increase vendor lock-in, reduce the government’s negotiating leverage and create a single point of commercial dependence. Multiple providers could offer alternatives if a service failed, let the Pentagon match workloads to different capabilities and preserve competition. Those were arguments about risk and procurement design, not proof that a single cloud would necessarily be unsafe or that multiple clouds would automatically be more secure.
Multi-cloud has costs of its own. Managing identity, monitoring, security policies, data movement, skills and contracts across providers can be harder than standardizing on one. Nor does a multi-vendor contract make providers interchangeable: classified-service coverage, available services, locations, support and integration can vary. At the tactical edge, bandwidth limits and disrupted connections complicate both approaches. The meaningful question is not simply “one cloud or many,” but how the department can provide the right capabilities while managing resilience, portability, security and operational complexity.
More than three companies were involved
The 2018 headline’s three names capture the most visible rivalry, not the full field. IBM, Google, SAP, General Dynamics/CSRA, Red Hat, VMware, Dell Technologies and Hewlett Packard Enterprise were among the companies reported as opposing a single-provider structure or exploring parts of the broader opportunity. Not all were positioned to supply hyperscale cloud infrastructure directly. Some could participate as software providers, systems integrators, migration partners or subcontractors; some also had existing government-technology businesses to protect. Contemporary reporting on the broader opposition helps explain why the fight was about procurement design as well as provider capability.
How JEDI became a different program
| Date | What happened |
|---|---|
| March 7, 2018 | The competition over the planned Pentagon cloud business was described in contemporary coverage. |
| July 26, 2018 | The Defense Department released the JEDI request for proposals. |
| October 25, 2019 | The Pentagon awarded JEDI to Microsoft. |
| February 13, 2020 | A federal court issued a preliminary injunction after AWS challenged the award, halting performance. |
| September 4, 2020 | The Pentagon reaffirmed Microsoft’s award after reevaluation. |
| July 6, 2021 | The Defense Department canceled JEDI and began termination procedures, saying requirements and the cloud market had changed. |
| December 7, 2022 | The Pentagon awarded contracts under the replacement program, JWCC, to AWS, Google, Microsoft and Oracle. |
The legal dispute and allegations of outside political pressure became part of the story, but should not be mistaken for a finding that the award was technically or financially wrong. The Defense Department inspector general reviewed allegations related to the procurement and outside pressure, but explicitly did not assess the merits of the technical or price evaluations or decide whether Microsoft’s award was substantively correct. The report sets out the scope and limits of that review.
Best Value
The Pentagon said JEDI no longer met its needs as requirements, cloud capabilities and initiatives such as Joint All-Domain Command and Control and AI and data programs evolved. It replaced the single-award plan with the Joint Warfighting Cloud Capability, or JWCC, a multi-award, multi-vendor contract intended to provide services across classification levels and from domestic facilities to the tactical edge. The four awardees were AWS, Google Support Services, Microsoft and Oracle. The Defense Department described the contract ceiling as $9 billion over five years; a ceiling is not guaranteed spending, actual obligations or revenue. See the JEDI cancellation announcement, the JWCC briefing and the announcement of the four vendors.
What the outcome says about the original fight
The Pentagon did not award the original JEDI business jointly to Amazon, Oracle and Microsoft. Microsoft won that contract, but litigation halted performance and the Defense Department later canceled it. The later JWCC program awarded contracts to those three companies and Google. Being named to JWCC makes a company eligible to compete for work through the vehicle; it does not mean that every Defense Department system migrated to it or that the vendor received the contract ceiling.
The shift from JEDI to JWCC was not just a technical choice. Requirements changed, the cloud market matured, and the procurement faced legal and political pressure. The episode shows how contract structure can shape which companies get access to government work—and why a defense-cloud decision must account for mission needs, resilience and vendor concentration, not just commercial market share.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
