Cloud Cost Management, or FinOps is tricky. Imagine Team A started consuming much more resources and the management just starts seeing hair-pulling consequences at the end of the month in AWS bill.
How to react fast and prevent unnecessary cost? Or become very restrictive by blocking spinning up a new resources w/o explicit management approval, this can slow down and progress and also can be catastrophic for the company.
What to do?
Introduce FinOps process, namely, start attributing cloud costs for every resources to a cost center, which is typically a team or department.
Use infrastructure as a code and try to avoid any manual manipulations from the console.
Automate infrastructure as a code repository with tools like InfraCost, that will give you cost estimation on the new resources to simplify decision making and/or budgeting.
Use cost anomaly detection provided by the cloud vendor to react on cost changes quickly with investigation.
Make costs information visible and accessible by creating dashboards and using certain third-party applications for this purpose.
And let the cost control be with you.