Know every dollar
in your cloud

Before setting up any exports, make sure the tags you want to slice costs by are activated in the AWS Billing Console → Cost Allocation Tags.

Activate any user-defined tag you plan to use as a dimension in CostGoblin (e.g. team, environment, service). Tags that aren't activated here won't appear in the CUR exports, no matter how they're configured.

Pick a dedicated bucket (or prefix) for all CostGoblin data. We recommend this structure so each export lands in its own namespace:

In the AWS Billing Console → Data Exports, create two exports. Select Cost and usage report (CUR) as the data table and configure each one as follows:

Under Column selection, enable these and disable the rest to keep file sizes small:

In the AWS Billing Console → Cost Optimization Hub → Preferences, enable the S3 data export:

Open CostGoblin, go to Sync and point each data source to its S3 prefix. Once the first sync completes, head to Dimensions to map your tags to cost allocation dimensions. This is where CostGoblin shines — for each dimension you can:

• Normalize — merge inconsistent casing and spelling (prod, Prod, production → one value)
• Define aliases — group multiple tag values under a single label across all views
• Define fallbacks — fill missing resource tags with the account-level tag
• No data reprocessing — changes take effect instantly across all views.