Skip to main content
emnode / learn
Learning path

Trim your network spend

NAT gateways, idle load balancers and public IPv4: the quiet network line items.

6 lessons·~79 min total

Lessons in this path

  1. 1
    Cost AWS

    Delete unused NAT Gateways

    A NAT Gateway with no traffic still bills $32/month — find the orphans and replace them with VPC endpoints where possible.

    14 min
  2. 2
    Cost AWS

    Delete idle load balancers

    A load balancer with no healthy targets still bills the hourly + LCU floor — find them and decide before they keep adding up.

    13 min
  3. 3
    Cost AWS

    Reduce NAT Gateway data processing costs

    A busy NAT Gateway's hourly fee is the small part — at scale the per-GB processing charge dwarfs it, and much of that traffic should never have touched NAT at all.

    13 min
  4. 4
    Cost AWS

    Consolidate redundant NAT Gateways

    Many VPCs run more NAT Gateways than they need — each one bills ~$32/month just to exist, so collapse the duplicates without breaking your AZ-resilience or cross-AZ data-transfer math.

    12 min
  5. 5
    Compliance AWS

    Block public access to AWS resources

    One capability across S3, EC2, RDS, snapshots, queues and topics: make sure nothing is reachable from, or shareable with, the public internet unless you genuinely intend it.

    14 min
  6. 6
    Compliance AWS

    Secure Site-to-Site VPN connections

    One capability across Site-to-Site and Client VPN: run tunnels on current crypto, keep redundant tunnels up, and log every connection, so the encrypted links into your network are modern, resilient and auditable.

    13 min