Unironically, this is one of the simpler setups for a multi-node WP setup I have seen, and I have set up prod WP many times. Anyone with associate level knowledge of AWS can do this. There is a reason there are entire companies (pantheon) dedicated to hosting Wordpress for you: doing it with speed, resiliency and redundancy is hard.

Meta: I've vouched for this comment. You appear to be shadowbanned.

They don't like conservative opinions here, so I am not surprised.

You seem to be confusing Amazon's internal infrastructure and its development model to how AWS is used by customers.

I would have posted internal slides directly from app architects or even service(-prototyping) dev teams within AWS including similar vibes regarding this discussion, but for obvious reasons that's not a good idea. But whom am I telling that ... That "reference architecture" aimed at customers using their infrastructure regarding a Wordpress installation gets the general idea across, though.

That's the result though, right? Radical internal simplicity forces incidental external complexity.

No, I'm talking about internal services that aren't directly exposed through AWS API. This represent the large majority of the internal codebase.

Would it be any simpler when running on-prem or in another cloud?