New Feature: Cost Visibility for AWS ECS and EKS

We’re excited to announce the beta release of CloudForecast’s latest feature: cost visibility for AWS ECS (Elastic Container Service) and EKS (Elastic Kubernetes Service). This new functionality addresses a critical gap for users who need to understand and manage the costs associated with containerized workloads on AWS.

What’s New?

With this release, CloudForecast leverages AWS’s new Split Cost Allocation Data from CUR 2.0 (Cost and Usage Report) to provide detailed insights into how your ECS and EKS services contribute to overall AWS spending.

This new data set from the CUR allows us to deliver precise cost visibility at the container level, which has historically been challenging for AWS users.

Interested in our new ECS & EKS Cost Visibility Feature? Contact us! We would love to hear from you and learn more!

Why It Matters?

Achieving cost visibility in ECS and EKS is challenging due to the dynamic nature of containers, shared resources, and the lack of native cost attribution at the container level. Without tools like AWS CUR 2.0 with Split Cost Data, accurately tracking and allocating costs can be difficult, especially in environments where multiple teams share clusters.

This new feature addresses these challenges by providing detailed cost breakdowns, enabling more precise budgeting and cost management. It also sets the stage for future enhancements, like resource optimization and container right-sizing, which are crucial for controlling costs in containerized environments.

Reporting via your CloudForecast Cost Groups

CloudForecast integrates AWS ECS and EKS cost data directly into your existing cost groups!

You can view these costs alongside other AWS services in a consolidated report by adding ECS and EKS as a “source” within a cost group and applying tags to help/slice dice costs —no additional complex dashboards are required.

For EKS, AWS automatically generates several tags that can be utilized for cost allocation. These include tags identifying the cluster, namespace, pod, and service associated with each resource. Using these tags within CloudForecast, you can easily slice and dice your EKS costs based on these key attributes and share them with your engineering teams.

For example, you can see how much a specific namespace or service within an EKS cluster is costing your organization, providing precise visibility into where your budget is being spent.

Similarly, for ECS, you can apply your custom tags to tasks and services, which CloudForecast will recognize and use to help you break down costs according to your organization’s needs. Whether you want to track costs by project, team, environment, or any other dimension, tagging allows you to see exactly where your resources are being allocated and how they impact your overall AWS spend.

By aligning CloudForecast “Cost Groups” with your business’s structure and cost allocation, your engineering teams can make more informed decisions with more visibility and how much they spend on containers.

Join the Beta!

We’re gradually onboarding and prioritizing users for our beta testing. During this phase, the feature is free to use—we ask for your feedback to help us keep improving it.

If you’re interested in trying this feature out and helping us make this better, please fill out this form for us: Interest Form

Stay tuned for more updates as we expand our toolset to deliver even greater cost management and visibility across your AWS infrastructure.