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

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Separate ACCEPT, REJECT, missing data and application success.

Prerequisite

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.

Match a request to the right evidence
Match a request to the right evidence1: Target traffic — Limit traffic scope — Observation point. 2: Observation point — Match time and direction — Time window. 3: Time window — Compare the application result — Comparison123Target trafficObservation pointTime windowComparisonMatch a request to the right evidence1: Target traffic — Limit traffic scope — Observation point. 2: Observation point — Match time and direction — Time window. 3: Time window — Compare the application result — Comparison123Target trafficObservationpointTime windowComparison
  1. Target traffic → Observation pointLimit traffic scope
  2. Observation point → Time windowMatch time and direction
  3. 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

Fictional records from the target ENI’s perspective.
ObservationStateInterpretation
Inbound at destination ENIACCEPTTraffic was accepted at that observation point
Another synthetic portREJECTTraffic was rejected at this point
Target ENI at 10:02SKIPDATADo not infer normal operation from missing data
Application record at 10:00HTTP 503The 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.

The ENI reports ACCEPT but the request returns HTTP 503. What is the result?
Read the answer and reason

Answer: Traffic accepted; application request unsuccessful · These are separate types of evidence.

Does SKIPDATA establish that no traffic occurred?
Read the answer and reason

Answer: Results for that window remain unverified · Records were skipped for the window.

What makes two records comparable here?
Read the answer and reason

Answer: The ENI, direction, destination and time window · Match the conditions that identify the same traffic.

Check, then explain in your own words

  1. Fix the ENI and traffic scope.
  2. Read action and log-status for the same window.
  3. 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.