Free lesson · What a Network Actually Is

Packets: why data is chopped up

When you download a 50 MB file, it does not travel as one 50 MB thing. It is cut into thousands of small pieces called packets, each sent separately, each finding its own way, and reassembled at the far end.

That sounds like more work than sending it whole. It is, and it is worth it for three reasons.

1. Loss becomes cheap

Networks lose data. A cable is disturbed, a device is momentarily overloaded, a wireless signal fades. If the file travelled as one unit, any single error would ruin the entire transfer and it would start again from nothing.

With packets, one lost piece means one piece is resent. The other 9,999 are unaffected.

2. Links can be shared

If one machine could seize a link for a whole 50 MB transfer, everyone else would wait. Because the data is in small pieces, packets from many different conversations interleave on the same wire — your download, someone's video call, a database query — and all progress at once.

3. Paths can differ

Each packet is independently addressed, so each can take a different route. If part of the internet becomes congested or fails mid-transfer, later packets simply go another way. Nothing has to be renegotiated.

A consequence worth holding on to: packets can arrive out of order, and something has to put them back in sequence. That something is usually TCP, later in this section.

What a packet contains

Every packet carries a header and a payload. The payload is your data. The header is the envelope — the information the network needs to deliver it:

  • Where it came from (source address)
  • Where it is going (destination address)
  • What kind of traffic it is
  • How to check it arrived undamaged

The addresses are the part that matters for everything in this course. When you write a security group rule, a route table entry, or a NACL, you are writing rules about packet headers — about which source and destination combinations are allowed and where they should be sent.

And when you read a VPC Flow Log in section twelve, you are reading a summary of exactly these header fields. It looks intimidating until you know it is just this list.

This is one lesson of 92

AWS Cloud Networking: From IP Addresses to Production VPCs continues from here — 6 lessons are free to read like this one, and the rest come with the course. Enrolled readers also get an AI tutor that has read the lesson they are on.

See the full course