Home

English | 简体中文

AWS Cost Exporter Wiki

This Wiki documents the current stable release, v0.3.0.

v1.0 stabilization is in progress and adds no collectors. It freezes the current configuration, metrics, and HTTP behavior as the v1 contract while adding machine-checked compatibility, lifecycle, capacity, security, and release gates. v0.3.0 remains the installable stable release until those gates produce real acceptance evidence.

AWS Cost Exporter turns low-frequency AWS billing data into stable, target-scoped Prometheus metrics. It is an exporter, not a financial reconciliation system. AWS remains the source of truth.

What it supports

• Explicit multi-account targets with default-chain, Profile, environment-backed, or AssumeRole credentials.
• Cost Explorer totals, service, region, linked-account, forecast, and allowlisted tag costs.
• Unblended, amortized, and net cost bases with explicit provider and cost_basis labels.
• CUR 2.0 aggregate queries through Athena.
• Organizations account metadata, COST Budgets, Savings Plans and Reserved Instances summaries, and Cost Anomaly Detection summaries.
• Prometheus rules, a Grafana dashboard, Docker images, a Helm OCI chart, and least-privilege IAM examples.

Core runtime contract

Background collectors call AWS and Athena on bounded schedules. Successful partial snapshots are validated and atomically published to memory. /metrics only reads the immutable snapshot and never calls AWS or Athena.

A failed refresh keeps the last successful data for that target and collector. Other targets continue independently. /healthz reports process liveness; /ready requires fresh successful Cost Explorer data for required targets.

Start here

1. Read Getting Started.
2. Choose an installation method.
3. Review credentials and target identity.
4. Validate configuration with --check-config.
5. Import the dashboard and alert rules after the first successful refresh.

Use one replica unless duplicate AWS and Athena requests are intentional. The v1 contract keeps replicaCount: 1, memory-only snapshots, and no leader election or shared cache.