On Friday, October 9, 2026, the Massachusetts Institute of Technology sued Amazon Web Services in federal court in Boston. MIT says the hardware security technology AWS uses to generate cryptographic keys infringes two patents the university owns. Reuters broke the story on Monday, and Investing.com, JD Journal, Hoodline, USA Herald and others picked it up the same day. That made it the most widely covered newly filed IP case in our feed this week. The case is Massachusetts Institute of Technology v. Amazon Web Services, Inc., No. 1:26-cv-14600 in the District of Massachusetts.
It is also MIT's second lawsuit in five months over the same two patents. In May, the university sued Microsoft in the Eastern District of Texas over its cloud security hardware. That case is already well into discovery. Together, the two suits show a research university putting old, foundational inventions to work against the largest cloud providers in the world.
What MIT is claiming
According to the docket, the complaint and press coverage:
- Two MIT patents. MIT asserts U.S. Patent Nos. 7,681,103 and 7,818,569, both issued in 2010. JD Journal reports that the patents come out of security research by MIT professor Srinivas Devadas and his co-authors, whose lab did early work on what are now called physical unclonable functions.
- The technology: PUFs. A physical unclonable function uses tiny, random variations that occur when a silicon chip is manufactured. No two chips come out exactly alike, so those variations can produce a value unique to each chip, a kind of hardware fingerprint. Security systems use that fingerprint to derive cryptographic keys without storing a secret key in memory, where an attacker could try to extract it.
- How AWS allegedly uses it. MIT says AWS relies on PUF-based key generation to secure its cloud infrastructure, and that this falls within the claims of its patents. The complaint attaches a claim chart for each patent and a product datasheet as exhibits.
- A supplier in the middle. MIT says the PUF technology AWS uses is supplied by Synopsys. Synopsys is not a defendant. MIT is suing the cloud provider that deploys the technology, not the vendor that sells it.
- Money, not an injunction (so far). MIT is asking for an unspecified amount of damages and has demanded a jury trial.
Amazon did not respond to Reuters' request for comment by Monday. MIT is represented by Joshua C. Krumholz and Jacob K. Baron of Holland & Knight, the same lawyers working on its Texas case against Microsoft.
The Microsoft case is the preview
The Amazon complaint follows a pattern MIT set in Massachusetts Institute of Technology v. Microsoft Corporation, No. 2:26-cv-00400, filed May 15, 2026, before Judge Rodney Gilstrap in Marshall, Texas, one of the busiest patent courts in the country. Bloomberg Law reported that MIT asserts the same two patents there and alleges that Microsoft's Azure Sphere and Project Cerberus security platforms use PUF technology supplied by Synopsys. Synopsys acquired the PUF specialist Intrinsic ID in 2024.
The Texas docket shows where the Amazon case is likely headed:
- Microsoft is fighting. It answered the complaint on July 31 with affirmative defenses and later filed its own jury demand.
- Invalidity is in play. On September 14, Microsoft served its invalidity contentions along with subject-matter eligibility contentions. That signals an argument that MIT's claims cover an abstract idea, such as generating a key from a measured value, rather than a patentable invention.
- A long road. Judge Gilstrap's original docket control order set a claim construction (Markman) hearing for December 2027 and jury selection for June 2028. The schedule was amended in August at Microsoft's unopposed request.
Expect AWS to push back with the same kind of defenses: that its systems don't practice the claims as written, that the patents are invalid in light of earlier PUF research, and that the claims are ineligible under Alice. Because the patents date from the PUF field's early years, damages arguments may also turn on timing. Patent damages generally reach back only six years before a suit is filed, and a patent's 20-year term runs from its filing date.
Why sue the customer instead of the supplier?
The most interesting strategic choice is the one MIT didn't make. If the infringing technology comes from Synopsys, why not sue Synopsys?
Patent law lets an owner sue anyone who makes, uses, sells or imports a patented invention, so a company that uses an infringing component in its own systems is directly liable. There are practical reasons, too. Damages are often measured against the value of the end use, and a hyperscale cloud built on millions of chips makes a far larger base than a licensing fee for a piece of design IP. Venue may also matter: suing the user lets MIT pick courts where those users are based or operate, such as Boston for AWS and East Texas for Microsoft.
What happens behind the scenes is often decided by contract. Large technology buyers usually negotiate indemnification clauses that require suppliers to defend them against IP claims arising from the supplier's product. Whether Synopsys ends up funding the defense, or negotiating a license to end both cases, depends on agreements the public can't see.
This is also not AWS's first major patent fight. In 2024, a Chicago jury ordered Amazon to pay $525 million to data-storage company Kove over S3 and related services in Kove IO, Inc. v. Amazon Web Services, Inc., a dispute that went up to the Federal Circuit.
Universities as patent plaintiffs
MIT isn't a patent troll. It is one of the most productive patent holders in academia, and its technology licensing office has long licensed university research to industry. Universities enforce patents for the same reason any rights holder does: licensing revenue funds research, and inventors share in the royalties. Caltech's lawsuits over Wi-Fi error-correction patents against Apple and Broadcom, and the University of Wisconsin's processor patent case against Apple, showed that universities are willing to take big cases to trial and win nine-figure verdicts. They also showed how often those verdicts are reduced or reversed on appeal, which is why most of these fights eventually end in a license.
Two suits filed in quick succession, against two of the three largest cloud providers, suggest a licensing campaign rather than a one-off. Other companies that use the same supplier's PUF technology will be watching closely.
What happens next
The Amazon case is at its very beginning. MIT has filed its complaint, corporate disclosure and the required notice to the USPTO identifying the two patents. AWS has not yet appeared. Its answer or motion to dismiss will be the first real signal of its strategy, and a motion challenging the patents' eligibility would mirror Microsoft's approach in Texas. We're tracking both dockets on the MIT v. Amazon and MIT v. Microsoft case pages.
What this means for filmmakers and other creators
A patent fight over chip security might seem far from independent film. But the core lessons apply to anyone who builds a business on intellectual property they don't fully control.
You can be liable for tools you didn't build. MIT is suing the user, not the vendor. In production, the same logic applies to software, plugins, fonts, music libraries, stock footage and AI tools. If a vendor's asset infringes someone else's rights, the claim can land on the production that put it on screen. Read your vendor terms, and favor suppliers that offer real IP indemnification.
Indemnities and E&O work together. Distributors will require errors and omissions insurance before they release a film, and E&O carriers will ask how you cleared every licensed element. Keep every license, receipt and vendor agreement with your chain-of-title documents. If a claim comes years later, those files are your defense.
Old IP can be valuable IP. MIT's patents issued in 2010 and are being enforced in 2026. Film rights work the same way. A library title, an underlying book option or a music catalog can produce income, or become the target of a claim, decades after it was created. Track rights terms, reversion dates and renewal windows so you know what you own and when it changes.
Know who owns what you made. MIT owns these patents because of its agreements with its researchers. In film, the rights to a script, score or footage belong to the production company only if the right contracts are signed: work-for-hire agreements, assignments and releases. Gaps in those documents are the most common chain-of-title problem buyers find.
Licensing is the real endgame. Most cases like this end in a license, not a verdict. For creators, the lesson is to set up rights so they can be licensed cleanly, with clear ownership, documented terms and a reliable way to collect and divide the revenue they produce.
Follow the filings, the related Microsoft case and press coverage on the MIT v. Amazon Web Services case page.
This post is editorial commentary on public court filings and news coverage, not legal advice. The allegations in MIT's complaint have not been proven. Some details, including the specific AWS systems accused and the inventors behind the patents, come from press reports and may be clarified as the case proceeds.