openskills.info
Course catalog
AWS Networking logoCourse Preview

AWS Networking

AWS networking provides the virtual network infrastructure for cloud workloads: VPCs, subnets, route tables, gateways, load balancers, and DNS. It controls how traffic flows between resources, the internet, and on-premises environments.

itCloud computing

Don't Panic — AWS Networking

AWS networking is the set of rules that decides which AWS systems may talk, where their packets go, and where a sensible boundary says no. It is less a collection of magical cloud pipes than a virtual network with several opportunities to point a packet at the wrong door.

Start with Amazon VPC, the isolated network inside one AWS Region. Give it address ranges, split those ranges into subnets in Availability Zones, and attach resources through network interfaces. The memorable part is not the inventory. It is the order: address the network, place the workload, route the packet, then filter the flow. The packet, with admirable indifference to architecture diagrams, checks the actual path.

A public subnet is not a personality trait. It is a subnet with a route to an internet gateway. A resource still needs a public IPv4 or IPv6 address to use that path. A private subnet can send IPv4 traffic outward through a NAT gateway, but outside hosts cannot start an unsolicited connection back through it. The useful surprise is that a route creates a next hop, not permission. A security group or network ACL can still stop the trip, and the return journey also needs to work.

When networks must connect, do not begin by collecting services like decorative stamps. VPC peering connects two VPCs directly and does not pass traffic onward through a third. Transit Gateway is the hub for many VPC and hybrid attachments. AWS PrivateLink is narrower: it exposes one supported service through private endpoints, rather than granting a whole network a visitor's pass. For premises connectivity, Site-to-Site VPN supplies encrypted tunnels, while Direct Connect supplies a dedicated Ethernet path. Each answers a different relationship.

Names and load balancers sit above this machinery. Route 53 can return the correct address; it cannot rescue a missing route. A load balancer can choose a healthy target; it cannot negotiate an unopened port. This is why VPC Flow Logs are useful: they provide evidence about observed traffic metadata when the expected flow and the actual one disagree.

Read the intro for the complete map and glossary. Use the slides when you need the choices side by side. Keep the cheatsheet nearby when debugging address, route, and filter decisions. The field notes cover operational traps that appear when the diagram has grown confident and the packet has not.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources