We are thrilled to announce that cost data for Amazon Elastic Container Service (Amazon ECS) tasks and AWS Batch jobs is now accessible in the AWS Cost and Usage Reports (CUR). This new feature, known as AWS Split Cost Allocation Data, allows users to gain a clearer insight into the costs and usage of their containerized applications. It empowers organizations to allocate application expenses back to specific business units, based on the consumption of shared compute and memory resources used by their containerized applications. To learn how to opt in and view your Split Cost Allocation Data, check out this comprehensive guide.
In case you missed it, there are valuable resources available to help you enhance cost visibility, optimize expenditures, and develop a robust Cloud Financial Management (CFM) framework for your organization. For further insights on building an effective CFM strategy, you can explore this other blog post here.
To effectively kickstart your cost optimization initiatives, it is essential to cultivate a team that understands and executes CFM strategies to maximize the value derived from cloud investments. This involves fostering cross-team communication and sharing best practices to expedite optimization efforts.
In addition, we discuss the importance of implementing a tagging strategy that enhances cost visibility. By utilizing tools such as AWS Cost Explorer, AWS Organizations, and AWS Config, organizations can define, apply, and enforce tagging protocols to improve cost awareness.
AWS has introduced new features that offer greater flexibility in grouping resources and accounts through AWS Cost Categories. The inclusion of a “Region” dimension and the “OR” operator enables users to create more refined cost category rules across various dimensions.
To operationalize your CFM strategy, you must identify available tools to help allocate, visualize, and manage AWS costs effectively. In our CFM Talk session, we provide an example optimization using AWS Graviton, illustrating how to effectively think about each pillar of CFM while integrating the right tools into your strategy.
For those looking to implement a chargeback strategy for shared services, we present a reference architecture that automates this process, using AWS Transit Gateway costs as a case study. Another valuable resource can be found here, which offers excellent guidance on the topic.
As your organization seeks to innovate and leverage the cloud’s flexibility, ensuring that your CFM setup is robust and adaptable is essential. This blog series will guide you through the four core AWS CFM principles: See, Save, Plan, and Run, providing actionable recommendations to set your business on a path to success.
Leave a Reply