What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

Resource tags assigned to Atlas clusters are not preserved in invoices if the cluster is deleted before the invoice is exported. Atlas fetches tags live at export time rather than recording them when the cost is incurred. This means that any ephemeral cluster - correctly tagged throughout its entire lifetime - will appear as untagged in the invoice, making it impossible to attribute its costs to the right team, project, or cost center.

What would you like to see happen?

Describe the desired outcome or enhancement.

Resource tags in invoices should reflect the state at the time of use, not export time.
Atlas should record and persist resource tags at the time each cost event occurs, so that invoice exports always reflect the tag state that was true during the billing period - regardless of whether the cluster still exists at the time of download. This is consistent with how cost allocation tagging works in AWS and GCP.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

Accurate tag-based cost attribution is a core part of our FinOps practice. We use resource tags to allocate cloud spend across teams, track budgets, and produce monthly cost reports. When ephemeral clusters - which are a normal and frequent part of our infrastructure - show up as untagged, entire categories of spend become invisible to our reporting. This directly undermines our ability to manage and understand our cloud costs.

What steps, if any, are you taking today to manage this problem?

Currently, there is no reliable workaround. We have to manually cross-reference cluster creation and deletion logs with invoice line items to reconstruct cost attribution - a time-consuming and error-prone process. For short-lived clusters, this is often not feasible at all.