Skip to Content
Cloud Engineering Academy
2. AWS Networking & Infrastructure

Module 2: AWS Networking & Infrastructure

Design and build private, segmented networks on AWS — VPCs, subnets, routing, firewalls, load balancers, DNS and private connections to AWS services and to on-premises data centres. You prove your database cannot be reached from the internet using Flow Logs and Reachability Analyzer.

SAA-C03SOA-C03SCS-C03

Assumes: AWS CLI v2 · IPv4 + IPv6 · Region us-east-1. Verified against official sources on 2026-11-18.

Design and build private, segmented networks on AWS — VPCs, subnets, routing, firewalls, load balancers, DNS and private connections to AWS services and to on-premises data centres. You prove your database cannot be reached from the internet using Flow Logs and Reachability Analyzer.

Estimated timeAbout 16 hours (lessons 10 h · labs 4 h · exercise 2 h)
Priority for youFoundation — underpins deployment (priority 1) and security (priority 3)
LevelBeginner → intermediate
CertificationsSAA-C03 (primary) · SOA-C03 · SCS-C03
Cost profile🟢 VPC basics free · 🟡 NAT/ALB/endpoints deploy-and-destroy · 🔴 hybrid links design-only

Why this matters in banking

In a bank, "private by default" is not a preference — it is the first question in every architecture review. Customer data must live in subnets with no route to the internet, every allowed connection must be explainable, and traffic logs must exist when an investigator asks "could anything have reached this database?". Banks also keep core systems on-premises for years, so you must understand how AWS connects privately to existing data centres. Networking mistakes are also the most common source of surprise bills (NAT Gateways and idle load balancers).

Analogy: a VPC is a bank branch building. Subnets are rooms, route tables are the corridors that connect them, security groups are the keycard reader on each door, and the NAT Gateway is a staff-only exit that lets people out but never lets visitors in.

From .NET/Azure to AWS

You know (Microsoft/Azure)AWS equivalentWhat's different
Azure Virtual Network (VNet)Amazon VPCA VPC lives in one Region; subnets live in one Availability Zone each
Subnets + route tables (UDRs)Subnets + route tables"Public" just means the route table has a route to an Internet Gateway
NAT GatewayNAT GatewayBilled hourly plus per GB processed — the classic lab bill shock
Network Security Groups (NSGs)Security groups (stateful) + network ACLs (stateless)SGs attach to network interfaces and can reference other SGs
Service endpoints / Private Endpoints / Private LinkGateway endpoints / interface endpoints / AWS PrivateLinkGateway endpoints (S3, DynamoDB) are free; interface endpoints bill hourly
Azure DNS / Private DNS zonesRoute 53 public and private hosted zonesRoute 53 adds routing policies and health checks for failover
Application Gateway / Azure Load BalancerApplication Load Balancer / Network Load Balancer / Gateway Load BalancerALB is layer 7 (HTTP), NLB is layer 4 (TCP/TLS, static IPs)
VNet peering / Virtual WANVPC peering / AWS Transit Gateway / Cloud WANPeering is not transitive; Transit Gateway is the hub for many VPCs
VPN Gateway / ExpressRouteSite-to-Site VPN / AWS Direct ConnectSame patterns; Direct Connect needs a partner and lead time
Azure FirewallAWS Network FirewallManaged stateful inspection and domain filtering for egress
NSG flow logs / Network WatcherVPC Flow Logs / Reachability AnalyzerReachability Analyzer proves a path exists or doesn't, without sending traffic

Learning objectives

By the end of this module you can:

  • Plan non-overlapping CIDR ranges for several environments and an on-premises network.
  • Build a VPC with public, private and isolated subnets across Availability Zones and explain every route.
  • Decide between security groups and network ACLs, and write SG rules that reference other SGs instead of IP ranges.
  • Reach S3, DynamoDB and other AWS APIs privately with VPC endpoints, and explain the cost trade-off against a NAT Gateway.
  • Configure Route 53 public and private hosted zones, routing policies and health checks.
  • Choose between ALB, NLB and Gateway Load Balancer for a workload.
  • Describe Site-to-Site VPN, Direct Connect, Transit Gateway and VPC peering, and sketch a bank's hybrid hub-and-spoke network.
  • Use VPC Flow Logs and Reachability Analyzer to prove what can and cannot talk to what.

Prerequisites

  • Module 1: AWS fundamentals — Regions, AZs, accounts, CLI with SSO
  • Basic TCP/IP knowledge (ports, DNS, HTTP/TLS) — refreshed in lesson 1 if needed

How the pieces fit

Only the load balancer faces the internet. The application tier reaches AWS services through endpoints, and the database tier has no route out at all.

Lessons

  1. Networking refresher for developers — IP addresses, CIDR notation, ports, DNS and TLS in ten minutes.
  2. Amazon VPC fundamentals — what a VPC is, default VPCs and why banks delete them.
  3. CIDR planning — an IP plan for dev/test/prod and on-premises ranges that must never overlap (Lab 2.1).
  4. Public, private and isolated subnets — three tiers across AZs and what makes a subnet "public" (Lab 2.2).
  5. Route tables and the internet gateway — how packets find their way and how to read a route table.
  6. NAT gateway and egress — outbound-only internet access, its hourly and per-GB cost, and NAT-free designs.
  7. Security groups vs network ACLs — stateful vs stateless, SG referencing, and layered defence.
  8. VPC endpoints and PrivateLink — gateway vs interface endpoints, endpoint policies and exposing your own service privately (Lab 2.3).
  9. DNS and Route 53 — public and private hosted zones, routing policies and health checks (Lab 2.5).
  10. Elastic Load Balancing — ALB, NLB and Gateway Load Balancer, listeners, target groups and TLS termination (Lab 2.4).
  11. Private networking patterns — keeping traffic off the internet end to end, including private APIs.
  12. VPC peering and Transit Gateway — connecting many VPCs and why peering doesn't scale for a bank.
  13. Hybrid connectivity — Site-to-Site VPN, Direct Connect, resilient connection models and hybrid DNS with Route 53 Resolver.
  14. VPC Flow Logs and Reachability Analyzer — enabling, reading and querying flow records, and proving what can talk to what.
  15. AWS Network Firewall — centralised inspection and domain-based egress filtering.
  16. Multi-account network architecture — shared VPCs, a central networking account and inspection VPCs.
  17. Lab: prove it's private — the module exercise: a database the internet cannot reach, proved with Reachability Analyzer and Flow Logs.

Labs and module exercise

The labs are written inside the lessons (each lesson's step-by-step section, with deploy-and-destroy steps) plus one standalone lab page backed by code.

  • Lab 2.1 (🟢) — CIDR planning worksheet for a fictional bank with three environments and two data centres, in CIDR planning.
  • Lab 2.2 (🟢) — Build a three-tier VPC with the console, then rebuild it from the CLI; compare, in Public, private and isolated subnets.
  • Lab 2.3 (🟢) — Add S3 and DynamoDB gateway endpoints with restrictive endpoint policies (both free), in VPC endpoints and PrivateLink.
  • Lab 2.4 (🟡) — Deploy an ALB in front of a tiny container, inspect listeners and health checks, then delete it, in Elastic Load Balancing.
  • Lab 2.5 (🟢) — Route 53 design exercise: failover and weighted records for a two-Region API, in DNS and Route 53.

Module exercise — prove it's private. Build a secure VPC with public and private subnets, deploy an application whose database sits in an isolated subnet, then prove the database is unreachable from the internet: run Reachability Analyzer from the Internet Gateway to the database's network interface (expect "not reachable"), and query VPC Flow Logs for rejected connection attempts. Tear down within the hour. The full walkthrough is Lab: prove it's private; the code is in labs/m02-secure-vpc/ (CIDR planner, flow-log checker, CDK and Terraform stacks, and a PowerShell proof script; tests run without an AWS account).

When you finish, keep the Module 2 cheat sheet handy for revision.

Cost profile

PartLabelFree alternative
VPC, subnets, route tables, IGW, security groups, NACLs🟢 freeNo charge for these components
Gateway endpoints (S3, DynamoDB)🟢 freeUse them instead of NAT for AWS service traffic
NAT Gateway🟡 creditsNAT-free design with endpoints; if you need one, create it, test, delete within the hour
Interface endpoints, ALB, public IPv4 addresses🟡 creditsAll bill hourly; deploy-and-destroy the same session
Route 53 hosted zone🟡 creditsMonthly fee per zone, waived if the zone is deleted within 12 hours (see the lesson); design-only exercise or create and delete the same day
Flow Logs and Reachability Analyzer🟡 creditsSmall per-GB and per-analysis charges ⚠ VERIFY; send flow logs to S3 to keep them cheap
Transit Gateway, Site-to-Site VPN, Direct Connect, Network Firewall🔴 paidDesign-only exercise with diagrams and route tables on paper

Certification alignment

ExamDomains (weight)What this module covers
SAA-C03Secure (30%) · Resilient (26%)VPC design, endpoints, load balancing, Route 53 failover, hybrid links
SOA-C03Networking (18%)Building and troubleshooting VPCs, Flow Logs, DNS
SCS-C03Infrastructure Security (18%)Segmentation, SGs/NACLs, Network Firewall, private access

Advanced Networking – Specialty is not on this roadmap

ANS-C01 retires on 2026-12-31, so this platform does not prepare for it. The networking depth you need is covered here and in the SAA-C03, SOA-C03 and SAP-C03 paths.

Key AWS services

Amazon VPC · Internet Gateway · NAT Gateway · Security groups and network ACLs · VPC endpoints and AWS PrivateLink · Amazon Route 53 (incl. Route 53 Resolver) · Elastic Load Balancing (ALB, NLB, GWLB) · VPC peering · AWS Transit Gateway · AWS Site-to-Site VPN · AWS Direct Connect · AWS Network Firewall · VPC Flow Logs · VPC Reachability Analyzer · AWS Resource Access Manager (shared VPCs)

Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.

On this page