Ask a precise cost question.

Analyze cost per compute service for a subaccount

Analyze costs by availability zone for a subaccount

Analyze costs by service name

Analyze costs of components of a resource

Analyze marketplace vendors costs

Analyze the different metered costs for a particular SKU

Analyze service costs by region

Analyze service costs by subaccount

Analyze service costs month over month

Calculate unit economics

Compare billed cost per subaccount to budget

Compare resource usage month over month

Determine Effective Savings Rate

Determine Effective Savings Rate by Service

Determine Effective Savings Rate

Forecast amortized costs month over month based on historical trends

Forecast cashflow month over month based on historical trends by service

Get historical usage and rates to enable cost forecasting

Analyze tag coverage

Identify anomalous daily spending by subaccount

Identify anomalous daily spending by subaccount and region

Identify anomalous daily spending by subaccount, region, and service

Identify unused commitments

Report costs by service category

Report effective cost of compute

Report recurring charges for commitment-based discounts over a period

Report service costs by providers subaccount

Report spending across billing periods for a provider by service category

Report subaccounts by region

Update budgets with billed costs

Verify Accuracy of Provider Invoices

Verify accuracy of services charges across providers

Verify discount accuracy for previously invoiced billing period

Allocate multi-currency charges per application

Allocate multi-currency charges per application

Analyze cost by participating entities

Analyze costs by availability zone for a subaccount

Analyze costs by service name

Analyze credit memos

Analyze credit memos

Analyze marketplace vendors costs

Analyze resource costs by SKU

Analyze service costs by region

Analyze service costs month over month

Analyze tag coverage

Breaks one SKU's quantity, list cost and effective cost down by charge period, SKU price and list unit price. SkuMeter does not exist in v1.0 and is dropped; SkuPriceId still separates the SKU's price tiers. Default SKU A86N9S7CGUKZHH8P (CloudFront data transfer out) shows a paid $0.12/GB tier next to the free tier; effective cost is whole-dollar rounded in this sample, so the chart uses list cost.

Analyze the different metered costs for a particular SKU

Cash vs. Accrual Comparison by Billing Period

Commitment Discount Effective Cost Breakdown

Compare billed cost per subaccount to budget

Compare resource usage month over month

Determine Effective Savings Rate by Service

Discount Effectiveness by Service

Effective Cost by Service and Region

Forecast amortized costs month over month based on historical trends

Forecast cashflow month over month based on historical trends by service

Get historical usage and rates to enable cost forecasting

Identify anomalous daily spending by subaccount and region

Identify anomalous daily spending by subaccount

Identify anomalous daily spending by subaccount, region, and service

Identify sources of billed cost

Identify sources of billed cost

Identify unused commitments

Report application cost month over month

Report commitment discount purchases

Report commitment discount purchases

Report costs by service category

Report effective cost of compute

Report service costs by providers subaccount

Report service costs by providers subaccount

Report spending across billing periods for a service provider by service category

Report subaccounts by region

Track marketplace purchases across providers

Understand the billing account or sub account entity

Understand the billing account or sub account entity

Update budgets for each application

Update budgets for each application

Update budgets with billed costs

Verify accuracy of provider invoices aka invoice reconciliation

Verify accuracy of service provider invoices

Verify accuracy of services charges across service providers

Verify discount accuracy for a previously invoiced billing period (corrections excluded)

CapacityReservationId and CapacityReservationStatus are absent from the v1.0 sample, so compute charges cannot be classified as used, unused or non-reserved capacity.

CapacityReservationId and CapacityReservationStatus are absent from the v1.0 sample, so compute charges cannot be classified by capacity-reservation usage.

PricingCurrency and PricingCurrencyEffectiveCost are absent from the v1.0 sample, so effective cost cannot be expressed in the pricing currency.

The v1.0 sample lacks PricingCurrency and PricingCurrencyEffectiveCost, so BillingCurrency and EffectiveCost cannot reproduce pricing-denominated costs or exchange-rate effects.

No virtual-currency Purchase charges exist in the sample: the only Purchase rows have PricingUnit Hours and are AWS Savings Plan purchases.

The sample contains no virtual-currency Purchase charges: its only Purchase rows are three AWS Compute Savings Plan fees priced in Hours, so the PricingUnit filter has no virtual-currency unit to select.

No virtual-currency Purchase charges are present in the sample: the only Purchase rows have PricingUnit Hours and describe AWS Compute Savings Plans.

AllocatedMethodId, AllocatedResourceId and AllocatedResourceName (v1.3+ allocation columns) are absent from the v1.0 sample, so allocated-resource costs cannot be derived.

SkuPriceDetails (with its CoreCount and InstanceSeries properties) is absent from the v1.0 sample, so effective cost per core cannot be computed.

The v1.0 sample lacks SkuPriceDetails, including its CoreCount and InstanceSeries properties, so average effective cost per core cannot be calculated.

CommitmentProgramEligibilityDetails (v1.4) is absent from the v1.0 sample, so the eligibility-adjusted denominator of uncovered-but-eligible usage cannot be computed.

PricingCurrency and PricingCurrencyEffectiveCost (introduced in FOCUS v1.2) are absent from the v1.0 sample.

PricingCurrency and PricingCurrencyEffectiveCost are absent from the v1.0 sample, so consumption denominated in a virtual currency cannot be measured.

CommitmentProgramEligibilityDetails (FOCUS v1.4) is absent from the v1.0 sample, so eligible program types and eligible cost cannot be derived.

PricingCurrency, PricingCurrencyListUnitPrice, PricingCurrencyContractedUnitPrice and ServiceSubcategory are absent from the v1.0 sample, so savings in a virtual pricing currency cannot be computed.

PricingCurrency and PricingCurrencyEffectiveCost (introduced in FOCUS v1.2) are absent from the v1.0 sample.

PricingCurrency and PricingCurrencyEffectiveCost (and HostProviderName) are absent from the v1.0 sample, so virtual-currency consumption cannot be attributed to services.

CommitmentProgramEligibilityDetails (with its CommitmentPrograms ProgramType entries) and CapacityReservationStatus are absent from the v1.0 sample, so capacity-reservation-eligible spend cannot be identified.

CommitmentProgramEligibilityDetails is absent from the v1.0 sample, so eligible program types and eligible uncovered spend cannot be determined.

AllocatedMethodId (v1.3+ allocation column) is absent from the v1.0 sample, so resources with shared cost allocation cannot be identified.

CapacityReservationId and CapacityReservationStatus are absent from the v1.0 sample, so unused capacity reservations cannot be identified.

CapacityReservationId and CapacityReservationStatus (v1.1+) are absent from the v1.0 sample, so unused capacity reservations cannot be identified.

ContractApplied and the Contract Commitment dataset fields ContractCommitmentId, ContractCommitmentCategory, ContractCommitmentPeriodStart, ContractCommitmentPeriodEnd, and ContractCommitmentCost are absent from the v1.0 sample.

SkuPriceDetails (FOCUS v1.2+, holding CoreCount and InstanceSeries) is absent from the v1.0 sample.

SkuPriceDetails (with its CoreCount and InstanceSeries properties) is absent from the v1.0 sample, so core counts by instance series cannot be summed.

InvoiceId and the separate Invoice Detail dataset containing InvoiceId and BilledCost are absent from the v1.0 sample, preventing invoice-level reconciliation.

The query reads the v1.4 Invoice Detail dataset (InvoiceId, PaymentCurrencyInvoiceDetailId, PaymentCurrencyBilledCost), none of which exist in the v1.0 cost-and-usage sample.

The sample contains no ChargeClass = 'Correction' rows (ChargeClass is null throughout), so corrections to previously invoiced billing periods cannot be reported by subaccount.

ChargeClass is null on every row of the v1.0 sample, so there are no 'Correction' charges to report for any billing period.

The sample contains no ChargeClass = 'Correction' records, so corrections to previously invoiced billing periods cannot be reported.

The sample contains no ChargeClass = 'Correction' rows (ChargeClass is null throughout), so the query returns nothing meaningful.

ServiceSubcategory is absent from the v1.0 sample (it was added in FOCUS v1.1), so costs cannot be reported at the service-subcategory grain.

ServiceSubcategory is absent from the v1.0 sample, so billed costs cannot be reported at the requested service-subcategory grain.

ContractApplied and its ContractCommitmentID / ContractCommitmentAppliedCost elements are absent from the v1.0 sample, so contract-commitment purchases cannot be reported.

ContractApplied and its ContractCommitmentID / ContractCommitmentAppliedCost elements are absent from the v1.0 sample, so contract-commitment burn-down cannot be tracked.

The Invoice Detail dataset and InvoiceId are absent from the v1.0 sample, so tax and service amounts cannot be totalled per invoice.