Most businesses can make the conscious decision to go with the simple 3-component option and accept that they might only get three or four nines of uptime, depe

Most businesses can make the conscious decision to go with the simple 3-component option and accept that they might only get three or four nines of uptime, depending on how flaky AWS decides to be that year. If you run a service where the worst case scenario for your site being down for an hour on a Thursday afternoon is "millions of dollars are lost" or "our high profile customers go out of business in a way that's directly traceable back to us" then yes, you need all 24 of those things. If, on the other hand, the worst case scenario for your site being down for an hour on a Thursday afternoon is "some of our customers have to manually post to Facebook so that their friends know that they've been for a run", you can probably shave about 21 nodes off that diagram.