Learn Cloud Engineering: AWS Networking, Cost Optimization and Observability
Learn cloud engineering on AWS in three tracks: build the network and storage basics, learn where the bill actually comes from, then instrument systems so you find problems before customers do. Each step links a guide with real CLI commands and dated prices.
Most examples use AWS; the cost and observability stages apply to Azure and GCP with renamed services.
Stage 1: Foundations
Network, storage and identity.
Stage 2: Cost
Where cloud bills come from and how to cut them.
- 4Cloud cost optimization guideFind the biggest line items first.
- 5NAT gateway costsCut the most common surprise charge.
- 6Data transfer and egress costsPrice cross-AZ and internet traffic.
- 7Reserved Instances vs Savings Plans vs SpotCommit to the right discount.
- 8AWS bill spike: the first-hour runbookContain a runaway bill.
Stage 3: Observability
Metrics, logs, traces and alerts that mean something.
- 9Correlating logs, metrics and tracesDebug across signals.
- 10Distributed tracing with OpenTelemetryInstrument a service end to end.
- 11Prometheus vs DatadogChoose self-hosted or SaaS metrics.
- 12Burn-rate alerting for SLOsPage on user impact, not CPU.
- 13Best APM and observability toolsCompare tools by cost and use case.
Keep these open
Every guide on this path names the versions and docs it was checked against and lists its sources at the end. Browse all cloud guides or another learning path.