AWS Cost Explorer: Complete Guide to Cloud Cost Analysis
AWS Cost Explorer is the first tool most teams reach for when cloud bills start growing faster than expected. According to AWS, Cost Explorer processes billions of billing line items daily across millions of customer accounts, making it the most widely used cloud cost analysis tool in the world.
This guide covers everything from initial setup to advanced analysis techniques. Whether you're tracking spending trends, investigating anomalies, or building a case for commitment purchases, Cost Explorer provides the data foundation for cloud cost optimization on AWS. Understanding its capabilities and limitations helps you extract maximum value from this free, built-in tool.
Key Takeaways
- AWS Cost Explorer is free and provides up to 12 months of historical cost data
- Rightsizing recommendations alone can identify 20-40% compute savings (AWS)
- Cost Explorer works best alongside AWS Budgets and the Cost and Usage Report
- Filtering by tag, service, and linked account enables team-level cost tracking
What Is AWS Cost Explorer?
AWS Cost Explorer is a free cost visualization and analysis tool built into the AWS Management Console. According to AWS documentation, Cost Explorer provides up to 12 months of historical cost data plus 12 months of cost forecasting, enabling both retrospective analysis and forward-looking budget planning.
[CITATION CAPSULE: AWS Cost Explorer provides 12 months of historical cost data and 12 months of forecasting at no additional cost. According to AWS, its rightsizing recommendations analyze 14 days of CloudWatch metrics to identify EC2 instances that can be downsized or terminated, targeting 20-40% compute savings.]
Core Capabilities
Cost and usage visualization: Interactive charts showing daily, monthly, or hourly cost trends. Filter by service, linked account, region, tag, instance type, or usage type for granular analysis.
Forecasting: Machine learning-based spend forecasts for the current and next month. Forecast accuracy improves with more historical data and consistent usage patterns.
Rightsizing recommendations: EC2 rightsizing suggestions based on CloudWatch CPU and memory metrics. Recommendations include estimated savings from downsizing or terminating underutilized instances.
Savings Plans and Reserved Instance recommendations: Analysis of your usage patterns to recommend optimal commitment purchases with projected savings percentages.
How Do You Set Up AWS Cost Explorer?
Cost Explorer requires minimal setup but benefits significantly from proper configuration. According to AWS cost management documentation, enabling Cost Explorer takes effect within 24 hours, and retroactive data population covers the previous 12 months of billing history.
Initial Setup Steps
Step 1: Enable Cost Explorer. Navigate to the AWS Billing console and select Cost Explorer. Click "Launch Cost Explorer." This is a one-time action for your AWS organization. Data becomes available within 24 hours.
Step 2: Activate cost allocation tags. In the Billing console, go to Cost Allocation Tags and activate the tags you want to use for cost filtering. Both AWS-generated tags and user-defined tags must be explicitly activated for Cost Explorer to recognize them.
Step 3: Enable hourly granularity (optional). By default, Cost Explorer shows daily and monthly data. Hourly data is available for the last 14 days and requires explicit enabling. It's useful for investigating short-lived spending spikes.
Step 4: Configure member account access. If you use AWS Organizations, decide which member accounts can access Cost Explorer. By default, only the management account has access. Enable member account access through the Organizations billing preferences if teams need direct visibility.
[INTERNAL-LINK: FinOps fundamentals -> /blogs/finops/]
Need expert help with aws cost explorer: complete guide to cloud cost analysis?
Our cloud architects can help you with aws cost explorer: complete guide to cloud cost analysis — from strategy to implementation. Book a free 30-minute advisory call with no obligation.
What Are the Most Useful Cost Explorer Analysis Techniques?
Cost Explorer's value comes from knowing which views to create and which filters to apply. According to AWS, the most common analysis patterns are service-level trending, tag-based team attribution, and commitment coverage analysis. Mastering these three patterns covers 80% of day-to-day cost management needs.
Service-Level Trending
Start every cost review with a service-level trend view showing the last 3-6 months. Group costs by Service and look for services with unexpected growth. EC2, RDS, S3, and data transfer typically represent 70-80% of total AWS spend. If any service grows faster than your business, investigate why.
Tag-Based Team Attribution
Filter costs by your team or cost-center tag to generate team-level spend reports. This is the foundation for showback and chargeback. If untagged costs represent more than 15% of total spend, prioritize tag compliance improvement before refining team-level analysis.
Linked Account Analysis
In multi-account environments, filter by linked account to identify which accounts are driving cost growth. This is especially useful for catching development and staging environments that have grown to production-scale costs without corresponding business justification.
Commitment Coverage Analysis
Use the Reserved Instance and Savings Plans utilization reports to evaluate your commitment strategy. Check utilization (are you using what you bought?) and coverage (are you covering your steady-state usage?). Target 90%+ utilization and 60-80% coverage for predictable workloads.
[PERSONAL EXPERIENCE] The most valuable Cost Explorer habit we've developed is a weekly "anomaly check" using the daily granularity view for the past 30 days. Set the view to show cost by service, and visually scan for any unusual spikes or step-changes. This five-minute check catches issues that automated alerting sometimes misses, particularly gradual cost increases that don't trigger percentage-based alerts.
How Do AWS Cost Explorer Rightsizing Recommendations Work?
Cost Explorer's rightsizing recommendations analyze 14 days of CloudWatch metrics to identify EC2 instances that are larger than their workload requires. According to AWS, organizations that act on rightsizing recommendations reduce EC2 spend by 20-40% on average.
[CITATION CAPSULE: AWS reports that organizations acting on Cost Explorer rightsizing recommendations reduce EC2 spend by 20-40% on average. Recommendations analyze 14 days of CloudWatch metrics including CPU utilization, network throughput, and memory usage to suggest optimal instance sizes.]
Understanding the Recommendations
Each recommendation shows the current instance type, suggested target instance type, estimated monthly savings, and the utilization data that triggered the recommendation. Recommendations fall into two categories: modify (downsize to a smaller instance) and terminate (instance shows near-zero utilization).
Be cautious with terminate recommendations. Near-zero CPU utilization doesn't always mean the instance is unused. It might serve as a bastion host, license server, or DNS resolver with minimal but critical traffic. Always verify with the owning team before terminating.
Limitations to Know
Cost Explorer rightsizing only covers EC2 instances, not RDS, ElastiCache, or other services. It uses CloudWatch basic metrics (5-minute intervals), which may miss short burst patterns. Memory utilization requires the CloudWatch agent and isn't included by default. For comprehensive rightsizing across services, consider complementary tools like AWS Compute Optimizer or third-party platforms.
What Are Cost Explorer's Limitations?
While Cost Explorer is powerful for its price (free), it has meaningful limitations that organizations should understand. According to the FinOps Foundation's tools survey, most organizations with $1M+ annual AWS spend supplement Cost Explorer with additional tools to address its gaps.
Data Granularity Limits
Hourly data is only available for the last 14 days. Resource-level cost data requires the Cost and Usage Report (CUR), which Cost Explorer's UI doesn't expose directly. For deep analysis, you'll need to export CUR data to Athena, Redshift, or a third-party platform.
No Multi-Cloud Support
Cost Explorer only covers AWS. If you run workloads on Azure, GCP, or other providers, you need a separate tool for unified cross-cloud visibility. This is the primary reason organizations invest in third-party FinOps platforms.
Limited Automation
Cost Explorer provides recommendations but doesn't automate implementation. Rightsizing, commitment purchases, and waste elimination require manual action or integration with other tools. The Cost Explorer API enables programmatic access for custom automation.
Single-Dimension Grouping
Cost Explorer allows grouping by one dimension at a time in the UI. You can view costs by service or by tag, but not by service within a tag in a single view. This limits the complexity of analysis possible without exporting data.
[UNIQUE INSIGHT] Cost Explorer's biggest limitation isn't technical. It's organizational. The tool provides data, but it doesn't drive action. Organizations that treat Cost Explorer as a reporting tool see limited impact. Those that integrate Cost Explorer analysis into regular team cadences, sprint reviews, architecture decisions, and budget planning, extract significantly more value from the same data.
How Does Cost Explorer Work with the Cost and Usage Report?
The Cost and Usage Report (CUR) complements Cost Explorer by providing line-item billing data at the resource level. According to AWS, the CUR contains the most granular cost data available, including resource IDs, usage quantities, and amortized commitment costs.
When to Use CUR Instead of Cost Explorer
Use CUR when you need resource-level cost attribution (which specific EC2 instance costs how much), custom allocation logic that goes beyond tag-based filtering, or multi-dimensional analysis combining several attributes simultaneously.
CUR data can be exported to S3 and queried with Athena for SQL-based analysis. This enables custom dashboards in QuickSight, Grafana, or other BI tools. The combination of CUR + Athena + QuickSight provides enterprise-grade cost analytics without third-party tools.
Complementary AWS Cost Tools
AWS Budgets: Proactive alerting and automated actions based on spending thresholds.
AWS Compute Optimizer: Broader rightsizing recommendations covering EC2, EBS, Lambda, and ECS.
AWS Cost Anomaly Detection: ML-powered anomaly detection with automated alerting.
AWS Trusted Advisor: Cost optimization checks alongside security and performance recommendations.
Frequently Asked Questions
Is AWS Cost Explorer really free?
Yes. AWS Cost Explorer is included at no additional charge with every AWS account. The only cost-related feature that incurs charges is the Cost Explorer API, which costs $0.01 per paginated API request. The web-based UI, including all visualizations and recommendations, is completely free.
How far back does Cost Explorer data go?
Cost Explorer provides up to 12 months of historical data at daily or monthly granularity. Hourly data is available for the last 14 days. For longer historical analysis, configure the Cost and Usage Report to export data to S3, where you can retain it indefinitely.
Can Cost Explorer show costs for individual resources?
Cost Explorer shows costs grouped by dimensions like service, tag, account, and region, but doesn't show individual resource-level costs in the UI. For resource-level data, use the Cost and Usage Report (CUR), which includes resource IDs for most AWS services.
How accurate are Cost Explorer's forecasts?
Forecast accuracy depends on the consistency of your usage patterns. For steady-state workloads, forecasts are typically within 5-10% of actual spend. For workloads with significant variability (seasonal spikes, new product launches), forecasts may be less accurate. Cost Explorer improves forecast accuracy as it accumulates more historical data.
Getting the Most from AWS Cost Explorer
AWS Cost Explorer is a capable, free tool that should be the starting point for every AWS cost management practice. Master the core analysis techniques: service trending, tag-based attribution, and commitment coverage. Use rightsizing recommendations to capture quick wins. And understand its limitations so you know when to supplement with CUR, Compute Optimizer, or third-party platforms.
The key to success with Cost Explorer isn't the tool itself. It's building the habit of regular analysis and the organizational processes to act on what you find. A five-minute weekly anomaly check is worth more than a comprehensive monthly report that nobody reads.
For organizations looking to build comprehensive AWS cost management beyond what native tools provide, cloud cost optimization services can help design analysis workflows, implement advanced reporting, and drive optimization actions.
Related Services
About the Author
Creative Lead at Opsio
Brand strategy, UX design, and creative direction for cloud technology
Editorial standards: This article was written by a certified practitioner and peer-reviewed by our engineering team. We update content quarterly to ensure technical accuracy. Opsio maintains editorial independence — we recommend solutions based on technical merit, not commercial relationships.