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.
Explain where one changed condition affects the path, distinguishing checked, unsatisfied, unexamined and unknown conditions.
Know VPCs and the SG/NACL distinction. Boolean inputs are synthetic facts, not parsed real settings.
Establish the modeled topology first
Subnet A
Subnet 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
| Try | Prediction and observation |
|---|---|
| Evaluate the initial inter-subnet case | Modeled path conditions are met; real traffic remains untested |
| Set destination NACL return egress to false | Inspect the failed return condition and reason |
| Set same subnet to true | NACL scope changes; SG checks still remain |
| Make a required condition unknown | Do 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
| Label | Meaning |
|---|---|
| Checked: satisfied | The model evaluated and satisfied this condition |
| Checked: not satisfied | This failed condition stopped the evaluation |
| Not checked | An earlier stop or scope boundary prevented this check |
| Not applicable: same subnet | This case does not use inter-subnet NACL checks |
| Missing context | A necessary fact is unknown |
Choose an option to see the result and explanation.
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
- Choose a guided case below and read its baseline conditions and reason.
- Change one forward or return fact, predict and evaluate again.
- Explain the stopping point, unexamined later stages and untested real-world conditions.
Check, then explain in your own words
- Identify request and response directions.
- Change one condition in the same case.
- 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.
Try different conditions
Compare fixed synthetic conditions locally. No real AWS operations, input persistence or input transmission occur.
Loading exercise…
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 lessonLesson overview and review
- VPC security groupsChecked:
Scope and conditionsStateful resource traffic controls
Used in this lessonEstablish the modeled topology first Separate SG response handling from NACL return rules
- VPC network ACLsChecked:
Scope and conditionsStateless subnet boundary controls; rule order and return traffic
Used in this lessonEstablish the modeled topology first Separate SG response handling from NACL return rules
- VPC route tablesChecked:
Scope and conditionsDestination/target and subnet associations
Used in this lessonEstablish the modeled topology first