INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Separate placement, routing, traffic controls and application behavior, and explain what a request and its response require.

Prerequisite

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

Three terms that describe placement
TermRoleWhat to establish
VPCThe virtual networkWhich VPC the example concerns
SubnetAn address range within one Availability ZoneWhere the source and destination are placed
ENI: Elastic Network InterfaceA network interface used by a resourceIts 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

An app and web server in different subnets of one VPC
Amazon VPC One VPC, different subnets

Subnet A

Source appENI · Network interfaceSG A
NACL A Subnet boundary
TCP request and response directionsThe request travels from source to destination; the response returns to the client port used by the source.Request: TCP 443Reply: client portTCP request and response directionsThe request travels from source to destination; the response returns to the client port used by the source.RequestTCP 443ResponseClient port

Subnet B

NACL B Subnet boundary
Destination web serverENI · Network interfaceSG 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

Four separate questions
QuestionEvidence to inspectStill not established
PlacementVPC, subnet, IP and ENIRouting or permitted traffic
RoutingAssociated table, destination and targetWhether SG and NACL conditions are met
Traffic controlsApplicable SG and NACL rulesOS listeners or application authentication
ApplicationListener, host configuration and authenticationWhether 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.

You found a route to the destination. Does that verify a successful application connection?
Read the answer and reason

Answer: No; traffic controls and application checks remain · A route selects a target. Traffic controls, the OS, a listener and actual connection evidence are separate questions.

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

  1. Draw the source and destination subnets.
  2. Locate the applicable route table, SG and NACL checks.
  3. Read the SG/NACL comparison, then change one return condition in the VPC lab.

Check, then explain in your own words

  1. Separate placement, routing, controls and applications.
  2. Trace both the request and the response.
  3. 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.