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: Bill increases and data transfer costs

AWS data transfer costs: separate AZ, Region and NAT processing charges

Data volume alone does not determine a transfer bill. Separate source, destination, direction, AZ/Region boundaries, intermediate processing, available time and the applicable plan. A zero transfer charge on one leg does not make every related component free. Practice with fictional quantities and rates.

What you will learn

Separate network paths from billing units and compare transfer, processing and time components on consistent terms.

Prerequisite

An AZ is a placement boundary within a Region; NAT translates traffic for uses such as outbound connections. Check the service’s definition of billed GB. This is not a calculator that reproduces a real bill.

Describe source, destination and path first

The same volume can have different billing conditions
ConditionQuestion
Service and directionEC2→S3 or EC2→internet? Is there return traffic?
Region and AZWhich same-AZ, cross-AZ or cross-Region boundaries are crossed?
IntermediariesDoes traffic traverse NAT, an endpoint or a load balancer?
Rates and planHow are time, processing, requests or included flat-rate components treated?

Avoid universal rules such as “everything inside AWS is free,” “same-AZ traffic has no processing cost” or “every service receives data free.” Match the official conditions to the service and path. Storage or requests at a destination can remain separate components.

Transfer, processing and time are separate components

Cost components; arrows are not network paths
Cost components; arrows are not network paths1: Available time — Time units × applicable rate — Selected subtotal. 2: Processed data — Processed quantity × applicable rate — Selected subtotal. 3: Billable transfer — Billable transfer × applicable rate — Selected subtotal123Available timeProcessed dataBillable transferSelected subtotalCost components; arrows are not network paths1: Available time — Time units × applicable rate — Selected subtotal. 2: Processed data — Processed quantity × applicable rate — Selected subtotal. 3: Billable transfer — Billable transfer × applicable rate — Selected subtotal123Available timeProcessed dataBillabletransferSelectedsubtotal
  1. Available time → Selected subtotalTime units × applicable rate
  2. Processed data → Selected subtotalProcessed quantity × applicable rate
  3. Billable transfer → Selected subtotalBillable transfer × applicable rate
Available time
Time units for the selected mode
Processed data
Data processed by an intermediary
Billable transfer
Volume for the covered direction/path
Selected subtotal
Sum the component costs
Separate components for example EC2 paths through NAT
Path conditionPricing check
Same-AZ EC2→NAT→same-Region S3The official example separates free covered EC2/S3 transfer from NAT time and processing
EC2 and zonal NAT in different AZsReview applicable cross-AZ transfer in addition to NAT components
EC2→NAT→internetSeparate NAT time/processing from applicable outbound transfer
Regional NAT configured across AZsOne NAT ID can still involve configured per-AZ time units

P1: distinguish one resource ID from its billing units

P1 arithmetic for only three components
ComponentQuantityInvented rateCost
Time2 AZs × 10 hours = 20 AZ-hours$0.04/AZ-hour$0.80
NAT processing6 GB forward + 4 GB return = 10 GB$0.05/GB$0.50
Covered transfer6 GB as stipulated$0.10/GB$0.60
Selected subtotalSum money, not incompatible quantities—$1.90

One NAT ID still produces 20 AZ-hours in P1, not ten. The 10 GB processed and the separate 6 GB transfer component are different billing dimensions; they do not imply that NAT processed 16 GB. Do not generalize P1’s stipulated transfer quantity to an arbitrary live path.

Compare related conditions before changing paths or plans

For eligible same-Region S3/DynamoDB traffic, a gateway endpoint can provide a route that avoids NAT, without an additional gateway-endpoint charge. Verify service support, route tables and access controls. This does not make S3 storage or requests universally free.

For web delivery, distinguish CloudFront pay-as-you-go pricing from flat-rate plans. Review included services/features, usage allowances and origin-path conditions. A CDN does not erase every AWS component; compare any change in origin requests under the actual usage pattern.

  1. Describe source, destination, direction, AZ/Region and actual route.
  2. Separate transfer, processing, time, requests and other components.
  3. Align units, scope, Region, plan and check date before calculating.
  4. Compare availability, controls, migration/recovery and related costs too.
  5. Inspect before/after line items and quantities while allowing for reporting lag.

Practice separating quantities and components

Choose an option to see the result and explanation.

P1 has one regional NAT ID configured in two AZs for ten hours each. How much time is counted?
Read the answer and reason

Answer: 20 AZ-hours · Two times ten equals twenty under P1’s whole-hour assumptions.

What quantity does NAT process in P1?
Read the answer and reason

Answer: 10 GB: 6 forward plus 4 return · Add the stipulated forward and return processing quantities, separately from the transfer component.

What is the subtotal of P1’s three components?
Read the answer and reason

Answer: $1.90 · 0.80 + 0.50 + 0.60 equals 1.90 for only the stipulated components, not a full AWS bill.

If transfer on one covered leg is free, are NAT and all related components also free?
Read the answer and reason

Answer: Check separately; processing and time can remain · Review each component under the conditions for the actual service and path.

Check, then explain in your own words

  1. Separate P1’s 20 AZ-hours, 10 GB processed and 6 GB transfer component.
  2. Verify the invented-rate subtotal of $1.90.
  3. List conditions for comparing NAT, gateway endpoints and web-delivery plans.
Check your understanding: Besides volume, what must you align for transfer-cost analysis?

Service, direction, AZ/Region, path, processing/time and pricing plan.

Several components can apply to a path; one free leg or one resource ID does not determine the total.

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.