You open the AWS Billing Dashboard for the first time and see: "Month-to-date spend," "Forecasted month-end spend," a list of services, some charts, and a bunch of numbers that may or may not include tax. It's not immediately obvious which numbers matter, which ones are estimates, and which ones you should be worried about.
Here's the breakdown.
The Top-Line Numbers
Month-to-Date Spend
This is how much you've spent so far this billing month. The billing month runs from the 1st to the last day of the calendar month. This number is updated approximately every 24 hours — it is not real-time. If you launched expensive resources today, they might not appear here until tomorrow.
Watch this number for: unexpected jumps compared to the same point last month. If you're 15 days into the month and your MTD spend is already higher than last month's total, investigate.
Forecasted Month-End Spend
AWS's estimate of what your total bill will be when the month ends, based on your spending so far and the remaining days in the month. This is a linear projection — it assumes you'll spend at the same daily rate for the rest of the month.
The limitation: Linear projections don't account for weekday/weekend patterns, one-time charges, or changes you've made mid-month. If you terminated a bunch of resources yesterday, the forecast won't reflect the savings until enough days pass to change the daily average.
Last Month's Total
Your final, actual bill for the previous month. This is the number that was charged to your credit card. Compare this to the current month's forecast to see if you're trending up or down.
The Service Breakdown
Below the summary, the dashboard lists your spend by AWS service. This is where you'll spot anomalies.
The important services to watch:
- EC2 (Elastic Compute Cloud) — Usually the largest line item. Includes instance hours, EBS storage, data transfer, and Elastic IPs. A spike here usually means new instances running (expected or not), data transfer costs (often unexpected), or EBS volume accumulation.
- RDS — Database costs. Check for instances that are oversized for their actual workload. A
db.r5.2xlargecosts ~$1,200/month — make sure you need that much capacity. - S3 — Storage + requests + data transfer. Storage costs grow silently as logs, backups, and versioned objects accumulate. Check whether lifecycle policies are in place.
- Data Transfer — Often the most confusing line item. Data transfer between AZs, between regions, and out to the internet each have different rates. Cross-region transfer is the most expensive and the most commonly accidental.
- NAT Gateway — Charges per hour plus per GB processed. If this is a significant line item and you're in a development environment, consider whether you actually need a NAT Gateway.
Services You Might Not Recognize
The service names in the billing dashboard don't always match what you'd expect. "Amazon Elastic Compute Cloud - Compute" is EC2 instances. "EC2 - Other" includes EBS, data transfer, and Elastic IPs. "AWS Key Management Service" is KMS — if you're using encrypted EBS volumes or S3 buckets, you're paying for KMS requests even if you never configured it directly.
If you see a service you've never heard of, don't panic. Click into it to see the line items. It might be a service that another service is using on your behalf (like KMS for encryption or CloudWatch for logging).
Cost Explorer vs. Billing Dashboard
The Billing Dashboard shows your current month's summary. Cost Explorer shows historical data with filtering, grouping, and comparison capabilities. If you want to understand trends, compare months, or drill into specific services/regions/tags, use Cost Explorer. The Billing Dashboard is your quick glance; Cost Explorer is your analysis tool.
The Numbers That Aren't on the Dashboard
The Billing Dashboard shows you what you've spent. What it doesn't show: whether your spending is normal (you need Cost Anomaly Detection for that), whether your spending correlates with security events (you need to cross-reference with GuardDuty), how your spending compares to your budget (you need AWS Budgets for that), and whether your account is healthy overall (you need to check billing + security + compliance + SES reputation together).
Vigilare puts all of these signals in a single dashboard with a risk score that tells you whether your account needs attention. If you want more than a spending summary — if you want to know whether your account is healthy — start a free 14-day trial.
Related Reading
Protect your AWS accounts before it's too late
Vigilare monitors your AWS accounts for suspension risks — billing anomalies, IAM issues, GuardDuty findings, and more — and alerts you before AWS takes action.
Written by Viktor B.
Co-founder & CEO