Economy of scale is an indispensable aspect of any competent engineering effort. Any reasonably adept AWS engineer would always include cost considerations for any change to AWS backend architecture, including helping the client decide which service tier makes the most sense for a particular application's use case...
Nonsense, AWS is an industry leader in use of the asterisk. With exception to perhaps S3 and AWS Lambda, the predominant majority of AWS services are cloaked with accounting legalese and hidden billing gotchas that can easily result in a several thousand dollar bill within days if you don't analyze every aspect of AWS service offerings including their EULAs and acceptable use policies.
So yes, it was bad form for OP to not establish billing alerts, but you can't in any way say that AWS is transparent about most aspects of their service tiers.
AWS support completely sucks unless you are paying 10K+ per month for the enterprise support tier.
My average ticket response with paid AWS Developer is probably 72+ hours, and that's just for the initial triage what's up query.
Unless you are either a seasoned Linux developer with many years of Linux internals experience, or you have an enterprise level account, all of the lower class AWS support rungs are largely meaningless.
Firefox silently pulled all production ESNI code as of v83 without a word of warning to anyone. As in, the Firefox development team simply killed encrypted SNI and told nobody that may have been using ESNI in despot regimes, in exchange for future ECH support which is not implemented anywhere yet.
Yah but what these turds did not mention is that as long ago as Firefox 83, they simply removed all production ESNI code, silently, without warning a single soul.
As in, hundreds of thousands if not millions of Firefox browser users that were relying upon encrypted SNI in despot regimes - after waiting some two fucking years for Cloudflare to actually implement ESNI on their endpoints - updated their browser one day, just to have all SNI in the clear and without a word of warning from the Firefox development team. In order to implement ECH which nobody supports yet, no mainstream even nightly web server build has ECH yet, with exception to early alpha Cloudflare go code which based on the initial ESNI debacle is probably ~1.5 years away from being implemented on their production DNS servers.
RSA SecureID has been compromised for decades, way before this puff piece of sensationalist sell newspapers bit.