System-wide? Not really since AWS has hundreds of services. Some services or some regions fail sometimes, but in 99% of cases good architecture can avoid that.
Sure, I'll warm my home and feed my family on good vibes, then.
I'm trying to build something awesome, not work for Peace Corps, I already accept a certain amount of third or fourth degree Evil, just by using Apple products, or even using this website (can you be certain not a single byte of this data touches material that was made under duressing work conditions?).
It's the whole The Good Place problem, all over again; it's impossible to live a moral life in a globalized society, if you think any use whatsoever of anything that could have in some way contributed to an amount of unhappiness is a Thing Worth Avoiding.
Well to clarify, I'm not necessarily saying that the ethics reason clearly outweighs all other tradeoffs. I was responding to the very specific assertion that "no reason exists". My greater point would be that the comment I'm responding to was being a little hyperbolic. There are definitely reasons not to use cloud. Your ultimate decision, especially in the context of project-specific requirements, is a different, bigger discussion.
Why do you need to use a major service though? There's a ton of cloud providers you can use that offer pretty much a similar range of services and are certified, e.g. ISO27001, SoC2.
Major services have major pay outs when majorly bad things happen to their enterprise customers. Finance will not approve a level of risk that would bankrupt your cloud provider for any critical service. I suppose this is mostly immaterial for startups given they don't have the weight or value.