Cargando...
Cargando...
Visualize, analyze, and forecast your AWS spending with historical data and ML-powered predictions
AWS Cost Explorer is a fully managed cost visualization and analysis tool that lets you explore, understand, and manage your AWS costs and usage over time — including up to 12 months of historical data and 12-month forecasts. It provides pre-built reports, customizable filters, grouping by dimensions (service, account, tag, region), and an API for programmatic access. Unlike monitoring tools, Cost Explorer is purpose-built for financial analysis, not operational health or performance.
To give AWS customers granular visibility into historical and projected cloud spend, enabling data-driven cost optimization decisions across accounts, services, and teams.
Use When
Avoid When
Pre-built cost and usage reports
Includes reports for Monthly costs by service, Daily costs, Reserved Instance utilization, Savings Plans utilization, and more
Custom report creation with filters and groupings
Filter by service, account, region, availability zone, instance type, purchase option, tag, and more
ML-powered cost forecasting
Uses machine learning on historical data to predict future spend; requires at least 1 month of history
Reserved Instance (RI) purchase recommendations
Recommends RI purchases based on your on-demand usage patterns to maximize savings
Savings Plans purchase recommendations
Recommends Compute Savings Plans, EC2 Instance Savings Plans, and SageMaker Savings Plans
RI and Savings Plans utilization and coverage reports
Track how well your existing RIs and Savings Plans are being used — critical for avoiding waste
EC2 rightsizing recommendations
Identifies over-provisioned EC2 instances; based on 14 days of CloudWatch CPU/memory metrics
Cost allocation tags support
Filter and group costs by user-defined or AWS-generated tags after activation in Billing console
Programmatic API access
Cost Explorer API allows querying cost and usage data, forecasts, and recommendations programmatically
Hourly granularity (API only, last 14 days)
Available only via API, not the console, and only for the most recent 14 days
Multi-account (AWS Organizations) support
Management account can view consolidated costs or drill into individual linked accounts
Anomaly Detection
AWS Cost Anomaly Detection (a related service) uses ML to detect unusual spend — integrates with Cost Explorer console
Real-time cost alerting
Use AWS Budgets for alerts — Cost Explorer data has up to 24-hour lag and has no native alert mechanism
Resource-level cost breakdown (e.g., per EC2 instance ID)
Resource-level data is available but must be enabled; uses Cost and Usage Report under the hood for resource IDs
Cost Visibility + Proactive Alerting
high freqCost Explorer provides historical analysis and forecasting; AWS Budgets provides threshold-based alerts and actions. Use Cost Explorer to understand spend patterns, then set Budgets alerts to notify when forecasted or actual spend exceeds thresholds. These are complementary, not competing — Budgets alerts, Cost Explorer analyzes.
Consolidated Billing Cost Analysis
high freqThe management account in an AWS Organization can use Cost Explorer to view costs across all member accounts, filter by linked account, and generate chargeback reports. Cost allocation tags applied across accounts are visible in a unified view. Member accounts can also view their own costs if given access.
Cost Reduction via Right-Sizing
high freqCost Explorer provides basic EC2 rightsizing recommendations based on 14 days of CloudWatch data. Compute Optimizer provides deeper, ML-driven recommendations across EC2, Lambda, ECS, EBS, and Auto Scaling Groups with configurable lookback periods. For exam questions: if the scenario requires deep multi-service rightsizing, choose Compute Optimizer; if it's about RI/SP purchasing, choose Cost Explorer.
Cost Optimization Recommendations
high freqTrusted Advisor provides broad best-practice checks across cost, security, performance, fault tolerance, and service limits. Cost Explorer provides deeper financial analysis and RI/SP recommendations. Trusted Advisor's cost checks (e.g., idle EC2, unassociated EIPs) complement Cost Explorer's spending analysis. For comprehensive cost optimization, use both.
Cost Accountability + Audit Trail
medium freqCloudTrail logs API calls made to the Cost Explorer API (GetCostAndUsage, etc.), providing an audit trail of who queried cost data. CloudTrail does NOT provide cost data — it provides API activity logs. Use Cost Explorer for the financial data, CloudTrail for auditing access to that data.
Utilization Data for Rightsizing
medium freqCost Explorer's EC2 rightsizing recommendations consume CloudWatch CPU utilization metrics. Optionally, you can enable CloudWatch agent to send memory utilization data, which Cost Explorer uses for more accurate recommendations (at additional cost). CloudWatch handles operational metrics; Cost Explorer handles financial analysis.
Console Analysis vs. Programmatic Deep Dive
medium freqCost Explorer is the high-level, interactive analysis tool. CUR is the raw, line-item billing data delivered to S3. For high-volume API queries, custom dashboards in QuickSight, or Athena-based cost analytics, use CUR. Cost Explorer API is suitable for lightweight programmatic access; CUR+Athena is the scalable enterprise pattern.
ML-Powered Spend Anomaly Alerting
medium freqAWS Cost Anomaly Detection is accessible within the Cost Explorer console and uses ML to automatically detect unusual spending patterns without requiring manual threshold setting. It can send alerts via SNS or email. This is distinct from AWS Budgets alerts which require manual threshold configuration.
Cost Explorer is for ANALYSIS (historical + forecast), NOT for real-time alerting. When an exam question asks 'how do you get notified when costs exceed a threshold,' the answer is AWS Budgets — not Cost Explorer.
Cost Explorer must be MANUALLY ENABLED by the management account — it is NOT enabled by default. After enabling, data takes up to 24 hours to appear. This is a common scenario question trap: 'why can't the team see cost data?' — because Cost Explorer was never enabled.
Know the three layers of granularity: Monthly (console + API, 12 months), Daily (console + API, 12 months), Hourly (API ONLY, last 14 days). Exam questions about 'hourly cost breakdown for the past 6 months' cannot be answered with Cost Explorer — use CUR.
Cost Explorer vs Compute Optimizer for rightsizing: Cost Explorer = basic EC2 rightsizing + RI/SP purchasing recommendations. Compute Optimizer = deep ML rightsizing for EC2, Lambda, ECS, EBS, Auto Scaling Groups. If the question involves non-EC2 services or requires workload-performance-based recommendations, choose Compute Optimizer.
Cost Explorer = ANALYZE (history, forecasts, RI/SP recommendations). AWS Budgets = ALERT (threshold notifications, automated actions). Never substitute one for the other on exam questions.
Cost Explorer must be manually ENABLED by the management account — it is NOT on by default. Tags must be ACTIVATED in the Billing console before appearing in Cost Explorer — two separate activation steps that candidates routinely miss.
For rightsizing: Cost Explorer = basic EC2 only, 14-day lookback. Compute Optimizer = advanced ML, multi-service (EC2/Lambda/ECS/EBS/ASG), configurable lookback. Match the service to the scope of the requirement.
Cost allocation tags must be ACTIVATED in the AWS Billing and Cost Management console BEFORE they appear as filterable dimensions in Cost Explorer. Tags applied to resources but not activated will NOT show up. Activation can take up to 24 hours to propagate.
In AWS Organizations, the MANAGEMENT ACCOUNT enables Cost Explorer for the entire organization. Member accounts can view their own costs but cannot see other accounts' costs unless given explicit IAM permissions. The management account sees the consolidated view.
Cost Explorer API charges per request — for high-volume, automated cost reporting pipelines (e.g., daily reports for 100+ accounts), the recommended architecture is CUR delivered to S3 + AWS Glue + Amazon Athena + Amazon QuickSight, NOT repeated Cost Explorer API calls.
Cost Anomaly Detection (accessible via Cost Explorer console) uses ML and does NOT require you to set manual thresholds — this distinguishes it from AWS Budgets. If a question asks about 'automatically detecting unexpected cost spikes without defining thresholds,' the answer is Cost Anomaly Detection.
RI Utilization vs RI Coverage are two different reports in Cost Explorer: Utilization = what % of your purchased RIs are being used (are you wasting money on unused RIs?). Coverage = what % of your eligible usage is covered by RIs (should you buy more?). Know both for exam questions about RI optimization.
Cost Explorer data has up to a 24-hour delay — it is NOT real-time. If an exam scenario says 'a developer just launched 1000 EC2 instances and you need to see the cost impact immediately,' Cost Explorer cannot help in real-time. This is a distractor pattern.
Common Mistake
AWS CloudWatch can be used to analyze and report on AWS costs and billing trends
Correct
CloudWatch monitors operational metrics (CPU, memory, latency, error rates) — it has NO cost analysis capability. Cost Explorer is the correct service for financial analysis. CloudWatch can create a billing alarm (a single threshold alert), but it cannot analyze spending trends, forecast costs, or provide RI recommendations.
This is the #1 misconception on cost management questions. The trap is that CloudWatch is so broadly used that candidates assume it covers billing too. Remember: CloudWatch = Operations, Cost Explorer = Finance. The only billing-related CloudWatch feature is a basic billing alarm, which is far less capable than AWS Budgets.
Common Mistake
AWS Config provides cost insights and can identify which resources are driving high costs
Correct
AWS Config tracks resource CONFIGURATION history and compliance rules — it records what a resource looks like (instance type, security group rules, etc.) but has NO knowledge of cost or spending. Cost Explorer is the correct tool for identifying cost drivers. Config and Cost Explorer can be complementary (Config shows what changed, Cost Explorer shows what it cost), but they are entirely separate services.
Exam questions often present Config as an answer choice for cost-related scenarios because it does track resource changes. Candidates confuse 'knowing what resources exist and changed' with 'knowing what they cost.' Config = Configuration compliance. Cost Explorer = Financial analysis.
Common Mistake
AWS Cost Explorer and AWS Budgets are interchangeable — both alert you when you're overspending
Correct
Cost Explorer is an ANALYSIS tool — it shows you historical data, forecasts, and recommendations but does NOT send alerts. AWS Budgets is an ALERTING tool — it notifies you (via SNS/email) when actual or forecasted spend crosses a threshold you define, and can trigger automated actions (e.g., apply an IAM policy to restrict spending). Use Cost Explorer to understand your costs; use Budgets to act on them.
This distinction appears in nearly every cost management scenario question. The key test: 'Does the requirement involve NOTIFICATION or AUTOMATED ACTION?' → AWS Budgets. 'Does it involve UNDERSTANDING or ANALYZING spend?' → Cost Explorer. They are designed to work together, not replace each other.
Common Mistake
AWS Trusted Advisor and AWS Cost Explorer both provide the same cost optimization recommendations
Correct
Trusted Advisor provides BROAD best-practice checks across 5 pillars (cost, security, performance, fault tolerance, service limits) with relatively simple heuristics (e.g., 'this EC2 instance has <10% CPU for 14 days'). Cost Explorer provides DEEP financial analysis including RI/Savings Plans purchase recommendations, utilization/coverage reports, and spend forecasting. Trusted Advisor is a checklist; Cost Explorer is a financial analytics platform.
Both appear in cost optimization questions and both can recommend 'buy Reserved Instances,' causing confusion. Remember: Trusted Advisor = broad health check across all pillars. Cost Explorer = deep financial analysis and purchasing optimization. For detailed RI/SP recommendations with dollar amounts, Cost Explorer is the answer.
Common Mistake
Cost Explorer provides rightsizing recommendations equivalent to AWS Compute Optimizer
Correct
Cost Explorer's rightsizing recommendations are BASIC — they cover EC2 only, use 14 days of CloudWatch data, and focus on identifying over-provisioned instances. AWS Compute Optimizer is ADVANCED — it covers EC2, Lambda, ECS on Fargate, EBS volumes, and Auto Scaling Groups; uses ML with configurable lookback (14 days to 3 months with enhanced metrics); and provides specific instance type recommendations with performance risk scores. For comprehensive, multi-service rightsizing, always choose Compute Optimizer.
Exam questions will describe a scenario needing 'rightsizing recommendations' and offer both as choices. The differentiator is SCOPE: if it's EC2-only and simple, Cost Explorer works. If it involves Lambda, ECS, EBS, or requires performance-risk analysis, Compute Optimizer is correct.
Common Mistake
After enabling cost allocation tags on resources, they immediately appear as filter dimensions in Cost Explorer
Correct
Cost allocation tags require a TWO-STEP process: (1) Apply tags to AWS resources, AND (2) ACTIVATE those tags in the AWS Billing and Cost Management console. Only after activation (which can take up to 24 hours) do tags appear as filterable dimensions in Cost Explorer. Tags applied to resources but never activated in Billing are invisible to Cost Explorer.
This is a subtle but frequently tested gotcha. Candidates assume tagging resources is sufficient. The activation step in the Billing console is mandatory and non-obvious. This is why a newly tagged environment 'can't see cost by team/project in Cost Explorer' — the tags were never activated.
Common Mistake
AWS CloudTrail can be used to monitor and analyze AWS service performance and costs
Correct
CloudTrail records API ACTIVITY (who called what API, when, from where) — it is an audit and governance tool, not a performance or cost tool. It cannot tell you how much a service costs or how it's performing. For costs → Cost Explorer. For performance → CloudWatch. For API audit → CloudTrail. These are three completely distinct services with distinct purposes.
This misconception appears specifically in questions about 'monitoring' where CloudTrail is presented as a distractor. The word 'monitoring' is ambiguous — CloudTrail monitors API activity, CloudWatch monitors operational metrics, Cost Explorer monitors financial trends. Knowing which 'monitoring' maps to which service is essential.
CEA = Cost Explorer Analyzes (history + forecasts). Budgets = Budgets Alert (notifications + actions). Never flip these.
The 3 C's of Cost Management: Cost Explorer (Comprehend your spending) → Cost Anomaly Detection (Catch surprises) → Cost Budgets (Control with alerts). In that order: understand, detect, act.
ACTIVATE before you ANALYZE: Tags on resources ≠ Tags in Cost Explorer. You must Activate tags in Billing before they Appear in Analysis.
Compute Optimizer = COMPUTE performance optimization (EC2, Lambda, ECS, EBS, ASG). Cost Explorer = COST purchasing optimization (RI, SP recommendations). One optimizes HOW you run, the other optimizes HOW you pay.
Cost Explorer is like a bank statement — it shows you what happened (12 months back) and predicts what's coming (12 months forward), but it doesn't stop you from overspending. AWS Budgets is like a credit card alert — it warns you when you're about to exceed your limit.
CertAI Tutor · SAA-C03, SAP-C02, DEA-C01, AIF-C01, CLF-C02 · 2026-02-22