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

Trace AWS network costs through NAT processing, transfer and running hours

An idle path may still incur hourly charges. Separate running hours, processed GB and applicable transfer along a single network path.

What you will learn

Separate running hours, processed GB and applicable transfer along a single network path.

Prerequisite

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

Count each cost along the path

NAT gateway time and processed volume are separate charges. Inspect the route and applicable conditions before assigning transfer charges.

Estimate quantities from synthetic observations
Estimate quantities from synthetic observations1: Path — Map each path segment — Time. 2: Time — Calculate by unit — Volume. 3: Volume — Reconcile billing — Verify123PathTimeVolumeVerifyEstimate quantities from synthetic observations1: Path — Map each path segment — Time. 2: Time — Calculate by unit — Volume. 3: Volume — Reconcile billing — Verify123PathTimeVolumeVerify
  1. Path → TimeMap each path segment
  2. Time → VolumeCalculate by unit
  3. Volume → VerifyReconcile billing
Path
Source, destination and AZ
Time
Gateway running hours
Volume
Processing and transfer
Verify
Compare billed usage types

A week of traffic on a test path

One NAT gateway remains running for 168 hours. No actual rates are assumed.
Charge componentObservationCheck
NAT running168 hoursHourly component
NAT processing40 GBProcessing component
Crosses AZ boundary10 GB of the trafficCheck direction and transfer conditions
No traffic48 hoursRuns throughout, so count these hours

Keep hours and GB separate. Compare path alternatives using the same availability requirements.

Checks for quantity and cost

Verify charge units Map gateway hours, processing volume and transfer to the network path.

Keep constraints comparable Align region, AZs, paths and availability requirements between designs.

Explain any residual Filter billing by usage type and track overlaps or unexplained differences.

Check your decision

Choose an option to see the result and explanation.

How do you treat the 48 idle hours?
Read the answer and reason

Answer: Include the time in running hours · The gateway remained running.

What additional charge applies to the 10 GB across AZs?
Read the answer and reason

Answer: Match conditions and usage types · First confirm charging conditions on the actual route.

Which conditions make an alternative comparable?
Read the answer and reason

Answer: Aligned availability, volume and path assumptions · Use equivalent service conditions.

Check, then explain in your own words

  1. Map the actual route.
  2. Calculate quantities by unit.
  3. Explain billing differences by usage type.
Check your understanding: Does zero traffic imply a zero total charge?

Check running hours and any separately billed path components.

The path has multiple billing units.

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.