Configure AWS Cost Exports

Understand CUR 2.0, ingestion coverage and when monthly spend becomes available.

AWS resource inventory and AWS billing are different data sources. CoreFinOps financial views are grounded in configured AWS CUR 2.0 / Data Export records, not inferred from the existence of EC2 or RDS resources.

What to prepare

Configure a supported AWS billing Data Export/CUR 2.0 to a customer-controlled S3 bucket. Verify the export scope, selected billing or payer account, manifest/output location and required S3 read permissions for the CoreFinOps read-only role. AWS may take time to produce the first export.

Ingestion sequence

AWS Data Export → S3 manifest → bounded read/chunks
                → staging/validation → atomic publication
                → allocation run → Overview / Explorer / Reports

The platform preserves previous successfully published periods if a later ingestion fails. Restatements update the affected billing period using a controlled replacement path; raw duplicates must not be counted twice.

Cost measures and currencies

CoreFinOps retains unblended, net unblended, amortized and net amortized measures where available. Net amortized is the default display basis. Every financial fact has a currency, and the system must not silently convert or add different currencies.

Diagnose gaps

A successful connection with no export still produces no authoritative allocated monthly spend. A completed cost ingestion without an allocation run may yield raw spend but leave workload attribution incomplete. A partial export or unavailable service must be reported as incomplete coverage, not zero cost.

Before relying on a number

Confirm the period, whether the month is complete, the cost measure, currency, latest successful ingestion, allocation version and any remaining unallocated amount. Reports generated later can still reflect earlier billing collection times.