Cost Explorer shows where your AWS money went and forecasts it. Trusted Advisor runs best-practice checks, including cost ones, against your account. Compute Optimizer recommends rightsizing for specific compute and storage resources. They answer different questions, so they complement each other. Alone, none gives you ownership, workflow or multi-cloud coverage.
AWS Trusted Advisor vs Cost Explorer: what is the difference?
The short version: Cost Explorer is a reporting tool, Trusted Advisor is a checklist tool, and Compute Optimizer is a recommendation engine for specific resource types. People compare Cost Explorer and Trusted Advisor because both appear under "cost" in the console, but they do not overlap much.
- Cost Explorer reads your billing data. You filter and group by service, account, region, tag or usage type, view trends, and get a forecast. It also has built-in recommendations for Savings Plans and Reserved Instance purchases, and a rightsizing view for EC2.
- Trusted Advisor inspects your resources and configuration against checks in five areas: cost optimization, performance, security, fault tolerance and service limits (the category set has evolved, so check current docs). On the cost side it flags things like idle or low-utilization resources and unused or unassociated resources.
- Compute Optimizer analyzes utilization metrics (CloudWatch, and optionally memory metrics if you configure them) and suggests better-sized options for EC2 instances, Auto Scaling groups, EBS volumes, Lambda functions and some other resource types. Coverage expands over time, so verify the current list.
Think of it this way: Cost Explorer tells you that EC2 grew 22% last month. Compute Optimizer tells you which instances are oversized. Trusted Advisor tells you that an idle load balancer exists. Nothing in the three tells you which team should fix it by Friday.
Which Trusted Advisor checks need Business or Enterprise Support?
Hedge this one: AWS has changed Trusted Advisor's packaging more than once, so confirm against the current AWS documentation before you plan around it.
Historically, accounts on Basic or Developer support get a limited set of core checks (a small group of security checks and service limit checks). The full set of checks, including most of the cost optimization checks, the Trusted Advisor API and Trusted Advisor notifications, has been tied to Business, Enterprise On-Ramp or Enterprise Support plans. More recently AWS has been shifting to the newer support plan tiers and adding Trusted Advisor features such as a priority view and organizational view for paid tiers, so the exact boundary may differ by the time you read this.
The practical implication: if you rely on Trusted Advisor for cost findings, check what your support plan actually unlocks. A company on a lower plan may be looking at a mostly empty cost tab and assuming nothing is wrong. Conversely, upgrading support solely to get these checks rarely pays for itself unless you were going to buy the plan anyway for response times and architectural guidance. Support plans are priced as a percentage of AWS spend with minimums (check current pricing), so at several million dollars a year this is a real line item.
Do I also need Compute Optimizer, Cost Anomaly Detection, Budgets and the CUR?
Cost Explorer and Trusted Advisor are only part of the native toolbox. A fuller picture:
| Tool | What it does | Cost to use | Main limitation |
|---|---|---|---|
| Cost Explorer | Spend analysis, trends, forecast, Savings Plans and RI recommendations | Console use is free; API requests are charged per request (check current pricing) | Reporting only; relies on tags and account structure for allocation |
| Trusted Advisor | Best-practice checks across cost, security, performance and more | Limited checks free; full checks with Business-tier or higher support (verify) | Narrow set of cost checks; no owner routing or savings tracking |
| Compute Optimizer | Rightsizing for EC2, ASG, EBS, Lambda and other supported types | Basic features free; enhanced options such as longer lookback are paid (verify) | Only supported resource types; recommendations, not execution |
| Cost Anomaly Detection | Detects unusual spend with ML and sends alerts | Free to use | Alerts on spend changes, not on the cause; tuning monitors takes thought |
| AWS Budgets | Budget thresholds, forecasts and alerts; optional budget actions | Some budgets free, action-enabled budgets may be charged (verify) | A threshold, not a diagnosis |
| CUR / Data Exports | Most detailed billing data, line item per usage record | Export itself is free; you pay for S3 storage and the query engine | Raw data; you need Athena, a BI tool or a platform to make it useful |
Three notes on that table:
Cost Anomaly Detection is worth turning on at any size. It is free and catches the runaway job, the misconfigured NAT gateway or the forgotten GPU cluster. Route the alerts to a channel someone reads. Our write-up The $32 Gateway to Nowhere is a small example of the kind of leak these alerts exist to catch.
Budgets are guardrails. Set one per account or team with alerts at, say, 80% and 100% of forecast. They do not tell you why you are over.
CUR and Data Exports are where serious analysis starts. The Cost and Usage Report (and the newer Data Exports options, including a FOCUS-format export; see FOCUS 1.2 explained) is the source of truth for chargeback, unit costs and anything Cost Explorer cannot slice. Setting it up is a few clicks. Making it useful takes SQL skills or a tool that ingests it.
Is AWS Cost Explorer enough for a company with $3M annual cloud spend?
Usually not by itself, but it depends on what "enough" means and how your estate looks.
At $3M a year you are spending about $250K a month. If waste in an environment without structured review is somewhere in the 20-30% range (a typical range in our experience, not a measurement of your account), that is $50K-$75K a month, or $600K-$900K annually, in potential savings. For illustration: $250K x 20% = $50K; $250K x 30% = $75K. Even if you realize only a third, that exceeds the cost of a dedicated owner.
Here is what native tools do and do not cover at this size:
- They do well: trend analysis, top-line forecasting, Savings Plan and RI recommendations, EC2 and EBS rightsizing, anomaly alerts, budget guardrails.
- They do less well: the long tail across 100+ services (idle NAT gateways, orphaned snapshots, oversized managed databases, forgotten data transfer), cross-account prioritization, owner assignment, tracking whether a saving actually materialized, and anything beyond AWS if you also run Azure or GCP.
- They do not do: change management. Someone must open tickets, chase teams and verify the result.
If your estate is simple (a handful of accounts, one cloud, good tagging, an engineer who owns the process), native tools plus discipline can be enough, and you should push them hard before buying anything. If you have many accounts, weak tagging, several clouds or nobody with time to triage recommendations, the gap is operational more than technical. We cover the structural gaps in Cloud Native Tools vs Independent FinOps.
What should I use at each spend level?
A decision table. Spend bands are indicative and the right answer depends more on complexity than on dollars.
| Annual AWS spend | Suggested stack | Who owns it |
|---|---|---|
| Under $250K | Cost Explorer, Budgets, Cost Anomaly Detection, tags; Compute Optimizer for sizing | A part-time engineer, reviewed monthly |
| $250K - $1M | Add Compute Optimizer routinely, CUR in Athena or a dashboard, commitment review twice a year, Trusted Advisor if your support plan includes it | A named owner with a monthly review; finance involved |
| $1M - $5M | All native tools plus a structured FinOps cadence; evaluate a scanning or FinOps platform and run a proof of value against your native findings | A FinOps lead or a part-time lead plus engineering champions |
| $5M+ or multi-cloud | Native tools as the data layer, plus a dedicated platform for cross-account, cross-cloud allocation and workflow | A FinOps team with executive sponsor |
What is the easiest cloud optimization tool to deploy with no coding?
If you want zero setup, the easiest are the native ones already in your account: Cost Explorer, Budgets, Cost Anomaly Detection and Compute Optimizer. Enabling them involves clicks, not code. Trusted Advisor is also no-code once your support plan supports the checks.
For something beyond native, look for tools that connect through a read-only IAM role (a role you create via a CloudFormation template or a few console steps) and begin producing findings from billing and configuration data without agents or application changes. That includes a number of FinOps platforms. Our own Fintropy is delivered this way, and is listed on the Microsoft Marketplace with Core at $128 per month and Growth at $372 per month, each with a 15-day free trial; check the pricing page for current details. When evaluating any option, ask what permissions it needs, whether it writes anything to your account, and how long until real findings appear.
"No coding" does not mean "no work." Someone still has to review findings and get them implemented.
When are native AWS tools alone enough?
Native tools are usually enough when all of these hold:
- Spend is modest, or concentrated in a few well-understood services.
- You run one cloud and a small number of accounts.
- Tagging is good and teams own their costs.
- A person actually reviews the recommendations on a schedule.
- Your commitment coverage is already high and reviewed.
They stop being enough when recommendations pile up unactioned, when finance cannot get allocation they trust, when you add a second cloud, or when you need proof of realized savings. And remember the honest limit of this article: AWS changes these services frequently, so verify features, limits and support-plan requirements in current documentation.
Where Nuvika fits
Nuvika Technologies helps enterprises go beyond native tooling with a three-week fixed-fee assessment and a 90-day roadmap, backed by Fintropy's 497 scan rules across AWS, Azure and GCP. See our AWS cost optimization consulting page for how that works. We are probably not the right fit if you are below the spend where an outside assessment pays back, or if a single engineer using Cost Explorer, Compute Optimizer and Anomaly Detection is already closing the recommendations you have.
FAQ
What is the difference between AWS Trusted Advisor and Cost Explorer?
Cost Explorer analyzes and forecasts your billing data, while Trusted Advisor checks your resources and configuration against best practices, including some cost checks like idle resources. One tells you where money went; the other flags specific things that look wasteful or risky.
Which AWS Trusted Advisor checks require Business or Enterprise Support?
Historically most cost optimization checks, the Trusted Advisor API and notifications required Business, Enterprise On-Ramp or Enterprise Support, while lower tiers got a limited core set. AWS has been changing support plans, so confirm against current AWS documentation.
Is AWS Cost Explorer enough for a company with $3M annual cloud spend?
Often not on its own. It handles visibility, forecasts and basic recommendations well, but at $3M a year the long tail of waste, owner assignment and savings tracking need extra process or tooling. A simple, well-tagged, single-cloud estate with an engaged owner may manage with native tools.
What is the easiest cloud optimization tool to deploy with no coding?
The native AWS tools (Cost Explorer, Budgets, Cost Anomaly Detection, Compute Optimizer) are the easiest because they need only console configuration. Third-party platforms that connect through a read-only role are also no-code, but you still need someone to act on the findings.
Does Compute Optimizer replace Trusted Advisor?
No. Compute Optimizer focuses on rightsizing supported resource types using utilization metrics, while Trusted Advisor runs a broader set of checks across cost, security and reliability. Use both if your support plan allows.
Is AWS Cost Anomaly Detection free?
AWS has offered Cost Anomaly Detection as a free service, with alerts delivered through email or SNS. Verify current terms, and note that any downstream services you use for notifications may have their own costs.