Core lesson 15 of 18Topic: VPC: routing and traffic controls
What is Amazon VPC? Subnets, routes and traffic controls explained
Amazon Virtual Private Cloud (VPC) is a virtual network for AWS resources. Subnets divide its address space into ranges. Route tables direct traffic; security groups and network ACLs control traffic. Creating a VPC or assigning an IP address does not establish that an application can communicate.
Separate placement, routing, traffic controls and application behavior, and explain what a request and its response require.
Think of an IP address as identifying a network destination. No AWS connection or VPC creation is needed.
Start with VPCs, subnets and network interfaces
| Term | Role | What to establish |
|---|---|---|
| VPC | The virtual network | Which VPC the example concerns |
| Subnet | An address range within one Availability Zone | Where the source and destination are placed |
| ENI: Elastic Network Interface | A network interface used by a resource | Its addresses and associated security groups |
An Availability Zone (AZ) is an availability boundary within an AWS Region. A VPC can contain multiple subnets, but a subnet resides in one AZ. Resources in the same VPC can still have different subnet placement and associated controls.
Trace a request and response across two subnets
Subnet A
Subnet B
Arrows show request and response directions. SGs apply at the resource; NACLs apply at subnet boundaries.
- Source app
- The initiator; review source SG egress.
- Destination web server
- The target; review destination SG ingress.
- Request and response paths
- Review applicable route tables and the NACL directions at both subnet boundaries.
A route maps a destination address range to a target. A route table holds these mappings. Identify the table associated with the originating subnet before reading its destinations and targets.
Routing and permission to pass traffic are separate
| Question | Evidence to inspect | Still not established |
|---|---|---|
| Placement | VPC, subnet, IP and ENI | Routing or permitted traffic |
| Routing | Associated table, destination and target | Whether SG and NACL conditions are met |
| Traffic controls | Applicable SG and NACL rules | OS listeners or application authentication |
| Application | Listener, host configuration and authentication | Whether a different request will also succeed |
A security group (SG) provides allow rules for associated resources. A network ACL (NACL) applies allow and deny rules to traffic entering or leaving a subnet. SG response handling and NACL directional rules are not the same mechanism.
Choose an option to see the result and explanation.
Address space does not imply Internet connectivity
CIDR represents an address range with a prefix length, such as /24. Multiple subnets within a VPC must not overlap. Separate general address arithmetic from AWS rules for allowed subnet sizes and reserved addresses.
Internet or other-network connectivity needs the appropriate gateway, routing, addressing and controls. A VPC alone does not make every resource publicly reachable. Also distinguish the VPC itself from chargeable components used in its design.
Practice a bounded path within one VPC
- Draw the source and destination subnets.
- Locate the applicable route table, SG and NACL checks.
- Read the SG/NACL comparison, then change one return condition in the VPC lab.
Check, then explain in your own words
- Separate placement, routing, controls and applications.
- Trace both the request and the response.
- Distinguish modeled path conditions from real traffic verification.
Check your understanding: Do two IP addresses within one VPC establish a working web application?
No. Conditions beyond placement remain.
Routing, SG/NACL conditions, host state, listeners and authentication need their own evidence. A placement diagram does not verify them all.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- What is Amazon VPC?Checked:
Scope and conditionsVirtual networking; no implicit Internet reachability
Used in this lessonStart with VPCs, subnets and network interfaces Trace a request and response across two subnets Routing and permission to pass traffic are separate Address space does not imply Internet connectivity
- VPC route tablesChecked:
Scope and conditionsDestination/target and subnet associations
Used in this lessonTrace a request and response across two subnets Routing and permission to pass traffic are separate
- VPC security groupsChecked:
Scope and conditionsStateful resource traffic controls
Used in this lessonStart with VPCs, subnets and network interfaces Trace a request and response across two subnets Routing and permission to pass traffic are separate
- VPC network ACLsChecked:
Scope and conditionsStateless subnet boundary controls; rule order and return traffic
Used in this lessonTrace a request and response across two subnets Routing and permission to pass traffic are separate
- VPC subnet CIDR blocksChecked:
Scope and conditionsAWS subnet size restrictions and reserved addresses differ from generic arithmetic
Used in this lessonStart with VPCs, subnets and network interfaces Address space does not imply Internet connectivity
- Subnet route tablesChecked:
Scope and conditionsSubnet associations, implicit main-table use, destinations, targets and IPv4/IPv6 distinction.
Used in this lessonTrace a request and response across two subnets
Scope and conditionsConnection mode, network, host and authentication must be separated
Used in this lessonRouting and permission to pass traffic are separate
- Elastic network interfacesChecked:
Scope and conditionsVirtual network interface attributes, addresses and associated security groups; not a real connectivity test.
Used in this lessonStart with VPCs, subnets and network interfaces