AWS charges for what you use and invoices after the month ends. A test loop that calls an AI model all weekend, or a forgotten GPU instance, can run up thousands of dollars before the invoice shows it. It gets worse in a company that mostly runs on Azure, where the AWS bill goes to finance and no engineer ever opens it.
Treat AWS like Azure: Do you monitor your costs in Azure? Someone must own the number, so see Do you have a FinOps owner for every project?
Do all of this in the management account, because it pays the bill and sees every member account:
Neither tool is real time. AWS refreshes budget data up to three times a day.
Nobody at Northwind checks the AWS bill. A test loop calls a Bedrock model from Friday night, and the team hears about it when finance queries the invoice three weeks later.
❌ Figure: Bad example - Bad example - With no budget or anomaly alert, the invoice is the first warning
Cost Anomaly Detection posts to Northwind's #aws-alerts channel on Saturday. The developer on call stops the loop that afternoon.
✅ Figure: Good example - Good example - An anomaly alert in a team channel gets the loop stopped in a day, not a month
These lines grow with usage:
Microsoft retired the Azure Cost Management connector for AWS on 31 March 2025. The replacement is to export AWS costs in FOCUS, the open billing format both clouds can produce, and load them into a FinOps hub:
ingestion container under Costs/yyyy/mm/aws/[account-id]. The hub does not pull from AWS, so you build and run this jobStep 3 is where this goes wrong. Each run must replace the whole month's folder, and a Data Explorer hub ingests nothing until you upload a manifest.json after the data files. Follow Ingest from other data sources exactly.
Warning: Microsoft's documentation says support for non-Azure data "hasn't been explicitly tested in the latest release". Reconcile the hub's AWS total against the AWS invoice for a closed month before anyone makes decisions from it.
Figure: FinOps hubs are not explicitly tested with non-Azure data, so reconcile the AWS total yourself