Hence, the need for a new license.
However, they seem to have kept the deployment infrastructure as a trade secret, and since that didn't interact directly with MongoDB's interfaces, it șes that it really didn't come under the scope of the AGPL.
I think another commenter got it right: this is a fuss created by commercial entities that wanted to have their cake and eat it too.
Because they were already using the AGPL, and it did precisely Nothing to stop Amazon from turning into a massive free-rider who undermined the very ability of the project to fund continued development of the project Amazon was free-riding on.
We can attempt to solve this free rider problem, or we can shrug our shoulders and decide we’re just comfortable with a world with a lot of dead Open Source projects and a lot more proprietary software. But “the current situation is fine and sustainable” is head-in-sand thinking. This Bad Citizen behaviour is an existential threat to the long term prospects of Open Source.
There is no "free rider" problem. There are companies competing and one of them out competing the other. Are you as vocal about every company who failed because they didn't have a good business plan?
Now, should companies (or anyone) who use f/oss contribute back in kind or monetarily? Yes, of course they should; no one is arguing that.
IMHO all use cases can probably be covered by MIT/BSD, GPL, LGPL, and AGPL. Everything else is license proliferation and adds confusion and problems sharing code between projects.