This article is based on reporting originally published at searchaws.techtarget.com (October 2019).
AWS Opens Cloud Credits to Open Source Projects
AWS announced a promotional cloud credits program aimed at open source software (OSS) project maintainers, offering them AWS credits to use for infrastructure tasks directly related to their projects. The move was framed as part of a broader effort by AWS to deepen its engagement with the open source community alongside sponsorships, increased code contributions, and the open sourcing of some of its own internal technology.
According to an AWS blog post at the time, typical use cases for the credits include upstream and performance testing, CI/CD pipelines, and storage of build artifacts on AWS infrastructure. The stated goal was to relieve resource pressure on OSS projects so their maintainers could focus on expanding and innovating within their communities.
Who Qualifies and How the Program Works
To be eligible for AWS open source credits, project maintainers must meet the following criteria:
- Active AWS account with no outstanding balance.
- OSI-approved license: The project must be released under a license recognized by the Open Source Initiative (OSI), such as the GNU GPL or Apache License 2.0. AWS indicated exceptions could be made for projects using non-OSI licenses on a case-by-case basis.
- Specific credit request: Maintainers must request a defined amount of credits and provide a clear description of intended use.
- One-year validity: Credits are valid for twelve months from the time they are issued.
AWS stated it would select recipients partly based on alignment with Amazon’s leadership principles. Projects with maintainers from more than one organization, or those owned by nonprofits, were given preference in the selection process.
Representatives from AdoptOpenJDK and the Cloud Native Computing Foundation (CNCF), among others, publicly endorsed the program and stated they were already benefiting from it at the time of the announcement.
Context: AWS and the Open Source Community
The announcement came against a backdrop of growing friction between AWS and certain segments of the open source ecosystem. AWS had faced criticism—particularly from commercial open source vendors—for consuming and building managed services on top of popular OSS projects without proportional contributions back to those projects.
The tension had already escalated to legal action in at least one case. Elastic filed a trademark infringement lawsuit against AWS following AWS’s release of Open Distro for Elasticsearch. AWS argued the fork was necessary after Elastic began mixing proprietary code into what had been a fully open source project. That dispute would later lead to much broader licensing changes at Elastic.
Industry Reaction: Table Stakes or Genuine Progress?
Analysts and practitioners had divergent takes on the significance of the credits program.
“It’s actually pretty consistent with industry standard open source engagement to provide some level of free or heavily discounted services, so while it’s certainly an opportunity for AWS to try to build some goodwill, it is at the same time something like table stakes.”
— Stephen O’Grady, Analyst, RedMonk
Others were more skeptical about the timing of the initiative.
“They could have made this a program years ago. Open source groups have been reaching out to cloud vendors to donate resources for a long time. I think in the past it was a more human process. They’re making the process public for an obvious reason. … Is the timing suspect? You tell me.”
— Ryan Marsh, Serverless expert and DevOps trainer, TheStack.io
Unanswered Questions
At the time of the original reporting, several practical details about the program were not publicly addressed by AWS:
- The total budget AWS planned to commit to the credits program.
- The minimum or maximum credit amount any single project could receive.
- What would happen to credits if a project’s maintainer decided to commercialize the project after receiving credits.
These gaps left observers uncertain about the scale and long-term intent of the program.
How AWS Compared to Google at the Time
Even with the credits program, AWS had not matched the depth of Google’s commercial OSS engagement at that point. At Google Cloud Next in April 2019, Google announced expanded partnerships with seven commercial open source vendors—including MongoDB, Redis Labs, and DataStax—to create tightly integrated, fully managed services on Google Cloud Platform. Those deals included shared support and unified billing, going significantly further than credits alone.
The AWS credits program nonetheless represented a formal, structured acknowledgment of its obligations to the OSS ecosystem—a notable shift in posture even if industry veterans considered it overdue.
Key Takeaways for DevOps Teams and OSS Maintainers
- If you maintain an OSI-licensed open source project, check whether an AWS credits program is currently active and whether your project qualifies.
- Use cases like CI/CD, artifact storage, and performance testing are explicitly supported use cases for cloud credits across multiple providers—not just AWS.
- When evaluating cloud vendor support for OSS, look beyond credits to assess code contributions, governance participation, and partnership terms.
- The broader AWS-vs-OSS tension illustrated by the Elastic lawsuit has since reshaped open source licensing strategies across the industry, making license choice a strategic decision for project maintainers.