Cloud concept · Updated

Packet Capture - Packet capture records individual network packets at an observation point so engineers can inspect protocol behavior and troubleshoot communication.

In short

Packet capture provides packet-level evidence, including headers, timestamps, and any captured payload bytes, rather than only aggregate traffic statistics. In cloud and hybrid networks, it helps engineers validate connectivity, diagnose intermittent failures, and investigate security events, provided the capture point and collection scope match the problem.

Cloud Concepts Hub →

6 key aspects of Packet Capture

Effective packet capture combines carefully placed observation points, controlled tests, sufficient collection capacity, and secure handling of packet-level evidence.

01
Packet-level evidence

Captures preserve individual packet observations, including timing, headers, and the payload bytes retained by the capture configuration. Use them to investigate handshakes, retransmissions, resets, and protocol errors that flow summaries cannot fully explain.

02
Observation-point awareness

A capture describes traffic visible at its collection point, not the entire end-to-end path. Capture near both endpoints when possible, and account for NAT, tunnels, load balancers, and asymmetric routes when correlating packets.

03
Selective collection and capacity planning

Filter traffic and limit collection duration to control bandwidth, CPU, and storage consumption. Monitor collector drops and understand packet-length limits before treating missing packets or payload bytes as evidence of network loss.

04
Complementary visibility methods

Use flow logs for broad traffic metadata, configuration analyzers for supported routing and policy checks, and packet capture for live protocol evidence. A successful configuration analysis does not establish that an application is healthy.

05
Controlled connectivity validation

Generate repeatable tests using the application protocol and compare observations in both directions. For hybrid paths, include return routing, tunnel boundaries, and packet-size behavior rather than relying only on ping.

06
Sensitive-data handling

Packet files can expose application content, identifiers, and credentials. Apply access controls, encryption, retention limits, and authorized collection procedures; encrypted application payloads are not automatically readable.

Cloud services for Packet Capture

Use VPC Flow Logs to establish broad traffic visibility and identify connections that need deeper investigation. VPC Reachability Analyzer and AWS Network Manager's Transit Gateway Route Analyzer help evaluate supported configuration and routing questions without capturing live packets. For runtime evidence, capture locally on EC2 or deliver selected traffic through VPC Traffic Mirroring to an analysis collector. Correlate these observations with controlled application tests and on-premises captures for hybrid paths. Collection tooling can upload packet files to Amazon S3, where access controls and retention policies protect the resulting evidence. These capabilities complement one another; no single tool establishes every aspect of end-to-end connectivity.

Amazon EC2Amazon EC2

Provides workload hosts where tools such as tcpdump can capture traffic visible to the guest operating system. EC2 instances can also host traffic-mirroring collectors, with appropriate permissions, software, and network capacity.

Amazon S3Amazon S3

Can store capture files uploaded by collection tooling for later investigation. Apply restrictive access policies, encryption, and lifecycle rules because packet archives can contain sensitive data and grow quickly.

Packet Capture exam questions

Real practice exam questions on Packet Capture, with the correct answer and its explanation. Answer them with every option in the exam simulator.

ANS-C01

A company runs a client application and an HTTPS service on Amazon EC2 instances in separate AWS accounts in the same Region. Their VPCs communicate through a shared transit gateway. Both instances use network interfaces that support VPC Traffic Mirroring. Most HTTPS requests succeed, but some connections time out. Configuration reviews have found no routing, security group, or network ACL errors.

A network engineer must determine whether TCP SYN packets reach the service instance and whether SYN-ACK packets or TCP resets return to the client during failed attempts. The engineer needs packet-level timestamps and TCP sequence information from both endpoints. Company policy prohibits installing software or running diagnostic commands on the production instances and prohibits changing their traffic paths.

Which solution meets these requirements?

Show answerCORRECT ANSWER

Create Traffic Mirroring sessions for both production network interfaces, with filters covering both directions of the HTTPS connections. Send the mirrored traffic to appropriately sized EC2 collectors in the respective VPCs, allow VXLAN delivery to the collectors, and capture and correlate the encapsulated packets.

VPC Traffic Mirroring copies actual traffic from supported EC2 network interfaces without requiring diagnostic software on the source instances or redirecting their production traffic. Collectors that receive and decode the VXLAN traffic can record TCP flags, sequence numbers, and packet timestamps. Capturing at both endpoints helps distinguish forward-path delivery failures from missing or rejected responses.

Practice Packet Capture in a full exam

Questions on Packet Capture in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Packet Capture

3 min read

Packet capture records packets observed at a network interface or another collection point, usually in a format such as PCAP or PCAPNG. Engineers analyze these records with tools such as Wireshark, tcpdump, or protocol-analysis platforms. Captures can reveal TCP connection establishment, retransmissions, resets, DNS exchanges, ICMP errors, and application messages when those messages are not encrypted. What a capture proves depends on where it was collected: seeing a packet leave a client does not prove that it reached the server.

Cloud environments typically do not allow customers to attach a sniffer to the provider's physical switches. Instead, engineers capture traffic inside a workload or use a supported traffic-mirroring capability to copy selected interface traffic to an analysis appliance. On AWS, VPC Traffic Mirroring copies selected traffic from supported EC2 network interfaces to a configured mirror target using VXLAN encapsulation. The collector must handle the encapsulation and have sufficient network, processing, and storage capacity. Mirroring does not automatically create a durable packet archive.

Flow logs and packet captures answer different questions. VPC Flow Logs provide flow-level metadata, such as addresses, ports, traffic counts, and accept or reject information, but do not record packet payloads or a packet-by-packet timeline. They are useful for broad, ongoing visibility across many resources. Packet capture provides deeper evidence for a narrower investigation, at greater collection and analysis cost. Neither method guarantees visibility into every packet or every managed-service internal path.

For a failed connection between an on-premises client and a cloud server, first identify the source, destination, protocol, port, expected route, and return route. Generate a controlled test using the actual application protocol, then capture at both endpoints where possible. Repeated TCP SYN packets at the client with no corresponding arrival at the server suggest a problem somewhere between those observation points. A SYN arriving at the server without a SYN-ACK leaving it shifts attention toward the server, its host firewall, or its local configuration. Compare captures with routing information, flow logs, and firewall logs before assigning a root cause.

Hybrid investigations must account for NAT, asymmetric routing, encryption boundaries, and packet size. NAT can change the addresses and ports used to correlate observations. A capture outside a VPN tunnel normally shows encrypted tunnel traffic rather than the original application packets. Successful small probes do not establish that larger application packets work; controlled packet-size tests and relevant ICMP messages can help diagnose path MTU problems. Synchronize capture-host clocks before comparing timestamps across environments.

Configuration-analysis tools complement captures but do not replace them. VPC Reachability Analyzer evaluates supported network configurations without sending packets. Transit Gateway Route Analyzer in AWS Network Manager analyzes transit gateway routing rather than capturing live traffic or proving application health. Across accounts, Regions, and VPCs, use these tools within their supported scopes, then validate actual behavior with controlled traffic and observations at accessible endpoints.

Capture collection has operational and security costs. Narrow the source interfaces, direction, protocols, time window, and captured packet length to the investigation. Truncation reduces volume but can remove evidence needed for protocol analysis. Collector overload can drop packets, while host offloading can produce misleading checksum or segmentation artifacts. TLS payloads remain encrypted unless an authorized decryption method is available. Treat capture files as sensitive data: restrict access, encrypt storage, define retention, and avoid collecting credentials or unrelated user content.