CloudWisdom’s Bill Analysis tool uncomplicates the task of tracking and budgeting your AWS or Azure Cloud spend. This tool reads the Cost Explorer data from your AWS or Azure account and breaks it down by cost allocation tags, services, and metadata.
About These guide show you how to use the Bill Analysis tool using different scenarios; for a full list of features, see our Bill Analysis Documentation pages. The Bill Analysis tool requires at least one AWS or Azure datasource enabled on your account.
Budget Alerts can be set in the Bill Analysis tool using a combination of:
Saved reports Send Daily Email Matching Conditions Read the guide on creating AWS Bill Analysis reports or creating Azure Bill Analysis reports
AWS Practice Create a daily Budget Alert of cost deltas above $5 for EC2 - Other Usage Types.
Navigate to Cost Management > Bill Analysis. Select Quick ranges > Latest day.
AWS Bill Analysis Report To use the AWS Bill Analysis tool, login to CloudWisdom and navigate to Cost Management > Bill Analysis.
Create and Save a Monthly Total Cost Report Let’s say you want to explore a breakdown of your bill across AWS Availability Zones for the past month (30 days). How would you do that?
Select Latest 30 days in the Quick ranges dropdown. Select CONFIGURE to open the configuration modal.
AWS Bill Analysis Report Cost deltas are noticeable rises in resource cost discovered when comparing two distinct time periods in your AWS billing history. Measuring your cost deltas against the average application workload cost is a great way to discover opportunities to save.
Read the guide on creating budget alerts before using this guide.
In the previous guide, we created a Bill Analysis report that displays EC2 - Other costs from the Latest 30 Days broken down by Usage Type.
AWS Getting an accurate picture of your entire AWS bill requires looking at your costs from multiple perspectives. Examining dimensions like AWS Services, Reservations, and Storage usage individually often gives you new insights you wouldn’t otherwise have viewing them together as a whole.
In this article, we’re going to show you how to filter out Reservations from your AWS Services Costs analysis. We want to do this because Reserved Instances have a unique pricing model in comparison to On-Demand instances.
You already have a tagging strategy in place and you’ve mastered exploring your costs by services, attributes, and tags. So what’s next?
Another great way to discover savings opportunities (or simply gain more context for your bill) is to examine what hasn’t been given a particular value for a tag. The easiest way to find resources that are missing tags is to use the Bill Analysis tool.
Prerequisites This guide assumes you have already created User-Defined Cost Allocation Tags from your AWS Console.
When you purchase EC2 reservations with no upfront payment or partial upfront payment, the monthly installments appear as a single charge on the first day of each month:
This distorts the scale of the cost axis and makes it difficult to see spending trends.
Even worse, when you purchase EC2 reservations with Partial or All Upfront payment the upfront costs are recorded at the time they are charged rather than at the time of associated usage and they typically do not show up in the graphs at all.