While leveraginvg serverless gives a lot of benefits in terms of hardening and infrastructure setup, all the traditional application security issues (e.g. OWASP TOP 10) like SQL injection can still apply.
You can create a custom auth flow using lambda and cognito; you can return a series of challenges and create a stateful flow using session tokens which results in a set of access, identity, and refresh tokens.
Alternatively you can use the auth code flow baked into lambda; if you have premium support make a case and someone can walk you through it :)
Once we lost the user account DB at a startup to database data loss and some other day, someone logged into mongodb and dropped all the tables and backups were not test before, so they did not work.
After that we no longer store these details.
We've been using amazon cognito with lambda authorizers.
Exactly. GitHub is quite good at showing the history and current state of a file. This extension aims to also provide a way to see how a file might change in the future.
Sunk cost or costly effort? There are a more than a handful of large of technologies, frameworks and libraries used in my industry which would have to be ported/rewritten and supported from C++ before anyone would think twice before using an alternate language. Particularly when speed is the name of the game (in terms of integration, not just compiled binaries). There are hundreds of C++ libraries employed daily that would be non-trivial to port.
I was exactly feeling like this before i started budiness then i found friends to take over the boring parts.