Topic lessonTopic: Connecting VPCs and investigating traffic
Reading VPC Flow Logs: interface, direction and observation window
Fix the network interface and time window before interpreting the records. Separate ACCEPT, REJECT, missing data and application success.
Separate ACCEPT, REJECT, missing data and application success.
The exercise uses fictional records and does not collect packets or live traffic.
Choose a specific network observation point
A Flow Logs record aggregates a network flow for a specific interface over a capture window, using values such as source, destination and ports.
- Target traffic → Observation pointLimit traffic scope
- Observation point → Time windowMatch time and direction
- Time window → ComparisonCompare the application result
- Target traffic
- API 443/TCP
- Observation point
- Application ENI
- Time window
- Around 10:00 to 10:01
- Comparison
- The same synthetic request
Separate allowed traffic from the HTTP response
| Observation | State | Interpretation |
|---|---|---|
| Inbound at destination ENI | ACCEPT | Traffic was accepted at that observation point |
| Another synthetic port | REJECT | Traffic was rejected at this point |
| Target ENI at 10:02 | SKIPDATA | Do not infer normal operation from missing data |
| Application record at 10:00 | HTTP 503 | The request did not succeed at the application |
ACCEPT describes whether traffic was accepted. It does not include packet contents or reveal a successful HTTP response or data update.
Identify what missing data can establish
Match interface and window. Align source, destination, port and direction. Account for aggregation and delay in delivery.
Treat a rejection as a clue. Do not identify a specific rule from REJECT alone. Check the policy that applies to the observation point.
Add workload evidence. Match the application request timestamp and response to a flow, and record acceptance separately from application success.
Check the worked example
Choose an option to see the result and explanation.
Check, then explain in your own words
- Fix the ENI and traffic scope.
- Read action and log-status for the same window.
- Compare application results and record both conclusions.
Check your understanding: Does ACCEPT prove a successful HTTP response?
Check the application response and outcome for the same attempt.
Permitted traffic is distinct from a successful transaction.
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.
- VPC Flow Logs recordsChecked:
Scope and conditionsInterface, aggregation interval, action and log-status.
Used in this lessonChoose a specific network observation point Separate allowed traffic from the HTTP response Identify what missing data can establish