Amazon Web Services
AWS coverage is
in development
The collector, the CUR reader and the commitment maths exist. The check set does not yet reach the depth of the Azure and AI platform work, and until it does we will not sell it as though it does.
Status
Where AWS coverage stands
AWS coverage is in development. The collector reads the Cost and Usage Report, streamed from your S3 bucket with read access only, and the pricing and commitment work is done; what is not finished is the check set at the depth the Azure and AI platform work has reached. We would rather say that here than take an engagement on a promise.
Azure, Microsoft Foundry, Databricks and Fabric are audited today. If your estate is mostly AWS, tell us — the queue and the timeline are both real, and knowing what you run changes what gets built first.
- FinOps practitioners
- AWS platform teams
- Cloud financial analysts
Method
What is already settled
The bill of record. the Cost and Usage Report, streamed from your S3 bucket with read access only is the only acceptable basis for a figure. Every rate a finding is priced at comes from there; where one is genuinely absent, the provider’s published price list is fetched at audit time, cited and labelled as list price rather than quietly assumed.
Commitments. Reserved Instances and Savings Plans overlap in what they cover, and a Savings Plan bought at the wrong commitment level quietly funds someone else’s account. Coverage is measured against coverable spend per service, and an opportunity may never exceed the spend it covers.
The provider’s own recommendations. Trusted Advisor and Compute Optimizer are read as a cross-check and grounded against current inventory, exactly as Azure Advisor is — a recommendation for an instance that no longer exists is shown and not counted.
What is deliberately out of scope. Nothing is written to your account at any point — no scratch bucket, no Athena result set, no tagging. That constraint is why the CUR is streamed rather than queried in place, and it is not negotiable.
Mostly AWS?
Say so. What customers actually run is what decides which collector gets finished first.