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: Costs, Free Tier and budgets

How to read an AWS bill: periods, services, Regions and usage

Read an AWS bill by aligning its period and scope, then drilling into service → Region → usage. Distinguish current estimates from finalized invoices and usage charges from credits or other adjustments. Explain a change using specific line items rather than comparing unlike totals.

What you will learn

Choose a useful sequence through the Bills page, compare like-for-like amounts and narrow down the reason for a difference.

Prerequisite

Know the main AWS cost components. Actual billing access belongs in an authorized account; this site does not need your invoice or account details.

Align the comparison before reading the total

Four initial checks
CheckWhy it matters
PeriodA partial current month and a full previous month contain different numbers of days
Estimate or final invoicePending current-month charges are estimates, unlike finalized charges
Account and billing scopeOrganizations and billing transfer can change visibility, permissions and invoice ownership
Currency and adjustmentsCheck how tax, credits and refunds enter the total

Open Bills in AWS Billing and Cost Management and select the Billing period. The current month’s estimate is an aggregation at that time, not a finalized invoice. If access is missing, ask the administrator for appropriate read permissions rather than using root for routine investigation.

Follow the charge breakdown from service to usage

Trace a total difference to a specific usage component
Trace a total difference to a specific usage component1: Period and scope — Align the scope, then choose the service with the relevant difference. — Service. 2: Service — Expand the service breakdown and identify the Region. — Region. 3: Region — Use the line item and quantity to form a hypothesis, then check the resource’s actual purpose. — Usage and line item123Period and scopeServiceRegionUsage and line itemTrace a total difference to a specific usage component1: Period and scope — Align the scope, then choose the service with the relevant difference. — Service. 2: Service — Expand the service breakdown and identify the Region. — Region. 3: Region — Use the line item and quantity to form a hypothesis, then check the resource’s actual purpose. — Usage and line item123Period andscopeServiceRegionUsage and lineitem
  1. Period and scope → ServiceAlign the scope, then choose the service with the relevant difference.
  2. Service → RegionExpand the service breakdown and identify the Region.
  3. Region → Usage and line itemUse the line item and quantity to form a hypothesis, then check the resource’s actual purpose.
Period and scope
Start from comparable conditions; distinguish estimates from final charges.
Service
Find the service with a material change.
Region
Identify where the usage occurred.
Usage and line item
Find the changed runtime, capacity, transfer or other usage component.

Billing line items are not a live inventory. They may include earlier use of a resource that has already stopped. Separate the charged period from the resource’s current state.

Worked example: the server count is unchanged but cost rises

Investigate beyond the number of servers
Observed differenceNext check
An EBS-related component increasedProvisioned capacity/performance, retention time and snapshots
Usage appears in another RegionLearning resources, resources created by other services and their owners
Usage is similar but the amount payable increasedDifferences in credits, tax, refunds and their application
The partial current month is smaller than last monthComparable day counts and estimate/final status

Choose an option to see the result and explanation.

The estimate through day 10 is below last month’s finalized total. Does that alone prove improved efficiency?
Read the answer and reason

Answer: No, align the period and cost breakdown first · The day count and estimate/final status differ. Compare equivalent periods, scope and cost measures, including usage and adjustments.

Return from a line item to the relevant resource

  1. Record the service, Region, line item and charged period.
  2. Have an authorized administrator inspect usage, related resources and ownership.
  3. Even for unexpected resources, establish data, purpose and dependencies before acting.
  4. After a change, recheck when billing data updates; separate past use from ongoing charges.

Record a finding and the next check

Replace “it is expensive” with a scoped finding: “Over the same period, storage-related usage increased in this Region; confirm retained resources with their owner.” Keep conditions, observations and next checks separate. Do not send this site actual account numbers or invoices.

For ongoing awareness, continue to budget-alert design. Align the alert’s scope and cost measure with your billing review, and decide who responds and what they investigate.

Check, then explain in your own words

  1. Align period, estimate/final status, scope and currency.
  2. Drill down through service, Region, line item and usage.
  3. Separate adjustments and establish the purpose of related resources.
Check your understanding: Does a resource appearing on a bill prove that it is running now?

No. Past usage can remain on the bill; establish current state separately.

A billing period and a live resource state are different observations. A charge displayed after deletion is not, on its own, evidence of continuing resource use.

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.