As AWS launches more services based on open source projects, some devs say AWS poses an existential threat by lifting others' work and renting access to it
Community leaders say AWS increasingly poses an existential threat — March 11, a Vice President at Amazon Web Services … Tweets: @mvzelenks , @vineetdevaiah , @mvzelenks , @acsifferlin , @mvzelenks , @medium , and @sogrady Tweets: Michael Zelenko / @mvzelenks : Much of our Amazon antitrust anxiety is currently focused on e-commerce. But @koxinga21 reports a similar dynamic is happening w/ AWS and the open source community. Open Source, Betrayed: Industry leaders accuse Amazon of playing a rigged game with AWS https://medium.com/... @vineetdevaiah : Google did this with Android and Chrome to kill everyone and take over two large consumer markets but the open source community never said anything 🤷🏽♂ ️ I always wonder why Google gets a pass at all@the shitty behavior they have http://twitter.com/... Michael Zelenko / @mvzelenks : Here too the company is both marketplace and vendor. Why shell out for Elasticsearch, when AWS now offers the newly minted Open Distro for Elasticsearch? Why use MongoDB when you can turn to AWS's newly integrated version, DocumentDB? Alexandra Sifferlin / @acsifferlin : For open-source developers, AWS has gone from a neutral platform to a cutthroat competitor: http://onezero.medium.com/... Michael Zelenko / @mvzelenks : It's all perfectly legal, but it may threaten the longterm viability of these companies. And as observers like @profgalloway discuss Amazon spinning out AWS to preclude antitrust action, a troubling question looms overhead: will AWS become big enough to be a monopoly of its own? @medium : Open-source software relies on a certain amount of good faith from those who wish to share and modify code freely. Now Amazon is weaponizing that good faith to cripple competition—ringing the antitrust alarm yet again. http://read.medium.com/zl5v2ci Steve O'grady / @sogrady : @koxinga21 hey Andrew, just read this piece. as an FYI, it misrepresents the context of my quote. you wrote that i cite AWS, etc. as existential threats, but my claim was rather that they are regarded as such by commercial OSS organizations. https://onezero.medium.com/...
Context & Ripple Effects
The accusation is not new so much as newly organized: as far back as 2018, reporting on Andy Jassy's playbook described AWS deliberately building services that compete with its own platform partners, and today's piece names the pattern from the other side of it — Open Distro for Elasticsearch and DocumentDB are hosted alternatives to projects whose communities never agreed to be distribution channels for Amazon.
What has changed is the response: with venture money flowing into open-source startups and multi-billion-dollar exits becoming normal, per the history of open source funding covered in October, developers now have companies worth defending — which is why the community leaders quoted here frame AWS not as a customer but as an existential threat, and why the antitrust anxiety Michael Zelenko notes is migrating from e-commerce to cloud infrastructure.
First-order effects
- Open-source projects like Elasticsearch and MongoDB face direct revenue cannibalization: AWS hosts managed versions of their work, capturing the paying workload while the upstream communities carry the development cost.
Second-order effects
- Project maintainers are pushed toward restrictive source-available licenses to block cloud resale — the commercialization debate Wired examined in August — which fractures the 'open' label itself and forces enterprises to re-evaluate what they can freely deploy.
Third-order effects
- If the pattern holds, infrastructure consolidates around whoever operates the hosting layer rather than whoever writes the software, echoing the AWS lock-in dynamic described by the anonymous engineer who found the platform easy to enter but hard to leave — and giving regulators a concrete monopoly case beyond retail.
The trend: Cloud providers are converting community-built open source into proprietary-adjacent managed services, forcing maintainers toward restrictive licenses and turning open-source governance into an antitrust question.