I come from places where that have self-managed on-prem datacenters, with self-managed CPU/GPU clusters, and using CloudFormation for internal infrastructure si

I come from places where that have self-managed on-prem datacenters, with self-managed CPU/GPU clusters, and using CloudFormation for internal infrastructure simple is a non-starter, but with some stuff in AWS, why would we do half CF and half terraform? Do it in tf et al for both. Yes I have occasionally used ELB/EFS in front of HAproxy for some of the reasons mentioned, because I recognize some situations where the value-add is worth the tradeoff. The entire point of my post is that lock-in to AWS can be bad in certain situations, which I have tried to clarify multiple times now and you have ignored every time. I'm not saying it's bad in all situations, just that it can be bad in some. Your extreme defensiveness seems strange to me for that reason. I look at it like datacenter design. You don't have just one isp. You have multiple ISP lines incoming, often in different forms (aerial/underground/wisp) so that you are never too dependent on one thing. Your metaphorical datacenter may have a OC-3840, and that may be a big feature for you, but you should at least admit to yourself and customers not having other ISP lines might be a weakness, despite the awesomeness of the 3840..