I have direct multi-year experience where an AWS heavy client (with a strong tie to Amazon) decided to shift course because AWS spend went nearly vertical despi

I have direct multi-year experience where an AWS heavy client (with a strong tie to Amazon) decided to shift course because AWS spend went nearly vertical despite the velocity of features delivered, and moved to migrate all logic/data into other enterprise systems where possible. So for the first few months, it was moving all business logic to lambdas/RDS then the next year, moving it all back elsewhere - not necessarily on-prem, but anywhere except AWS. So I'd expect your cloud team to get very much like infra once cost realities become involved. It's possible your volumes/costs are much less for the features you build - in that case, kudos to designing stuff that is perf-aware - but sometimes you don't control volume and that's a cost-risk.