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 18 of 18Topic: VPC: routing and traffic controls

VPC path lab: compare SG and NACL request and response conditions

Change route, SG and NACL conditions in a bounded IPv4/TCP model within one VPC. Inspect both request and response directions, and keep stages after an evaluation stop explicitly unexamined. The lab sends no real packets and does not connect to AWS.

What you will learn

Explain where one changed condition affects the path, distinguishing checked, unsatisfied, unexamined and unknown conditions.

Prerequisite

Know VPCs and the SG/NACL distinction. Boolean inputs are synthetic facts, not parsed real settings.

Start the exercise →

Establish the modeled topology first

Compare two network interfaces in one VPC
Amazon VPC One VPC, different subnets

Subnet A

Source ENIENI · 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 ENIENI · Network interfaceSG B

Arrows show request and response directions. SGs apply at the resource; NACLs apply at subnet boundaries.

Source ENI
Initiates the request; inspect the source SG egress fact.
Destination ENI
Receives the request; inspect the destination SG ingress fact.
Across subnet boundaries
Across subnets, inspect four NACL directions. Same-subnet placement changes that scope.

The figure above is a fixed illustration of a TCP 443 request across subnets. Model inputs are pre-analyzed synthetic route and control facts, rather than port numbers. This is not a parser for real IP lists, SG references, route priority or NACL rule order. Stage labels indicate what the model evaluated, not observed network activity.

Change one return-direction condition

Start with the same request
TryPrediction and observation
Evaluate the initial inter-subnet caseModeled path conditions are met; real traffic remains untested
Set destination NACL return egress to falseInspect the failed return condition and reason
Set same subnet to trueNACL scope changes; SG checks still remain
Make a required condition unknownDo not turn missing context into observed denial or success

After an edit, inspect whether the displayed result is stale. Reset restores the selected case’s initial values. When changing cases or several inputs, establish the new premises before comparing outcomes.

An unexamined stage has not passed

Read the path-stage labels
LabelMeaning
Checked: satisfiedThe model evaluated and satisfied this condition
Checked: not satisfiedThis failed condition stopped the evaluation
Not checkedAn earlier stop or scope boundary prevented this check
Not applicable: same subnetThis case does not use inter-subnet NACL checks
Missing contextA necessary fact is unknown

Choose an option to see the result and explanation.

A return NACL condition fails. How should later stages be read?
Read the answer and reason

Answer: They remain unexamined · Do not mark a stage successful after evaluation has stopped. Also keep modeled stage labels separate from observations of real traffic.

Separate SG response handling from NACL return rules

The lab does not invent an extra return SG requirement for responses to an allowed request. NACLs across subnets still need both directions. Switching to the same subnet retains SG checks.

Explain the change and what remains unverified

  1. Choose a guided case below and read its baseline conditions and reason.
  2. Change one forward or return fact, predict and evaluate again.
  3. Explain the stopping point, unexamined later stages and untested real-world conditions.

Check, then explain in your own words

  1. Identify request and response directions.
  2. Change one condition in the same case.
  3. Distinguish an unsatisfied condition from an unexamined stage.
Check your understanding: If NACL checks are not applicable within one subnet, can you skip SG checks?

SG checks still apply.

A change in NACL scope does not disable SGs associated with the resources.

INTERACTIVE / VPC

Try different conditions

Compare fixed synthetic conditions locally. No real AWS operations, input persistence or input transmission occur.

Loading exercise…

Review: calculate a CIDR range →

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.