Not sure why this is downvoted. It’s a perfectly valid “serverless” architecture.

The only downside is that it can get quite messy maintaining.

Hello, Author here.

Could you elaborate on what part of the maintenance would be messy? I was under the impression that maintaining this would be quite easy because there is no physical server present anywhere in this setup.

Not OP, but I think you should be fine. It can get messy if you're using it as a backend for an application that may at some point have different versions in the field (or dev/testing/staging) so you need to support multiple versions of your APIs. It's not impossible, but it can get messy. If anybody has some good rules/frameworks to organize that kind of thing, I'd appreciate a reply.

I would guess because then it's "just another serverless web app" and invalidates the title which is "Hosting your ENTIRE web app...".

Where even is the downvote button?

Hidden until you get more karma.