iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can use the AWS Billing and Cost Management console to make a quick first-pass review of development and test spend without buying a FinOps tool. The 20-minute outline below helps you spot the largest services, regions, and account-level changes, then check whether existing tags can identify dev/test costs. It is a review of billing data already available—not a guarantee that every charge can be attributed or safely reduced in 20 minutes.
What you can learn in a quick AWS dev/test spend review
The aim is to find the biggest cost drivers and decide what deserves follow-up—not to produce an invoice reconciliation or a perfect environment allocation. The AWS Billing and Cost Management home page uses Cost Explorer data and can show month-to-date estimates, same-period comparisons, top trends, and breakdowns by service and Region. For AWS Organizations management accounts, it can also show member-account breakdowns.
The Cost Explorer console 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. These are tool limits, not estimates of likely savings. AWS Cost Explorer documentation
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Minutes 0–3: Establish a comparable baseline
- Open AWS Billing and Cost Management. Review the home page’s current-month estimated cost and comparison with the same elapsed period last month.
- Keep the comparison consistent. Compare the same dates, account or account set, cost metric, and treatment of credits and refunds. A month-to-date total compared with all of the previous month can make ordinary timing look like a cost change.
- Record the period and account scope. Note the date range and whether you are looking at one account or an Organizations account set.
The home page is an analysis view, not the invoice ledger. Some cost-summary metrics exclude credits and refunds, and its figures can differ from Bills or an invoice because of grouping, the display of credits, refunds and taxes, estimated current-month timing, and rounding. For invoice reconciliation, open the Bills page. AWS guidance on the Billing and Cost Management home page
#1 Best Overall
Minutes 3–8: Find the largest services, Regions, and accounts
- Inspect the service breakdown. Identify the few largest services and any notable month-over-month changes.
- Check the Region breakdown. Look for costs concentrated in a Region or changes that could point to a specific workload or deployment.
- If you manage an organization, inspect member accounts. A separate account may make dev/test spend easier to distinguish, but confirm the account’s purpose before treating all of its charges as development or test costs.
- Follow notable trends into Cost Explorer. Use the same date range and grouping as your baseline so that you are investigating the same comparison rather than a different slice of spend.
The Billing home page provides breakdowns by service, AWS Region, member account for Organizations management accounts, cost allocation tag, and cost category. Its top trends can point you toward a change to investigate; they do not establish the cause of that change. AWS guidance on the Billing and Cost Management home page
Minutes 8–13: Separate dev/test costs where the data allows
Use existing environment tags or cost categories
In the Billing home page breakdown or Cost Explorer, filter or group by an existing environment cost allocation tag or cost category. Check that the selected values actually correspond to development and test workloads, rather than assuming a tag name proves ownership or purpose.
Rank #2
Resource tags are not automatically available as billing dimensions. Cost allocation tags must be activated before they appear in Cost Explorer or cost allocation reports, and AWS says they can take up to 24 hours to appear in the billing console. Adding a tag now will not create a clean historical split for charges incurred before it was applied. AWS guidance on cost allocation tags
When tags are missing or incomplete
If there is no usable environment dimension, use account, service, and Region patterns as clues, not proof. Report those known facts and label any inferred dev/test total as an estimate. Do not present a partial tag allocation as if it were the total for all accounts.
Rank #3
Some charges can remain unallocated even when tags are used. Examples include periods when resources were not tagged, services that do not support tagging, subscription fees such as AWS Support or Marketplace monthly fees, and some one-time fees such as Reserved Instance upfront charges. AWS guidance on the monthly cost allocation report
Minutes 13–17: Investigate the biggest or fastest-growing services
- Choose one or two items to investigate. Start with a large service or a service whose cost rose most in the comparable period.
- Inspect its resource or usage category. Use the available service detail to identify what kind of usage should be checked and who may own it.
- For EC2, review rightsizing recommendations. Cost Explorer recommendations analyze EC2 usage and can identify instances that may be candidates for downsizing or termination. AWS guidance on EC2 rightsizing recommendations
- Review Cost Optimization Hub if available. Recommendations can include unused-resource and rightsizing opportunities. Treat them as leads to validate, not instructions to act immediately. AWS guidance on the Billing and Cost Management home page
Before changing or removing a resource, confirm its owner, deployment schedule, and workload requirements. A cost chart or recommendation alone does not establish that a resource is idle or safe to stop.
Rank #4
Minutes 17–20: Record useful follow-ups
Capture the details needed for another person to verify the finding:
Recommended Free Tools
- The date range, account or account set, and cost metric used.
- The service, Region, account, tag, or cost category filters applied.
- The largest cost drivers and the changes worth investigating.
- How confident you are that the charges belong to dev/test, including any unallocated or inferred portion.
- One or two owner-confirmed follow-ups, with an owner and next action.
For example, a useful follow-up is to ask the owner of a rising EC2 cost to confirm which instances support scheduled tests and whether the rightsizing recommendation fits their workload. Do not stop or delete resources solely because a billing view suggests they may be idle.
Best Value
Why your result may be incomplete or delayed
Cost Explorer refreshes data at least once every 24 hours, subject to delays in upstream billing data. After initial setup, current-month data is typically available in about 24 hours; preparing other historical data can take a few days longer. The Billing home page data may also take up to 24 hours to appear. A quick review therefore works best when Cost Explorer is already set up and the relevant billing data has arrived. AWS Cost Explorer documentation AWS Billing home page guidance
First-time setup, delayed data, multiple accounts, missing tags, or service-by-service investigation can extend the review. AWS Well-Architected recommends giving users access to tools that make cost and usage visible; AWS-native follow-up controls include Cost Explorer, AWS Budgets, Cost Anomaly Detection, and Cost Optimization Hub. These can support ongoing monitoring, but they are not prerequisites for this first-pass review. AWS Well-Architected Cost Optimization guidance
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.
Free tools Windows power users keep installed
One-click scans. No signup required.

