AWS spend, in the same model as your Azure cost.
An AWS connector is on the CloudMonitor roadmap. It will read the Cost and Usage Report into Fabric and apply the same allocation, savings, and anomaly engine you already run on Azure.
Most teams are not single-cloud. The AWS integration will bring Amazon Web Services spend into one CloudMonitor model so a multi-cloud estate reports the same way, with allocation, commitments, and anomalies side by side rather than in two separate tools.
- Will read the AWS Cost and Usage Report into your Fabric workspace.
- Will allocate spend by account, tag, and cost group, matching your Azure model.
- Will surface EC2 right-sizing, Savings Plans, and idle-resource opportunities.
- Will forecast spend and raise anomalies through the same alert routing.
Unified allocation
One model for AWS and Azure together.
The AWS connector will land spend in the same cost groups and tag rules you use for Azure, so a multi-cloud bill reconciles into one picture instead of two.
- Cost and Usage Report read into your Fabric workspace
- Account, tag, and cost-group allocation shared with Azure
- Multi-cloud totals without exporting to a spreadsheet
Savings
Right-sizing and Savings Plans, ranked by return.
Idle resources, oversized instances, and commitment gaps will be surfaced and ranked by annual saving, the same way CloudMonitor already ranks Azure recommendations today.
- EC2 and RDS right-sizing based on real utilization
- Savings Plans and Reserved Instances modeled against usage
- Idle and orphaned resources flagged with owner attached
CloudMonitor started on Azure because that is where its customers spend the most. The AWS integration extends the same discipline to Amazon Web Services so a multi-cloud organization can run one FinOps practice rather than reconciling two consoles by hand.
This connector is in planning. If AWS coverage would change your decision to adopt CloudMonitor, the beta team would like to hear which AWS services and reports matter most to you.
More cloud platforms
Other integrations like this.
Be first to connect AWS.
Join the beta and tell the team what you need from this connector.
