IMHO the Trusted Publisher/Provider mechanism will make Zennet the ultimate solution even for AWS, from a pure economical point of view. If you have a datacenter, probably the ultimate way to monetize it is over a free and open market.
AWS can have an address on Zennet, set their own prices and configs (the network is very flexible), and give their own assurances.
From pure economical point of view (only?), even Google doesn't have to buy or rent hardware any more if not over Zennet.
Very true, but this all happens naturally and side-band to zennet itself, with the exception of zennet offering a facility for a participant to "cry foul" to that "meta-market" community against an established identity in an independently verifiable way. If I get an insane bill of X or don't get paid what services Y that I bill sanely for, I can have a certificate that it is necessarily the case that the bill in question was for X, and what services in question were Y. The independent participants of the "meta-market" can look at those certificates and know that is what was attempted to be transacted, and make their own decision about who to trust more and who to ding, if any, in their own local trust metric. None of this process is a part of zennet itself, but zennet should offer the two tools necessary to do it securely in a decentralized fashion - resource accounting certificates and receipt certificates.
Of course some will point out how it is an "unsolvable problem" just like "double spend" so zennet does something very similar to what btc did, solves it only with probabilistic proofs. The details are lightly messy, so I'll just refer interested readers to the pricing whitepaper.
Those probabilistic proofs over ledger-of-account are why I <3 bitcoin and the addition of some more probabilistic proof certificates over ledger-of-resource-account are why I will <3 zennet. Simple.
Anyway, I guess what zennet could never really provide is the combination of both ongoing assurance and immediate elasticity, where AWS can provide this up to their fixed capacity. Zennet itself has no fixed capacity, and makes no assurances about the types of hardware available at any particular moment. Of course this is just a trade-off against how many nodes you are willing to trust. Remember that pricing selections and publisher/provider inclusion (which zennet largely treats as the same problem) are easily handled with some local scripts so you get to decide these conditions yourself.