Use the Cost page in Stax to explore your AWS spend further. If you'd like to narrow down your exploration to one part of the business, use the Global Filters to filter Stax down.
The default AWS cost that is reported in Stax is based what you actually used, which might not be the same as what you paid for.
AWS has lots of ways to pay for resources, which can make it hard to understand what your team is actually using. Tracking consumption, or usage cost is useful for managing spend, as that’s the number that you can really influence.
The default cost you see in Stax removes some one-off charges and financial constructs like AWS Support, Tax, Reservations and Credits. To match Stax to your AWS bill, toggle on the Financial Filters:
Financial Filters will include the following in your view of AWS Cost in Stax:
One-off charges, like AWS Support and Tax.
While this is a cost that will be on your AWS bill and you will have to pay for, it’s not related to what you use or provision. Excluding these costs in your day to day view of AWS spend, removes noise that you don’t need to hear.
Similarly, Reservations of Instances or Capacity in AWS, can significantly reduce your bill, but are charged in a way that creates noise in your day to day view of cost. You might pay all upfront, in which case you’ll see a big cost on the day you’re charged, and nothing for the rest of the year. Or, you might be getting charged monthly, in which case the first of the month has a big cost spike, and the rest of the month is relatively flat.
Additionally, in lots of businesses, only one person makes the decision of what to reserve and the people who are actually using AWS can’t influence this dollar amount. The dollar amount that you can influence is your on-demand cost, which is what you’ll see in your default view of Stax.
As Reserved Instances get used during the month, Stax allocates them to usage for the AWS service in question, so your RI – EC2 cost will go down over the month, and your EC2 cost (reported as Usage) will go up.