1 Answer
- Newest
- Most votes
- Most comments
1
If these are cross-account peering, one part of the charges would be at the other account.
If the customer have CUR enable, they can use this query, modify the table name, to drill-down on the peering charges:
SELECT DISTINCT
"line_item_product_code"
, "bill_billing_period_start_date"
, "bill_payer_account_id"
, "product_product_name"
, "line_item_line_item_type"
, "line_item_operation"
, "product_region"
, "line_item_usage_type"
, "product_from_location"
, "product_to_location"
, "line_item_resource_id"
, ("sum"("line_item_usage_amount") / 1024) "TB's"
, "sum"("line_item_blended_cost") "cost"
FROM
customer_cur_data.customer_all
WHERE "line_item_operation" LIKE '%VPCPeering%'
GROUP BY "line_item_product_code", "bill_billing_period_start_date", "bill_payer_account_id", "product_product_name", "line_item_line_item_type", "line_item_operation", "product_region", "line_item_usage_type", "product_from_location", "product_to_location", "line_item_resource_id"
Relevant content
- asked 5 years ago
- asked 5 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago