Starting today, Split Cost Allocation Data for Amazon EKS now allows you to import up to 50 Kubernetes custom labels per pod as cost allocation tags. You can attribute costs of your Amazon EKS cluster at the pod level using custom attributes, such as cost center, application, business unit, and environment in AWS Cost and Usage Report (CUR).
With this new capability, you can better align your cost allocation with specific business requirements and organizational structure driven by your cloud financial management needs. This enables granular cost visibility of your EKS clusters running multiple application containers using shared EC2 instances, allowing you to allocate the shared costs of your EKS cluster. For new split cost allocation data customers, you can enable this feature in the AWS Billing and Cost Management console. For existing customers, EKS will automatically import the labels, but you must activate them as cost allocation tags. After activation, Kubernetes custom labels are available in your CUR within 24 hours. You can use the Containers Cost Allocation dashboard to visualize the costs in Amazon QuickSight and the CUR query library to query the costs using Amazon Athena.
This feature is available in all AWS Regions where Split Cost Allocation Data for Amazon EKS is available. To get started, visit Understanding Split Cost Allocation Data.
Categories: general:products/cloud-financial-management
Source: Amazon Web Services
Latest Posts
- Microsoft 365 Copilot Chat – Updates to Copilot in Word, Excel, and PowerPoint [MC1253863]
- Amazon CloudWatch introduces organization-wide EC2 detailed monitoring enablement
- SageMaker HyperPod now supports idle resource sharing for dynamic cluster utilization
- (Updated) Microsoft 365 Copilot: Prepare for your meeting with Copilot chat in Outlook mobile [MC1182702]
