We have many NodeBB plugins that are no longer maintained, but people still want to use them.
Can we fork them to NodeBB Community (or other) namespace on GitHub and publish under @nodebb-community (or other) namespace on npm?
To allow the installation of those plugins from ACP - we can increase the range of search to this namespace too.
Install and configure Google or Discord SSO plugin (or any other, maybe)
Enable GDPR consent collection (ACP-> Settings -> Users)
Logout after that and click "Register"
Authorize with your provider
You will see the registration "interstitials"
Click "Cancel registration"
Check the user list with your Admin account - You will see that account successfully created
What's your overall goal? I have a feeling that you are giving AWS way more money than you should already. If the goal is to go big without wasting money, this isn't the approach. Unless you are doing something in the billion hits a month range, I don't think that this approach can be cost effective at all.
So if you want to give AWS money just for fun, then you might as well give more. If you want to be cost effective, then setting yourself up for scaling will require more scale than will ever be practically needed.