Clarification on Split Cost Calculation

Quick question about how the Batch costs are calculated in the dashboards. I noticed a bit of a mismatch and wanted to check if I'm missing something obvious.

So from what I understand, the split cost for Batch is calculated based on the Compute and memory (used + unused) of the EC2 instances. But when I compare the numbers across tools, they don’t quite line up. ([AWS Blog Source](https://aws.amazon.com/blogs/aws-cloud-financial-management/la-improve-cost-visibility-of-containerized-applications-with-aws-split-cost-allocation-data-for-ecs-and-batch-jobs/))

For example, when I check Cost Explorer for EC2-Instance usage in February, I see:
- Cost Explorer EC2-Instance total: $1,580.66

But in Grafana, the sum of team costs for the same period comes out to:
- Grafana total: ~$4,627

I also queried Athena directly to double-check, and it aligns more with what Grafana is showing — so not sure what Cost Explorer is excluding (or what we're maybe double-counting?).

Just wanted to clarify:

- What services are included under Batch in the split cost allocation?
- If it’s really just CPU and memory (used + unused) from EC2, do you have any idea why this difference might show up?

Appreciate any insight — thanks!