AWS-CUR

AWS CUR detailed billing data export S3.

Définition

AWS CUR ~150 columns categories : (1) bill_* (bill_invoice_id, bill_payer_account_id, bill_billing_period_*). (2) line_item_* (line_item_usage_account_id, line_item_usage_type, line_item_operation, line_item_usage_amount, line_item_unblended_cost, line_item_blended_cost, line_item_currency_code, line_item_line_item_description). (3) product_* (product_product_name, product_servicecode, product_region, product_instance_type, product_instance_family, etc., ~30 columns describing product attributes specific service). (4) pricing_* (pricing_term, pricing_unit, pricing_public_on_demand_cost). (5) reservation_* (reservation_arn, reservation_reservation_a_r_n, reservation_effective_cost). (6) savings_plan_* (savings_plan_offering_type, savings_plan_savings_plan_effective_cost). (7) discount_* (discount_*). (8) resource_tags_user_* (custom tags). Granularity : hourly or daily, monthly file rotation. CUR 2.0 2024 : FOCUS columns native (BilledCost, EffectiveCost, etc.), reduces need transformation FOCUS adapters. Storage : Parquet preferred (compressed, optimized analytics, columnar), CSV legacy.

Origine

AWS Cost and Usage Reports initial release 2015 ; CUR Parquet support 2018 ; CUR 2.0 (FOCUS-compliant) announced re:Invent 2023 launched 2024.

Exemple en contexte

Capital One AWS environment ~500 linked accounts CUR exported S3 bucket Parquet format hourly, ingested AWS Athena + Quicksight for FinOps analytics dashboards, ~500GB CUR data/month, ~150 PIB historical analytics 5 years cost optimization insights.

Termes liés

• AWS Cost Explorer — console.