AWS Cost Explorer Reviews

My primary use case for AWS Cost Explorer is cost visibility and optimization, and I use it to understand where cloud spend is occurring, identify spending trends, analyze cost drivers, evaluate commitment coverage, and support decision making around Savings Plans, Reserved Instances, and workload optimization. A recent example involved preparing recommendations for Compute Savings Plans and RDS Reserved Instances, and I used AWS Cost Explorer to analyze historical usage patterns, identify stable workloads, evaluate commitment opportunities, and estimate potential savings. This analysis helped me build a business case for leadership and finance teams.

The challenge I typically run into when building business cases is determining the optimal commitment level without overcommitting resources. AWS Cost Explorer allows us to review usage trends, reservation coverage, high utilization rates, and forecast spend. This gives us the confidence to recommend commitments that could generate significant savings while maintaining operational flexibility.

The best features AWS Cost Explorer offers include cost and usage trend analysis, the cost forecasting feature, service-level spending breakdowns, the tags and cost allocation analysis, Savings Plans recommendations, Reserved Instances recommendations, and reservation coverage and utilization reports. I also appreciate being able to filter by account, service, region, tag, and cost category.

The features that stand out for my workflow include cost and usage trend analysis, which I probably could not imagine working without because it really helps me follow the evolution of the different costs per account, per month over the entire year to be able to give useful information to management for possible commitment purposes and decision-making. Without this service or feature, it would be difficult.

I particularly appreciate how quickly I can move from a high-level cost view to detailed analysis without requiring complex queries or external reporting tools.

AWS Cost Explorer has positively impacted my organization by improving our cost visibility, enabling better financial accountability, and supporting data-driven optimization decisions. It also facilitates collaboration between the teams—engineering, finance, procurement, and leadership—by providing a common source of truth for cloud spending. While I cannot disclose confidential figures, AWS Cost Explorer has helped support cloud optimization initiatives that resulted in great annual savings opportunities through Savings Plans, Reserved Instances, and rightsizing initiatives. It has also reduced the time required to investigate our cost anomalies from hours to minutes.

When I mention reduced investigation time from hours to minutes, the typical workflow before involved a team being lost, trying to reconcile where these costs have come from, what accounts have been involved, which services, and jumping from one account to another. For example, if leadership were to ask why AWS cost increased by twenty percent compared to the previous month, this investigation could take hours because you would need to review invoices, analyze usage reports, check which services had increased consumption, identify the affected accounts, and then contact engineering teams for context. However, AWS Cost Explorer streamlined this process significantly because it provides immediate visibility into cost trends. I can quickly compare the time periods, filter by service, account, region, tag, and cost category, and identify the primary drivers of the increase within minutes.

When discussing how AWS Cost Explorer can be improved, I would suggest that if they could incorporate more advanced forecasting capabilities, maybe stronger AI-driven optimization recommendations—especially related to tokenomics and AI-related services—improved anomaly root cause analysis, better executive-level dashboards, and easier multidimensional reporting across larger organizations, it would enhance the service.

While I feel that AWS Cost Explorer is very effective for operational FinOps work, I also believe larger enterprises would need to complement it with BI tools for deeper analysis.

I have been using AWS Cost Explorer for approximately six years, and I continue to use it extensively.

AWS Cost Explorer is deployed in my organization in a public cloud setup.

I use AWS as my cloud provider.

I did not purchase AWS Cost Explorer through the AWS Marketplace because it is a native AWS service included with the AWS Management Console and billing ecosystem, and I access it directly through AWS.

My advice to others looking into using AWS Cost Explorer is to start by implementing a strong tagging and cost allocation strategy because AWS Cost Explorer becomes significantly more valuable when costs can be mapped to business units, applications, environments, and teams. I would also recommend combining AWS Cost Explorer with AWS Budget, Cost Anomaly Detection, the Cost and Usage Report, and regular FinOps reviews, as it provides excellent visibility, but the greatest value comes when it is integrated into a broader cloud financial management practice.

I rate AWS Cost Explorer a nine out of ten because it provides excellent visibility into AWS costs, and it is quite easy to use. The reason I would not give it a ten is that advanced analytics, forecasting, and reporting often require additional services, as I mentioned earlier, such as the CUR, Athena, Quicksight, or third-party FinOps platforms.

Regarding AWS Cost Explorer's AI capabilities, I view the governance and security capabilities quite positively, as cost data access can be controlled through IAM policies, and an organization can implement role-based access controls to ensure users only see the information relevant to them, which is particularly important in regulated environments.

I find AWS Cost Explorer's output highly accurate because it is driven and derived directly from AWS billing and usage data, and for cost reporting and trend analysis, I consider it a reliable source of truth.

We have been handling all of the AWS infrastructure for the customer for maybe two years.

AWS Cost Explorer is used to visualize, analyze, and manage spending on the cloud. It can also make a forecast on how much you will spend and gives you information about past costs you had in the cloud in various regions for various different tools.

For example, you can see how much it will cost to use a specific product in the future. You can also set a timeline for how much you will use that product to see the effective amount of money you are going to spend. You can compare various tools in order to see which are the most suited tools for your needs and which are the most expensive.

You can filter by region and by specific product in order to see which costs are the most important in your organization and cloud environment. You can identify what is not necessary and what you can reduce. It has many good features that you can use with best practices.

You can integrate AWS Cost Explorer, and it gives you a better overview of all the related aspects to the costing part of your infrastructure.

AWS Cost Explorer is beneficial because you can access a simple interface where you can get an overview of all the costs you have in the cloud environment. You can see which costs you can reduce and how you can move from a specific product to another product in order to reduce costs and improve other aspects. It depends on the specific needs of the organization, but the most important advantage AWS Cost Explorer gives you is the ability to have a clear understanding of your cloud spending.

One disadvantage of AWS Cost Explorer is that you cannot filter too much. You cannot filter data by more than one variable. It depends on the specific permissions you assign to the group that will handle it. The people using AWS Cost Explorer have to know the tool as it is not as simple as other tools.

AWS Cost Explorer is stable.

I have never tried to scale AWS Cost Explorer, so I don't know how you would do that. I think it should not be so difficult. As far as I remember, it is a global service.

AWS Cost Explorer has good support. You can access a lot of materials and documentation before going directly to the support team.

Neutral

I am not using too much now as I am using other tools, specifically the cloud in general, AWS or Google Cloud Platform.

You can use AWS Cost Explorer directly from the console. You don't have to install it.

AWS Cost Explorer is affordable.

Some other cloud providers are GCP or Azure.

In the past, I worked with DynamoDB and all the tools related to IAM and Cloud to see all the costs. I have also worked with SNS, SQS, Route 53, CloudFront, Cloud DNS, EKS, the compute engine, tools related to databases for PostgreSQL, CloudFormation, CodePipeline, CodeCommit, and the tool to store Docker images.

Historic data depends on your organization. You can use the CPU or memory, or you can use metrics related to CPU use over time. The node depends on your organization, but in general, memory and CPU are the most important metrics. You can see that by specific namespace in Kubernetes.

AWS Cost Explorer is a good tool for every type of customer. The section rating for customer service is three.

Primarily, I use AWS Cost Explorer to maintain cost and current budget constraints. Our FinOps team provides us with a budget for the month, and we track our spending to identify where funds are allocated. We have billing alerts set up to notify us when our infrastructure exceeds a certain amount, prompting us to review our spending and justify it to the FinOps team. It's essential for keeping track of our monthly expenses.

AWS Cost Explorer assists in better forecasting our future budget needs based on previous month's data. This helps in deciding whether we need to increase or decrease our budget depending on upcoming projects and plans.

I find the forecasting feature particularly valuable as it helps predict future expenses. This feature allows for detailed analysis, providing insight into specific spending areas, making it a useful tool for budget planning.

While there is always room for improvement, any needs for enhancement depend on specific requirements at the time. Currently, I cannot pinpoint any specific improvements needed.

I have been using AWS Cost Explorer for at least three or four years.

AWS Cost Explorer is quite stable. Although Amazon has occasional issues, these have not impacted me significantly when using it. It's mainly used for reporting purposes, and I've never faced issues with downtime.

AWS Cost Explorer scales almost in real-time with our environment. It automatically adapts to any new infrastructure added, providing visibility into any changes, such as spikes due to testing, enhancing our management perspective.

Amazon's technical support team is very knowledgeable, quick, and responsive. Their availability is high, and the level of support depends on the business level and the level of support paid for.

Positive

The setup is straightforward since it integrates directly into the existing AWS infrastructure. You just need to access the tool through the AWS platform.

AWS Cost Explorer is part of the AWS package, so the cost is not directly associated with it. If you are using AWS services, you are already included in the cost structure.

It's important to ensure you utilize AWS Cost Explorer to control and forecast costs accurately. This tool is essential for anyone using AWS services.

I'd rate the solution ten out of ten.