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.
Separate network paths from billing units and compare transfer, processing and time components on consistent terms.
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
| Condition | Question |
|---|---|
| Service and direction | EC2→S3 or EC2→internet? Is there return traffic? |
| Region and AZ | Which same-AZ, cross-AZ or cross-Region boundaries are crossed? |
| Intermediaries | Does traffic traverse NAT, an endpoint or a load balancer? |
| Rates and plan | How 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
- Available time → Selected subtotalTime units × applicable rate
- Processed data → Selected subtotalProcessed quantity × applicable rate
- 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
| Path condition | Pricing check |
|---|---|
| Same-AZ EC2→NAT→same-Region S3 | The official example separates free covered EC2/S3 transfer from NAT time and processing |
| EC2 and zonal NAT in different AZs | Review applicable cross-AZ transfer in addition to NAT components |
| EC2→NAT→internet | Separate NAT time/processing from applicable outbound transfer |
| Regional NAT configured across AZs | One NAT ID can still involve configured per-AZ time units |
P1: distinguish one resource ID from its billing units
| Component | Quantity | Invented rate | Cost |
|---|---|---|---|
| Time | 2 AZs × 10 hours = 20 AZ-hours | $0.04/AZ-hour | $0.80 |
| NAT processing | 6 GB forward + 4 GB return = 10 GB | $0.05/GB | $0.50 |
| Covered transfer | 6 GB as stipulated | $0.10/GB | $0.60 |
| Selected subtotal | Sum 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.
- Describe source, destination, direction, AZ/Region and actual route.
- Separate transfer, processing, time, requests and other components.
- Align units, scope, Region, plan and check date before calculating.
- Compare availability, controls, migration/recovery and related costs too.
- 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.
Check, then explain in your own words
- Separate P1’s 20 AZ-hours, 10 GB processed and 6 GB transfer component.
- Verify the invented-rate subtotal of $1.90.
- 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.
Scope and conditionsReview transfer direction, Region/AZ boundaries and covered paths; no fixed-price guarantee. Documentation review, not live AWS verification.
Used in this lessonDescribe source, destination and path first
- Amazon VPC pricingChecked:
Scope and conditionsSeparate NAT AZ-hours, processing and transfer; compare eligible gateway endpoints. Documentation review, not live AWS verification.
Used in this lessonDescribe source, destination and path first Transfer, processing and time are separate components Compare related conditions before changing paths or plans Practice separating quantities and components
- CloudFront pricing plansChecked:
Scope and conditionsDistinguish flat-rate and pay-as-you-go plans; review included features, allowances and origin conditions. Documentation review, not live AWS verification.
Used in this lessonDescribe source, destination and path first Compare related conditions before changing paths or plans
Scope and conditionsNAT time/processing, AZ placement and endpoint comparisons. Documentation review, not live AWS verification.
Used in this lessonTransfer, processing and time are separate components Practice separating quantities and components
- VPC gateway endpointsChecked:
Scope and conditionsEligible S3/DynamoDB paths and no additional gateway-endpoint charge. Documentation review, not live AWS verification.
Used in this lessonCompare related conditions before changing paths or plans Practice separating quantities and components