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: SQL Server connectivity and AWS network operations

AWS network cost estimates: compare paths, directions and peak bandwidth

The same data volume can incur different charges on different paths. Break a SQL Server reporting workload into volumes, time and transfer for each component.

What you will learn

Break a SQL Server reporting workload into volumes, time and transfer for each component.

Prerequisite

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

Trace traffic and replies separately

Depending on the AWS VPC path, charges may include hourly usage, data processing and transfer. Compare the applicable Region and path conditions.

Three measurements for a scheduled report
Three measurements for a scheduled report1: Workload — Restrict the request — Response. 2: Response — Record the actual path — Path. 3: Path — Match rate conditions — Assessment123WorkloadResponsePathAssessmentThree measurements for a scheduled report1: Workload — Restrict the request — Response. 2: Response — Record the actual path — Path. 3: Path — Match rate conditions — Assessment123WorkloadResponsePathAssessment
  1. Workload → ResponseRestrict the request
  2. Response → PathRecord the actual path
  3. Path → AssessmentMatch rate conditions
Workload
SQL Server report
Response
Report sent to the reader
Path
Same AZ or another path
Assessment
Bandwidth and cost

A daily average hides a short peak

Fictional paths A and B deliver the same report and have identical latency requirements.
MeasureSample valueInterpretation
Daily egress response60 GB per daySeparate by traffic direction
Peak burst30 GB in 10 minutesAt least 400 Mbit/s on average
Path AClient in the same AZCheck service and billing conditions
Path BDevice on a path to another AZCheck processing and transfer independently

30 GB in ten minutes is 240 Gbit divided by 600 seconds, or 0.4 Gbit/s using decimal units. Overhead and shorter peaks need separate headroom.

Check assumptions before budgeting

Separate time and traffic. One quantity of traffic can be measured as equipment processing and as path transfer. Reconcile the actual billing units.

Record both directions. Replies can be much larger than requests. Keep the two measurements separate.

Include failover. Measure bandwidth and costs separately on the normal path and on the surviving path.

Check your decision

Choose an option to see the result and explanation.

What average is needed to send 30 GB in ten minutes?
Read the answer and reason

Answer: About 400 Mbit/s · Convert to 240 Gbit and divide by 600 seconds.

Only path B traverses another component. What do you add?
Read the answer and reason

Answer: Additional charge items and their measurement conditions · Compare equipment hours, processing and applicable transfer.

A different AZ is used only during failover. How do you evaluate it?
Read the answer and reason

Answer: Measure paths and required capacity in both states · Compare normal and degraded operation separately.

Check, then explain in your own words

  1. Map the path and direction.
  2. Match peak windows against measured volume.
  3. Separate hourly, processing and transfer charges.
Check your understanding: Does low daily average traffic establish a low peak?

Measure bytes transferred in a shorter window and observe workload latency.

Bandwidth and total volume describe different properties.

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.