INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

Topic lessonTopic: AWS billing analysis and cost optimization

Close an AWS Data Exports monthly report with a reproducible input version

Adding a refreshed delivery to an older delivery can double count the same month. Freeze the billing input used for SQL Server reporting.

What you will learn

Freeze the billing input used for SQL Server reporting.

Prerequisite

This exercise uses fictional evidence and makes no changes in a live environment.

From export delivery to report close

Confirm the report configuration and refresh behavior. Preserve the version and time used to produce the SQL Server aggregate.

A monthly close with traceable evidence
A monthly close with traceable evidence1: Receive — Identify the export — Inventory. 2: Inventory — Avoid duplication — Aggregate. 3: Aggregate — Reconcile before close — Close123ReceiveInventoryAggregateCloseA monthly close with traceable evidence1: Receive — Identify the export — Inventory. 2: Inventory — Avoid duplication — Aggregate. 3: Aggregate — Reconcile before close — Close123ReceiveInventoryAggregateClose
  1. Receive → InventoryIdentify the export
  2. Inventory → AggregateAvoid duplication
  3. Aggregate → CloseReconcile before close
Receive
Period and delivery version
Inventory
Record the complete input set
Aggregate
Same amount column and period
Close
Keep the approved snapshot

Two deliveries for the same month

A was received during the month. B is a trial close input. Figures are fictional.
InputCost totalTreatment
Delivery A950Preliminary report version
Delivery B1,000Later delivery for the same month
A plus B1,950Reject the overlapping total
Frozen report1,000Record columns, period and count

A later correction can be recorded alongside the exact version used to close.

Acceptance for recurring reporting

Inspect refresh behavior Verify the export configuration and select the complete intended set of files.

Check line-item scope Agree on granularity, usage period, refresh and monetary definition.

Freeze the result Tie the input inventory and types to row counts and the report total.

Check your decision

Choose an option to see the result and explanation.

Do you add deliveries A and B?
Read the answer and reason

Answer: Confirm version semantics and freeze the selected input · The same reporting periods overlap.

What is needed to reproduce the report?
Read the answer and reason

Answer: File inventory, version, period and cost metric · Keep the data version and calculation scope.

What happens when a correction arrives after close?
Read the answer and reason

Answer: Record the corrected version and its evidence · Preserve the old version and explain the difference.

Check, then explain in your own words

  1. Verify delivery configuration.
  2. Freeze the input version.
  3. Reconcile counts and amounts.
Check your understanding: Does selecting the month reproduce the exact amount?

Identify the export version and amount definition as well.

The delivered lines can change between refreshes.

Sources and conditions checked

The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.