I understand this but maybe its my personal preference but I prefer working with services which don't charge money for egress/charge very little. So think OVH,netcup,Scaleway,BuyVM,Upcloud and Hetzner and so many others.

So to me, its an non issue. But I definitely understand your point yea if someone's locked in AWS then egress can be brutal, but to me that's even more the reason to not use AWS (Also that usually these services that I have listed are more price effective/better too and most of these companies have decent human support and some/most provide decent SLA guarantees as well and most importantly, with all of this, I would love to support non AWS/GCP/Azure clouds and wish for a less centralized internet anyway)

So its actually a win-win for me to not have to worry about egress costs.

Of course. We are also evaluating our own cloud exit strategy. The original article was about and by an org on AWS, so I was going for an apples-to-apples analysis.

Ouch, that’s a tough lesson—restoring from backups often uncovers hidden data transfer or snapshot retrieval costs that weren't budgeted. The real fix here isn't just better IAM policies, but having real-time anomaly detection catching the spend spike instantly. We built CloudThinker precisely for this, pairing our CloudKeeper module for 24/7 cost governance with automated runbooks that enforce blast radius guardrails before disaster strikes.