Module 2 cheat sheet
One-page revision summary for AWS Networking: services, Azure mapping, CLI commands, limits, decision rules, exam traps and cost traps.
Assumes: AWS CLI v2 · IPv4 + IPv6 · Region us-east-1 · prices and limits as stated in the Module 2 lessons (us-east-1, checked 2026-11-18); items marked VERIFY there are not repeated as certain here. Verified against official sources on 2026-11-18.
A printable summary of Module 2. Each row links back to the lesson with the detail.
Key services
| Service | What it is for |
|---|---|
| VPC, subnets, route tables | Regional private network; subnets are zonal; routes decide where packets go |
| Internet gateway / NAT gateway | Two-way public access / outbound-only access |
| Security groups / network ACLs | Stateful allow-only on ENIs / stateless ordered allow and deny on subnets |
| Gateway and interface endpoints, PrivateLink | Private paths to AWS services (S3 and DynamoDB free) / to your own NLB-fronted service |
| Route 53 and Resolver | Public and private DNS, routing policies, health checks, hybrid DNS |
| ALB / NLB / GWLB | HTTP routing and WAF / TCP, static IPs, PrivateLink / appliance insertion |
| VPC peering / Transit Gateway | Two-VPC link (non-transitive) / Regional hub for many VPCs and on-premises |
| Site-to-Site VPN / Direct Connect | Encrypted internet tunnels / private dedicated circuit |
| Network Firewall | Stateless and Suricata stateful inspection, domain allow-lists |
| Flow Logs / Reachability Analyzer | What did talk / what could talk, from configuration |
.NET / Azure → AWS
| Microsoft / Azure | AWS |
|---|---|
| VNet | VPC (Regional; subnets per AZ) |
| NSG | Security group (stateful) + network ACL (stateless) |
| Service endpoint / Private Endpoint | Gateway endpoint / interface endpoint (PrivateLink) |
| Azure DNS, Private DNS zones | Route 53 public and private hosted zones |
| Application Gateway / Load Balancer | ALB / NLB |
| VNet peering, Virtual WAN | VPC peering, Transit Gateway |
| VPN Gateway / ExpressRoute | Site-to-Site VPN / Direct Connect |
| Azure Firewall | Network Firewall |
| NSG flow logs, Network Watcher | VPC Flow Logs, Reachability Analyzer |
Most useful CLI commands
| Task | Command |
|---|---|
| List VPCs and subnets | aws ec2 describe-vpcs · aws ec2 describe-subnets --filters Name=vpc-id,Values=VPC_ID |
| Read a route table | aws ec2 describe-route-tables --filters Name=vpc-id,Values=VPC_ID |
| Add S3 gateway endpoint | aws ec2 create-vpc-endpoint --vpc-id VPC_ID --service-name com.amazonaws.us-east-1.s3 --route-table-ids RTB_ID |
| Audit security group rules | aws ec2 describe-security-group-rules --filters Name=group-id,Values=SG_ID |
| Enable flow logs | aws ec2 create-flow-logs --resource-type VPC --resource-ids VPC_ID --traffic-type ALL ... |
| Prove a path | aws ec2 create-network-insights-path ... then aws ec2 start-network-insights-analysis ... |
| Find leftovers | aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab |
Key limits and defaults
| Item | Value | Lesson |
|---|---|---|
| VPC size; AWS-reserved addresses per subnet | /16 to /28; 5 per subnet | Refresher |
| VPCs per Region; subnets per VPC; IPv4 CIDRs per VPC | 5; 200; 5 (up to 50) | VPC fundamentals |
| Route tables per VPC; internet gateways per VPC | 200; one | Route tables and IGW |
| Security group rules | 60 in, 60 out per SG; 5 SGs per ENI | SGs vs NACLs |
| Ephemeral ports to allow in NACLs | 1024-65535 | Refresher |
| Endpoint quotas | 20 gateway endpoints per Region; 50 interface endpoints per VPC | Endpoints |
| VPC peerings per VPC | 50 (up to 125); full mesh needs n(n-1)/2 | Peering and TGW |
| Transit Gateway | 5 per Region; 5,000 attachments; up to 100 Gbps per VPC attachment per AZ | Peering and TGW |
| VPN tunnel bandwidth | 1.25 Gbps standard; 5 Gbps large-bandwidth; two tunnels per connection | Hybrid |
| ALB idle timeout | 60 seconds; keep app keep-alive longer | ELB |
| Flow log interval | 600 s default; 60 s optional | Flow Logs |
Decision rules
| If… | Then… |
|---|---|
| Reaching S3 or DynamoDB from private subnets | Gateway endpoint (free), not NAT |
| Reaching other AWS APIs privately | Interface endpoint, centralised at scale |
| Database or customer data tier | Isolated subnet: local route only, SG from app SG only |
| Rules inside the VPC | Reference security groups, not IP ranges |
| Immediate cut-off of an address | NACL deny (SG changes may not end tracked connections) |
| Overlapping CIDRs between VPCs | PrivateLink, not peering |
| Three or more VPCs, or on-premises plus VPCs | Transit Gateway hub, separate route tables per segment |
| HTTP routing, WAF, OIDC | ALB |
| Static IPs, raw TCP/TLS, PrivateLink service | NLB |
| Allow-list internet egress by domain | Network Firewall (strict order, drop established) |
| Quick, encrypted link to a data centre | Site-to-Site VPN; Direct Connect for predictable bandwidth |
| Canary release / DR / latency / residency | Weighted / failover / latency / geolocation routing |
| Proving a database is private | Reachability Analyzer plus Flow Logs, with a positive control |
Common exam traps
- "Public subnet" only means a route to an internet gateway. Internet access also needs a public address and open SG/NACL rules.
- Network ACLs are stateless: allow the ephemeral return ports; SGs are stateful.
- SGs cannot deny; use a NACL deny for blocking.
- VPC peering is not transitive and gives no edge-to-edge routing through a peer's gateway.
- Gateway endpoints work only from inside the VPC; interface endpoints are reachable over VPN and Direct Connect.
- A NAT gateway is not a firewall and never accepts unsolicited inbound connections.
- An all-unhealthy ALB target group fails open.
- Route 53 health checkers sit on the internet: use CloudWatch-alarm checks for private resources.
- DNS failover is bounded by TTL and by client connection reuse.
- Flow logs show allowed or rejected, not which control rejected, and arrive minutes late.
- Reachability Analyzer proves configuration, not traffic.
- Most Transit Gateway incidents are a missing return route.
Cost traps
| Trap | Avoid it by |
|---|---|
| S3/DynamoDB traffic through a NAT gateway (USD 0.045/GB) | Add the free gateway endpoints |
| NAT gateway per AZ idle (about USD 110/month for three, with addresses) | NAT-free design or delete after the lab |
| Idle ALB (about USD 16/month plus public IPv4) | Delete after the lesson |
| Interface endpoints (USD 0.01 per AZ-hour plus USD 0.01/GB) | Add only what you need; centralise |
| Transit Gateway (USD 0.05 per attachment-hour plus USD 0.02/GB) | Design-only; peering for heavy two-VPC flows |
| Site-to-Site VPN (USD 0.05 per connection-hour) and Direct Connect port-hours | Design-only on paper |
| Route 53 hosted zone (USD 0.50/month) | Delete within 12 hours to avoid the fee |
| Reachability Analyzer (USD 0.10 per analysis) and verbose flow logs | Run few analyses; send logs to S3 with retention |
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.
Lab: prove it's private — a database the internet cannot reach
Deploy a three-tier VPC with an isolated PostgreSQL database, then prove it is unreachable from the internet with Reachability Analyzer, VPC Flow Logs and a tested C# evidence checker — and tear it all down within the hour.
Module 3: .NET Application Development on AWS
Build, containerise, configure and deploy ASP.NET Core applications on AWS the way a bank would run them. You compare every hosting option (EC2, Elastic Beanstalk, ECS on Fargate, Lambda and more) and finish by deploying the same Web API three different ways.