It's likely that the outrage is from people who don't use MongoDB. A lot of my things rely on the Community Edition. Even with the SSPL, I'm still eagerly waiting a few more weeks to upgrade to 4.2, and take advantage of some of what's new.
If I found a bug, and was adventurous to fix it, I can still open a JIRA and submit a PR to the project ...
The license is no longer OSI approved, so how do you know what you're allowed or not allowed to do?
How do you know that what's keeping AWS from using it isn't also creating a problem from you?
Have you consulted with a lawyer?
That's one benefit of using actual Open Source. You have a definition that all licenses have to comply with, such that developers know exactly the set of freedoms that's common between all of them.
Once you step out of that definition, you're on your own. So you know, I wouldn't take legal advice from random people on HN, you might run into problems.
You're outsourcing your thinking to an organisation that's looking at specific definitions. Might be better to read the licensee and compare it with the previous one.
It's an AGPL + AWS-is-killing-our-support/monitoring/ops-business license.