You can use the AWS Billing and Cost Management console to make a quick first-pass audit of development and test spend without buying a FinOps tool. In about 20 minutes, compare equivalent periods, identify the largest service and Region changes, and isolate costs using existing cost allocation tags or categories. The time is a practical review target, not a guarantee: first-time setup, delayed data, missing tags, multiple accounts, or deeper service investigations can take longer.
What you can—and can’t—establish in 20 minutes
The console’s Cost Explorer interface is free to use. AWS charges $0.01 for each paginated Cost Explorer API request, so this walkthrough stays in the console. Cost Explorer can show up to 13 months of historical cost and usage data and up to 18 months of forecasted costs; forecasts are not a substitute for actual charges. See AWS Cost Explorer documentation.
As an Amazon Associate I earn from qualifying purchases.
A fast review can identify likely drivers and follow-up actions. It cannot guarantee a complete dev/test total if environments share accounts or resources, tags are absent or incomplete, or charges cannot be allocated. Treat any inferred split as an estimate, and distinguish it from a total explicitly attributed by an existing billing dimension.
Minutes 0–3: Set a comparable baseline
-
Open AWS Billing and Cost Management and review the home page’s month-to-date cost against the same elapsed dates in the previous month. The home page provides month-to-date and same-period comparisons, top trends, and breakdowns by service and Region. AWS describes these figures as estimates. See Using the AWS Billing and Cost Management home page.
-
Record the date range, account or account set, and metric you are comparing. Keep these consistent in every later comparison; use the same service/Region grouping and the same filters, including tag or category filters.
-
Use the Bills page if you need to reconcile the invoice total. The dashboard is for analysis, not an invoice ledger: its summaries can treat credits, refunds, taxes, timing, grouping, and rounding differently from Bills or invoices. Some dashboard cost-summary metrics exclude credits and refunds.
Cost Explorer’s current-month data is typically available about 24 hours after initial setup. It refreshes at least once every 24 hours, but upstream billing data can delay updates; other historical data may take a few days longer to prepare. If the numbers look unexpectedly low or stale, note the timestamp and revisit rather than treating a partial view as final. See AWS Cost Explorer documentation.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesMinutes 3–8: Find the biggest services, Regions, and accounts
-
In the Billing home page breakdown or Cost Explorer, inspect spend by service and AWS Region. Note the largest costs and the strongest changes versus the same elapsed dates last month.
-
If you manage an AWS Organization, inspect the member-account breakdown as well. A separate development or test account can provide a clearer boundary than tags; shared or production accounts require more cautious attribution.
-
Follow a notable trend into Cost Explorer and keep the date range and cost metric consistent with your baseline. Record which service, Region, and account explain the change before investigating individual resources.
Minutes 8–13: Isolate dev and test cautiously
Use existing cost allocation tags or categories
Filter by an activated environment tag or cost category, if one already exists. Tags for environment, application, or owner can help, but resource tags do not automatically become billing dimensions: cost allocation tags must be activated separately to appear in Cost Explorer or cost allocation reports. After activation, tags can take up to 24 hours to appear in the billing console. See AWS guidance on cost allocation tags.
A new tag is not a way to cleanly relabel the entire historical billing period. A tag added partway through a period does not establish a reliable retroactive split for the earlier untagged usage.
Account for costs that remain unallocated
Even with tags, some costs may not land in an environment total. Resources may have been untagged for part of the period; some services do not support tagging; subscription fees such as AWS Support or monthly AWS Marketplace fees cannot be allocated; and some one-time charges, including certain Reserved Instance upfront charges, cannot be allocated. AWS describes these limits in its monthly cost allocation report guidance.
When no reliable environment dimension exists
Use account, service, and Region patterns as clues, but label the result an estimate rather than an exact dev/test total. Report what is directly visible, call out unallocated spend, and identify tagging or account boundaries that owners can improve for future periods.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Minutes 13–17: Investigate the highest-cost or fastest-growing service
-
Open the largest or fastest-growing service in the cost view and identify the resource or usage category that needs investigation. The cost trend tells you where to look; it does not establish that an individual resource is safe to stop.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
For EC2, review Cost Explorer rightsizing recommendations. AWS says these analyze EC2 usage and can identify instances that may be candidates for downsizing or termination. See Optimizing your cost with rightsizing recommendations.
Best Value
-
If available, check Cost Optimization Hub for recommendations that can include unused-resource deletion and rightsizing of over-provisioned resources. Treat recommendations as investigation leads: confirm ownership, deployment schedules, and workload requirements with service owners before changing anything.
Minutes 17–20: Record the review and assign follow-ups
Capture a compact audit note so someone else can understand what the numbers mean:
- Period and comparison: the elapsed date range and prior-period dates.
- Scope: linked account or accounts, filters, and cost metric used.
- Drivers: largest services, Regions, accounts, and notable changes.
- Attribution confidence: whether the dev/test amount comes from an activated tag or category, a dedicated account, or an estimate based on patterns; include known unallocated spend.
- Follow-ups: one or two owner-confirmed investigations, with the resource or usage category to check.
Do not stop or delete a resource solely because a chart or recommendation suggests it is idle. AWS Well-Architected’s Cost Optimization guidance says: “To encourage accountability of cloud spend, grant users access to tools that provide visibility into their costs and usage.” Cost Explorer, AWS Budgets, Cost Anomaly Detection, and Cost Optimization Hub are examples of AWS-native tools for ongoing visibility and review, not prerequisites for this quick audit. See COST03-BP05: Configure billing and cost management tools.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
